Last updated: November 18, 2026
Privacy Policy
1. Scope and roles
This Policy explains how raw2ads collects, uses, discloses, and retains personal data when you use app.raw2ads.com, raw2ads.com, and the Service. It applies alongside the Terms of Service, Acceptable Use Policy, and Refund Policy.
For account, billing, security, support, and product operations, raw2ads is generally the controller (or equivalent business) of the data described here. If an organization instructs raw2ads to process personal data contained in its workspace, raw2ads may act as its processor/service provider; a data-processing agreement is available on request at hello@raw2ads.com. A user uploading someone else's data is responsible for having a lawful basis, notices, and instructions for that upload.
2. Data we collect and sources
- Account and authentication: email address, magic-link events, account identifier, workspace and plan details. Collected from you and your organization.
- Content and instructions: video, images, audio, voice-overs, music, prompts, text, brand assets, reference/competitor ads, metadata, and Outputs. These may contain faces, voices, names, contact details, or other personal data. Collected from you or your organization, or from your Google Drive when you import files you select (see Section 6).
- Usage and billing: feature events, job status, fair-use consumption, plan, invoices, transaction identifiers, refunds, chargebacks, and limited payment metadata. Our payment processor (Stripe) or the Merchant of Record (Creem) handles full payment credentials; they never touch raw2ads servers.
- Technical and security data: IP address, timestamps, browser/device information, approximate location derived from IP, cookies/local storage, logs, error reports, and security events.
- Communications: support requests, feedback, and information you provide in correspondence.
We may receive data from authentication, hosting, AI, email, analytics, payment, and other providers used to operate the Service. We do not intentionally request government identifiers, health data, or other sensitive data. Do not upload such data unless the feature requires it and you have a documented lawful basis.
3. How we use data and legal bases
- authenticate users, provide workspaces, process uploads, run requested AI/editing features, store and export files, and provide support - contract or steps requested before contract;
- administer trials, fair-use limits, subscriptions, invoices, taxes, refunds, and fraud/chargeback prevention - contract and legal obligation, with legitimate interests for fraud prevention;
- secure the Service, detect abuse, enforce the Terms, troubleshoot, and maintain reliability - legitimate interests and legal obligation where applicable;
- measure and improve the Service using aggregated or appropriately de-identified information - legitimate interests or consent where required;
- send service, security, billing, and legal messages, and a short onboarding email sequence during the trial (with an unsubscribe link for non-essential messages) - contract or legitimate interests; optional marketing requires consent or another lawful permission;
- comply with legal obligations and respond to lawful requests - legal obligation.
Where consent is the basis, you may withdraw it at any time; withdrawal does not affect earlier processing. We do not use your data to make solely automated decisions that produce legal or similarly significant effects.
4. Content, faces, voices, and biometric processing
Uploads containing a face or voice are personal data where a person is identifiable. raw2ads does not use uploads to uniquely identify people, authenticate them, or create biometric templates. A face image or voice recording can nevertheless be subject to additional biometric or sensitive-data rules depending on the technical processing and purpose. If a future feature would create or use biometric identifiers, we will complete a separate legal and risk assessment, provide the required notice, and obtain any required consent before enabling it.
You must obtain the necessary permissions and notices from people appearing in content. You must not upload content that you are not entitled to process or that violates the Acceptable Use Policy.
5. AI and service providers
We share the minimum data needed for the feature and route you select. Providers currently used to operate the Service:
| Provider | What it does | Data involved |
|---|---|---|
| Supabase | Sign-in (email magic links) and authentication records | Email address, authentication events |
| Resend | Transactional and onboarding email | Email address, message content |
| OpenRouter, routing to the model provider for the requested feature (for example Google Gemini) | AI analysis of clips and reference ads, tagging, suggestions, translation | The clips, frames, text, or prompts needed for the requested feature |
| Higgsfield, fal.ai, ElevenLabs (optional) | AI clip, image, or voice generation, only when you enable the feature or connect your own key (BYOK) | Content needed for the requested generation; with BYOK, your own agreement with the provider applies |
| OVHcloud (data centre in Singapore) | Application hosting and storage of uploaded content, Outputs, and workspace data | All workspace content and account data |
| Cloudflare | DNS, CDN/security proxy, hosting of the marketing site, and encrypted backup storage (R2) | Technical request data; encrypted backup archives |
| Hetzner Online GmbH (data centres in the European Union) | Encrypted backup storage of uploaded content and Outputs | Encrypted backup archives |
| Umami (self-hosted on our own infrastructure) | Cookieless, privacy-focused usage statistics | Anonymized usage events; nothing is shared with a third-party analytics company |
| Stripe (stripe.com), our payment processor for purchases sold directly by AdsCaffeine LLP | Card payment processing, subscription billing and renewals, refunds, fraud prevention, chargebacks, and payment-related tax records, on our behalf | Billing details and transaction data; card details are entered on Stripe's payment form and full card data never touches raw2ads servers |
| Creem (creem.io), Merchant of Record for purchases sold through the Creem checkout | Payment, tax, invoicing, subscriptions, refunds, fraud, and chargebacks, as seller of record | Billing details and transaction data; full card data never touches raw2ads servers |
We do not use Your Content to train our own machine-learning models. AI providers process content to deliver the result you request, under their API terms; where a provider offers API terms or settings that exclude API content from model training, we rely on those. With BYOK, your own agreement with that provider applies. Provider names, routes, and settings can change; we will keep this table current or provide any legally required notice.
6. Google Drive integration
raw2ads can connect to your Google Drive so you can import videos from it and, when that option is available, save finished videos to it. raw2ads requests only one Google permission (OAuth scope), https://www.googleapis.com/auth/drive.file. With this permission raw2ads can access only the files you select in Google's own file picker and the files raw2ads creates in your Drive. raw2ads cannot see, list, or open any other file in your Drive.
- Import from Google Drive: when you click "From Google Drive", Google's own file picker opens and you choose the video files to import. For each file you select, raw2ads reads its name, size, file type, and content, and downloads a copy into your raw2ads library on raw2ads servers. From then on the copy is treated like any other video you upload: it is processed to provide the features you use, including AI analysis by the providers listed in Section 5, and it is kept and deleted under the rules for uploaded content in Section 10.
- Save to Google Drive (coming soon): only when you click "Save to Drive" on a finished video, raw2ads creates that video file in your Google Drive. raw2ads does not create, change, or delete any other file in your Drive.
- Access tokens: Google gives your browser a short-lived access token, valid for about one hour. raw2ads uses it only to download the files you selected, or to upload the video you chose to save, and keeps it only in memory or in temporary job storage for the duration of that transfer. raw2ads never writes the token to disk or to logs, and discards it when the transfer ends and in any case within one hour. raw2ads does not request offline access and does not store refresh tokens.
- Revoking access: you can remove raw2ads's access to your Google account at any time at myaccount.google.com/permissions. Videos already imported stay in your raw2ads library until you delete them there.
raw2ads does not sell Google user data, does not use or transfer it for advertising, and does not use it to develop, improve, or train generalized AI or machine-learning models. People at raw2ads do not read Google user data unless you give us your consent, it is necessary for security purposes (for example, investigating a bug or abuse), it is necessary to comply with applicable law, or the data is aggregated and anonymized and used for internal operations as allowed by this Policy.
raw2ads's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
7. Meta (Facebook) integration
If you choose to connect your Meta account with the "Create ad on Meta" feature, raw2ads receives from Meta, with your permission: your Meta user ID and name, the list of ad accounts, campaigns and Ad Sets you can access, and the list of Facebook Pages you manage (ID and name). We use this data only to let you choose where to place a video ad and to create that ad, always in paused status, in your ad account. We store an encrypted access token so you do not need to reconnect every time. We do not sell this data, we do not use it for advertising, and we do not share it with third parties other than Meta.
You can disconnect Meta at any time from the "Create ad on Meta" dialog, which deletes the stored token. You can also remove raw2ads from your Facebook settings (Settings and privacy > Settings > Your activity > Business integrations); when you do, Meta notifies us and we delete the data we received from Meta. To request deletion by email, write to hello@raw2ads.com and we will delete your Meta data within 30 days and confirm it to you.
8. Sharing and disclosure
We disclose data to the providers above, our professional advisers, auditors, insurers, payment/fraud partners, and authorities or other parties where required by law, to protect rights and safety, or as part of a merger, financing, or sale of assets. We do not sell personal data for money, and we do not share personal data for cross-context behavioural advertising.
9. International transfers
Uploaded content and workspace data are hosted in Singapore (OVHcloud). Encrypted backups are stored in the European Union (Hetzner) and with Cloudflare. Some providers process data in the United States or other countries. Where required, we rely on an adequacy decision or another lawful transfer mechanism, such as the applicable EU/UK Standard Contractual Clauses or equivalent safeguards. Contact us for current transfer information.
10. Retention and deletion
- Account and workspace data: while the account is active, and deleted after account closure or on request, subject to the periods below.
- Uploaded content and Outputs: until you delete them or close the account, then removed from active systems within 90 days. Once removed from active systems, they are also removed from our encrypted backups automatically, on a rolling schedule, normally within about 90 days.
- Inactive and expired-trial accounts: if a trial ends without an active subscription, the account and its uploaded content may be deleted after 30 days of inactivity to free up storage, with advance notice by email where practical.
- Logs, usage, and security records: typically up to 12 months.
- Billing, tax, and fraud records: as long as required by law.
- Support communications: up to 24 months after resolution.
Deletion from raw2ads does not necessarily cause immediate deletion from a provider that has already received data; we apply our provider deletion processes and disclose relevant limits where required. You may request deletion at any time, subject to lawful exceptions.
11. Your rights
Depending on your location, you may have rights to access, correct, delete, restrict, object, portability, withdraw consent, and complain to a supervisory authority. Email hello@raw2ads.com; we may verify your identity and will respond within the period required by law. If you use the Service through an organization, send content-data requests to that organization first where it is the controller.
EU/EEA/UK: you can lodge a complaint with your local data-protection supervisory authority.
California and other US states: rights to know/access, delete, correct, opt out of sale/sharing, limit sensitive-data use, or appeal may apply. We do not sell personal data for money and do not share it for cross-context behavioural advertising. To exercise a right or appeal a decision, email hello@raw2ads.com.
12. Security
We use measures appropriate to the risk, such as HTTPS, access controls, magic-link authentication, per-user workspace isolation, provider permissions, logging, and encrypted backups. No system is completely secure. Report suspected unauthorized access to hello@raw2ads.com promptly. We will handle and notify qualifying incidents as required by law.
13. Cookies and similar technologies
We use strictly necessary cookies and local storage for sign-in, security, session continuity, and preferences. Analytics is self-hosted Umami and is cookieless: it sets no cookies, uses no advertising identifiers, and shares nothing with third-party analytics companies. We do not use advertising cookies. Because only strictly necessary cookies and cookieless analytics are used, no cookie banner is shown; if this ever changes, we will update this Policy and add any required consent mechanism first.
14. Children
The Service is not directed to, and may not be used by, anyone under 18. If we learn that we collected a child's personal data contrary to applicable law, we will take reasonable steps to delete it. Contact hello@raw2ads.com.
15. Changes and contact
We may update this Policy and will post the new effective date. For material changes, we will provide notice through the Service or by email where required. Questions, rights requests, and complaints: hello@raw2ads.com - AdsCaffeine LLP, 5307 Victoria Drive #485, Vancouver, BC V5P 3V6, Canada.