Privacy Policy

The data Ray receives depends on the features you choose. Opening or playing a local media file does not by itself upload that file to Ray. Cloud features, sign-in, support, and checkout require the data described below.

• Account data: email address, name if supplied, license and entitlement records, sign-in and verification events, account role, subscription status, device sessions, synchronized preferences, and usage balances.
• Device and app data: a Ray installation identifier, device type and model, operating system and app version, language, feature availability, local-network capability, IP-derived country or region, and security events.
• Cloud media data: audio or media you deliberately submit for cloud subtitles, transcription, translation, dubbing, summaries, or assistant features; associated filenames or source metadata; content identifiers; transcripts; subtitle cues; translations; generated audio; summaries; questions; and answers.
• Local recording data: camera, microphone, screen, and app-audio recordings you create with Capture. These remain on your device unless you explicitly choose a Ray Cloud feature, export, or share action.
• Library and playback data: media references, titles, artwork, subtitle choices, playback position, playlists, channels, and settings stored locally or synchronized when you enable the corresponding account feature.
• Diagnostics: crash reports, stack traces, performance and network diagnostics, app state, and the Ray installation identifier used to correlate a support report with a device. Ray does not attach your email address or license key to new mobile and TV crash reports.
• Support data: account email, messages and attachments you submit, conversation history, installation identifier, device/app details, plan and usage context, and diagnostics you choose to share through Intercom or email.
• Remote support session data, only if you start a session in the Ray app: details about Ray and your computer, Ray's activity log with personal details removed, test results, the settings our team tried, and a record of the session and your choices. See Remote support sessions in the Ray app.
• Checkout and order data: name, email address, cart contents, order reference, payment method, amount, currency, country, and payment status.
• Payment confirmation data: transaction identifiers, fraud-prevention signals, payment gateway status messages, and webhook or notification metadata.
• Marketing and product updates: email address, subscription preferences, campaign source, and consent or unsubscribe status.
• Website data: IP address, browser type, device information, cookies or local storage, analytics events, and security logs needed to operate and protect the site.

• To create and manage purchases, receipts, refunds, customer notices, software access, API access, and delivery communications where applicable.
• To authenticate Ray accounts, enforce device seats and entitlements, synchronize selected settings, meter cloud usage, and provide account management.
• To process media only when you request a cloud subtitle, transcription, translation, dubbing, summary, or assistant feature, and to return and reuse the requested output for that account.
• To discover and securely connect Ray devices on the same local network for nearby sign-in or user-requested processing and handoff.
• To redirect you to the correct payment provider and verify payment results after the provider sends us a return or webhook notification.
• To add paid customers to the correct customer email list and send purchase confirmation messages.
• To answer support requests, correlate a report with the affected installation, prevent fraud, diagnose crashes or service failures, and keep Ray secure.
• To run remote support sessions you start in the Ray app: to find and fix problems with Ray on your computer, and to keep a security record of what our support team did.
• To understand app and website performance and improve Ray using diagnostics and privacy-conscious analytics; advertising measurement applies only where enabled on the website.
• To comply with accounting, tax, payment, consumer protection, and other legal obligations.

Ray can play local files without uploading them. When you affirmatively start a Ray Cloud media feature, Ray sends the material needed for that request over an encrypted connection. Apple-platform clients normally extract and upload the audio needed for speech processing. Android clients may upload the selected audio or media file so Ray Cloud can extract and process its audio track. Ray Cloud may retain account-scoped audio, transcripts, subtitles, and related outputs so you can reuse them for translations, summaries, and assistant features without uploading the same content again.

Nearby features use your local network to discover another Ray device. A TV may send user-selected media or audio to a paired computer for processing. Local-network material is not sent to Ray Cloud unless the selected workflow says it will use Ray Cloud. Protected media or operating-system restrictions may prevent recording, capture, or audio handoff.

If you contact Ray support about a problem, you can choose to let our support team look into it on your computer through a remote support session in the Ray desktop app. A session is never required: we can also help you by email or chat without one. TechSpecs Ltd is the controller for remote support sessions.

A remote support session is not screen sharing. Our team never sees your screen and cannot control your computer. They can only work inside Ray, and Ray shows you everything they do as it happens.

Our team may use automated analysis tools, operated by our service providers under contract, to help analyse session data. If a personal detail slips past automatic removal, for example part of an unusual file name, we do not use it, and it is deleted with the rest of the session data.

How long we keep session data, the legal bases we rely on, and how to ask for a copy or deletion are described under Retention, Legal bases, and Your rights.

When a card payment is routed to SimplePay, card details are entered directly on SimplePay's hosted payment page. We do not receive or store your card number, CVC, or full card credentials.

We use trusted service providers only where they are needed for the service you request.

• TechSpecs Ltd and Stripe for hosted card checkout, payment status webhooks, fraud prevention, and payment-related records when Stripe is selected or routed.
• TECHSPECS Kft., MBH Bank Nyrt., and SimplePay Zrt. for hosted card payments, payment status notifications, and payment-related fraud prevention when MBH Bank VPOS or SimplePay is selected or routed.
• TechSpecs Inc for US operations and payment-related records where it appears as the merchant or customer support entity.
• BTCPay Server or related crypto payment infrastructure when crypto checkout is selected.
• Listmonk and email infrastructure for transactional receipts, product updates, and customer list management.
• Ray Cloud hosting, object storage, queueing, speech, language, and media-processing infrastructure used to perform the cloud feature you request.
• Sentry for mobile and TV crash, performance, and diagnostic reporting. New reports are correlated with a Ray installation identifier rather than an account email or license key.
• Intercom for optional live chat and customer support. Signed-in support profiles may include account email, device/app information, installation identifier, plan, and usage context so support can diagnose the request.
• Service providers that operate automated analysis tools under contract, which our support team may use to help analyse remote support session data.
• Remote support sessions themselves run through our own support service on servers we operate, and test clips come from our own storage.
• Hosting, logging, analytics, spam prevention, and security providers used to operate and protect Ray services and the website.
• Advertising or measurement pixels, including Meta and X, only where they are enabled on the website.

• Contract necessity for checkout, payment, delivery, licensing, support, and account-related communications.
• Contract necessity and your requested action for cloud media processing, generated outputs, account synchronization, and nearby-device workflows.
• Legal obligation for accounting, tax, fraud prevention, chargeback handling, and compliance records.
• Legitimate interests for security, debugging, service improvement, abandoned-cart follow-up, and business analytics.
• Consent where required for optional marketing messages, cookies, or similar tracking technologies.
• Consent for remote support sessions: you start each session, approve the named team member, and choose whether to allow setting changes, a test on one of your own videos, or sharing its subtitles. You can withdraw consent at any time by ending the session. This does not affect what happened before you ended it.
• Legitimate interests for the remote help availability check and the security log of support sessions: keeping our systems and your account secure, and offering remote help only where it works.

We keep personal data only as long as needed for the purpose collected, unless a longer period is required by law. Accounting and payment records may be retained for statutory tax and accounting periods. Support messages are kept while needed to resolve the request and maintain a useful support history. Crash and diagnostic records are kept for a limited operational retention period configured in the diagnostic service.

Pending order records are used to match the payment provider's notification to your checkout details. They are not used to store card details.

Account-scoped cloud audio, transcripts, subtitles, translations, and related media-intelligence outputs are kept while needed to provide the requested reusable feature or until the associated account data is deleted, subject to backup, security, and legal-retention limits. Temporary upload files and presigned download links expire separately from account-scoped stored content.

When Ray confirms owner-account deletion, normal account access is revoked, operational account and cloud-media records are removed, and direct identity fields are removed from limited records retained for accounting, fraud prevention, security, or legal compliance. Intercom places a deleted support contact into a seven-day recovery period before permanently destroying it. A shared-account member deletion removes that member's identity and access without deleting media and account data that remain with the owner.

For remote support sessions in the Ray app, our support service keeps:

• Ray's activity log from a session: up to 14 days after the session ends.
• Other session details, such as device details, test results, and the settings we tried: up to 30 days after the session ends.
• The record of the session, such as when it took place, your Ray version and operating system, your shortened network address, who helped you, the support reference, your choices, and any problem summaries you shared: up to 90 days after the session ends.
• A security log of who did what and when: 24 months. It holds your email address and installation ID only in coded form, and your network address only in shortened form.
• Nothing from the remote help availability check: the installation ID it uses is not stored.

Messages you send in the support chat, including a “[Remote help]” message, are kept like other support messages. The list of past support sessions on your computer is kept for up to 12 months, or until you clear it.

Depending on your location, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data. You can also withdraw consent for optional marketing at any time.

To make a privacy request, contact us at support@rayplayer.com. You may also have the right to lodge a complaint with your local data protection authority.

You can initiate deletion from My Account or Settings in a signed-in Ray app. You can also use the public Ray account-deletion page. Ray sends a fresh verification code and requires an explicit permanent-deletion confirmation. If an active renewal cannot be cancelled automatically, deletion stops and shows the support route without claiming success.

For remote support sessions, you can ask us at the same address for a copy of your session data or for its deletion. We find your sessions using your account email address or your Ray installation ID. Deletion removes your sessions with their activity logs, test results, and choices. The security log is kept for its 24 months because it protects our systems and your account, and it holds no readable email address. You can also end a session at any time with End session, and clear the list of past support sessions in Ray yourself.

Ray Cloud and other internet-facing Ray services use encrypted network connections, access controls, short-lived service links, rate limits, and account-scoped authorization to protect data in transit and restrict service access. Some optional TV-to-computer transfers on the same local network use a local HTTP connection after the devices are paired, so use nearby processing only on a network you trust. No internet or local-network service can guarantee absolute security, so please contact us promptly if you believe your Ray account is at risk.

TechSpecs entities and service providers may process data in countries other than your own. Where required, we use contractual, organizational, and technical safeguards for international transfers.

The website may use cookies, local storage, pixels, and similar technologies for cart behavior, language selection, analytics, fraud prevention, advertising measurement, and customer support. You can manage browser-level cookie settings in your browser. Blocking some cookies may affect checkout or support functionality.

We may update this Privacy Policy as Ray, our checkout, or legal requirements change. The effective date on this page shows when the current version became active.