Legal
Privacy Policy — Clonecode
Last updated: November 2, 2026 · Version: 1.1
1. Controller and contacts
The controller of your personal data (under the Brazilian LGPD and, where it applies, the GDPR) is Codai Tech (38.927.150 Eduardo Felipe Freire, CNPJ 38.927.150/0001-18), São José dos Campos, SP, Brazil, which operates Clonecode at getclonecode.com.
Privacy contact: privacy@getclonecode.com. Data Protection Officer / Encarregado: Eduardo Felipe Freire, privacy@getclonecode.com.
2. Data we collect
| Data | Source | Why |
|---|---|---|
| E-mail address, user ID, language | You | Login by magic link, delivery of results, account, transactional e-mails |
| Acceptance and consent records: purpose (terms or marketing), version/hash of the text shown, language, page, date/time, truncated IP (last part removed) | You / our systems | Proof of consent and acceptance |
| URLs you submit and the host | You | To run the job; abuse prevention |
| Job report and progress (steps, counts of files, errors) | Our systems | To show you the result and support you |
| The copy itself (mirror, kit, preview) | Public pages you asked us to copy | To deliver the service; kept 14 days |
| Editor edits: the changes you make to a copy (texts, links, the choice made for each element, image focal points), version number and dates | You | To provide the editor (see 2.4) |
| Files you upload in the editor (images and videos), with type, size, dimensions and a fingerprint (hash) of the file | You | To show them in your edited copy and build the edited site (see 2.4) |
| Abuse and audit logs: IP address, requested host, action, result code, date/time | Our systems | Fraud, phishing and abuse prevention |
| Abuse reports sent through our form or by e-mail: URL, reason, details, and your e-mail if you give it | You | Handling the report (see the Takedown and Abuse Policy) |
| Purchase and credit ledger: product, amount, currency, payment ID, status, credit movements | Us / Stripe | Delivering credits; tax and accounting |
| Application logs (request ID, user ID, error code, duration) | Our systems | Operation and security. No e-mail, no full URL with query, no page body |
| Basic usage events (e.g. "checkout started", "download") | Our systems | Operating and improving the product |
| First-party visit statistics (daily counts by page, referrer host, country/region/city) | Our systems, from our host's geolocation headers | Aggregate traffic. No cookie, no IP stored (see 2.2) |
| Sign-in request log: e-mail, date/time, language, page (landing or login), approximate location (country/region/city) | You / our host's geolocation headers | Security, abuse prevention and support (see 2.3) |
| Approximate sign-up location (country/region/city) on your profile | Our host's geolocation headers | Understanding where customers come from; abuse prevention (see 2.3) |
| Ad click identifier and conversion event (order value, currency, our checkout ID) | Google tag, when you arrive from a Google ad and when a purchase completes | Measuring the performance of our Google Ads (see 2.1) |
Meta Pixel events (page view, sign-up, purchase with order value, currency and our checkout ID) and the _fbp / _fbc cookies | Meta Pixel, on public pages, after your first sign-in and when a purchase completes, only outside the EEA, UK and Switzerland | Measuring the performance of our Facebook and Instagram ads (see 2.1.1) |
We do not receive or store payment card data; it goes directly to Stripe.
Page content you ask us to copy may incidentally contain personal data of third parties that is publicly visible on that page. We process it only to deliver the copy to the user who requested it, we do not use it for any other purpose, and we delete it after 14 days. If you find your personal data in a copy, write to privacy@getclonecode.com or use the Takedown and Abuse Policy.
2.1 Google Ads conversion measurement
When you visit our public pages (home, pricing, legal pages) and when you return from a completed checkout, we load the Google tag (gtag.js) from Google. If you arrived by clicking one of our Google ads, the tag stores the ad click identifier in first-party cookies on our domain (such as _gcl_aw / _gcl_au, which Google keeps for about 90 days). After a purchase, we send Google one conversion event with the order value, the currency and our checkout session ID (so Google does not count the same purchase twice). We never send your e-mail address or other contact data to Google. Google also receives the technical data any web request carries (IP address, browser information).
- Purpose: only to measure how our ads perform (which ads lead to purchases).
- No remarketing or personalised advertising: ad personalisation is turned off for everyone, Google signals are off, and the ad click ID is not passed along in page links.
- EEA, United Kingdom and Switzerland: advertising storage is denied (Google Consent Mode). No advertising cookies are set and ad identifiers are redacted; Google may still receive limited cookieless signals from the tag, without identifiers.
- The tag is not loaded in the logged-in app (except the purchase confirmation return) or in the admin area.
- Google's privacy policy: https://policies.google.com/privacy. How Google uses data from sites that use its services: https://policies.google.com/technologies/partner-sites
2.1.1 Meta Pixel (Facebook and Instagram ads)
Outside the EEA, the United Kingdom and Switzerland, we use the Meta Pixel from Meta Platforms to measure our ads on Facebook and Instagram. It is loaded only on our public pages (home, pricing, legal pages), on the first page of the app right after you create your account, and when you return from a completed checkout. It sends Meta a page view on public pages, one sign-up event (Complete Registration) when a new account signs in for the first time, and one purchase event with the order value, the currency and our checkout session ID. Each sign-up and purchase event carries a random event ID or our checkout ID so Meta does not count it twice. The pixel stores a first-party cookie on our domain (_fbp, and _fbc if you arrived from a Meta ad link; Meta keeps them for about 90 days). Meta also receives the technical data any web request carries (IP address, browser information) and the address of the page.
- Purpose: only to measure which ads lead to sign-ups and purchases.
- No advanced matching: we never send your e-mail address, name, phone or other contact data to Meta, and we do not use the pixel's automatic events, which read buttons and forms on the page.
- Not loaded in the EEA, United Kingdom and Switzerland: our server checks your approximate country (from our host's geolocation headers) before anything from Meta loads. If the country is unknown, the pixel is not loaded either. On public pages our server records this decision in a first-party cookie (
cc_mp, value1, 1 day, no personal data) that only tells your browser it may load the pixel; it is removed as soon as a request comes from a country where the pixel is not allowed. - To mark a new account, we set a short-lived first-party cookie (
cc_meta_reg, 10 minutes) that holds only a random event ID, and delete it as soon as the sign-up event is sent. - The pixel is not loaded anywhere else in the logged-in app or in the admin area.
- Meta's privacy policy: https://www.facebook.com/privacy/policy. Meta acts as joint controller with us for the collection and transmission of pixel data, and as an independent controller for its own processing afterwards.
2.2 First-party visit statistics
On our public pages our own server counts visits without cookies and without any script in your browser. We store only daily aggregated counts by page, referrer host (for example google.com), and country, region and city as estimated by our hosting provider's geolocation headers. We do not store your IP address. To count unique visitors per day, a one-way hash of IP address, browser string and date is combined with a random salt that changes every day; these salted hashes and the salts are deleted after 2 days. Bots and link previews are not counted.
2.3 Sign-in request log and sign-up location
When you request a sign-in link we log the e-mail address, date/time, language, the page you used and your approximate location (country/region/city from our host's geolocation headers, never the IP address). We keep this log for 90 days for security, abuse prevention and support (for example, to check whether a sign-in e-mail was requested). When an account is created, the same approximate location (country/region/city) is stored on your profile.
2.4 Editor
When you edit a copy, we store your edits in our database and the files you upload in private storage (Supabase), linked to the copy and to your account. We process them only to provide the editor: saving your work, showing your preview and building the edited site you download. We do not use them for advertising or profiling, we share them only with the providers in section 6, and we do not use them to train AI models. Before storing a JPEG, PNG or WebP image we re-encode it to remove hidden metadata (such as GPS location and device name); SVG files are cleaned of scripts and other active content. Uploaded files are private: only you can see them in the app, through short-lived signed links.
Files you upload may contain personal data, including photos of people. Upload only what you have the right to use; if a photo or video shows someone else, you are responsible for having their permission (see the Terms, section 4).
Photo effects in your browser. Some effects (for example turning a photo into a 3D face) prepare your photo in your own browser. The original photo is not sent to us; only the final images you confirm are uploaded, like any other editor file. To run the effect, your browser downloads the AI models it uses from Hugging Face (huggingface.co), which receives the technical data of that download (IP address, browser information) but never your photo.
3. Why we use it and the legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Create account, login, deliver kit | E-mail, ID, language, job data | Performance of a contract (LGPD art. 7, V; GDPR art. 6(1)(b)) |
| Run and deliver copies | URL, copy, report | Performance of a contract |
| Provide the editor (save edits, store and show uploaded files, build the edited site) | Editor edits, uploaded files | Performance of a contract |
| Take payment, grant credits, handle refunds | Purchase and ledger data | Performance of a contract; legal obligation (tax) |
| Proof of terms acceptance | Consent record | Legitimate interest and the exercise of rights in legal proceedings (LGPD art. 7, VI and IX; GDPR art. 6(1)(f)) |
| Marketing e-mails | E-mail, consent record | Consent, given by an unticked box, separate from accepting the Terms. Withdraw anytime in one click |
| Transactional e-mails (login, receipt, copy ready, expiry notice) | Performance of a contract. They contain no offers | |
| Abuse, phishing and fraud prevention, security | IP, host, logs, abuse reports | Legitimate interest (LGPD art. 7, IX; GDPR art. 6(1)(f)) |
| Tax and accounting | Purchases, ledger | Legal obligation (LGPD art. 7, II; GDPR art. 6(1)(c)) |
| Product operation and improvement | Usage events, logs | Legitimate interest |
| Visit statistics (aggregate) | Daily counts, salted daily hash | Legitimate interest |
| Sign-in security and support; approximate sign-up location | Sign-in request log, profile location | Legitimate interest |
| Measuring Google Ads performance | Ad click ID cookie, conversion event (value, currency, checkout ID) | Legitimate interest; in the EEA, UK and Switzerland no advertising cookies are set |
| Measuring Facebook and Instagram ad performance | Meta Pixel events (page view, sign-up, purchase value, currency, checkout ID), _fbp / _fbc cookies | Legitimate interest; not loaded in the EEA, UK and Switzerland |
We do not sell personal data. Our engine automatically refuses certain pages (for example pages with password fields or on our high-risk blocklist), and our systems may automatically block activity that looks like abuse. These decisions depend on the page or the activity, not on a profile of you. You can ask a person to review any automated refusal or suspension by writing to hello@getclonecode.com.
4. Marketing
We send marketing only if you tick the marketing box (unticked by default). The e-mail you give for login and delivery is not consent for marketing. Every marketing message has a one-click unsubscribe and states why you receive it. Unsubscribing from marketing does not stop transactional e-mails. A spam complaint stops marketing permanently. We keep a record of your consent (text hash, date, truncated IP).
5. Retention
| Data | Retention |
|---|---|
| Copy (zip, mirror) and preview | 14 days, then deleted from storage. Notice about 48 hours before |
| Account data (e-mail, language) | While the account exists; deleted within 15 days of a deletion request |
| Editor edits and files uploaded in the editor | While the copy is kept (14 days); deleted when the copy expires. An uploaded file is deleted sooner when you remove it in the editor; everything is deleted with the account, or sooner on request |
| Marketing consent records | Up to 5 years after withdrawal, as proof of consent |
| Abuse/audit logs (with IP) | 180 days |
| Abuse reports and actions taken | Up to 5 years |
| Purchases and credit ledger | 5 years, for tax and accounting obligations. On account deletion we remove your e-mail and identifiers from these records (anonymisation) and keep the financial record |
| Application logs | Up to 30 days |
| Visit statistics | Daily aggregated counts are kept as statistics (they do not identify anyone); salted daily visitor hashes deleted after 2 days |
| Sign-in request log | 90 days |
| Approximate sign-up location | While the account exists |
| Google Ads click ID cookies | About 90 days in your browser; data Google receives follows Google's own retention |
Meta Pixel cookies (_fbp, _fbc) | About 90 days in your browser; data Meta receives follows Meta's own retention. Our cc_meta_reg cookie: up to 10 minutes; our cc_mp cookie: 1 day |
| Database backups | Hold database records only: metadata about copies and uploaded files (paths, sizes) and your editor edits, never copy contents or uploaded files; rolling backups kept for up to 7 days |
When a retention period ends, the data is deleted or anonymised. Deleted data may remain in rolling backups until they are overwritten, within the period above.
6. Who receives your data: processors and sub-processors
| Provider | Role | Data | Location |
|---|---|---|---|
| Vercel | App hosting | Requests, logs | United States (global edge network) |
| Supabase | Database, authentication, file storage | Account, jobs, ledger, copies, editor edits and uploaded files | United States |
| Hostinger | Virtual server we operate, which runs the copy jobs | URLs, copy contents (temporary) | United States |
| Cloudflare | DNS and Turnstile (bot check) | IP, request signals | Global |
| Hugging Face | Serves the AI models that photo effects in the editor run in your browser (see 2.4) | IP address and browser data of the model download; never your photo | Global / United States |
| Resend | Transactional (and marketing, with consent) e-mail | E-mail address, message content | United States |
| Stripe | Payments | Payment and billing data, e-mail | United States and Brazil |
| Google (Google Ads, Google tag) | Ad conversion measurement | Ad click ID, conversion event (value, currency, checkout ID), IP address and browser data | Global / United States |
| Meta Platforms (Meta Pixel) | Facebook and Instagram ad measurement (not loaded in the EEA, UK and Switzerland; no advanced matching) | Page view, sign-up and purchase events (value, currency, checkout ID), _fbp / _fbc cookies, page address, IP address and browser data | Global / United States |
We may also disclose data to comply with law, court orders or requests from competent authorities, to protect rights and prevent abuse, and to a successor in a merger or sale of the business, which would remain bound by this policy. Stripe, Google and Meta may also act as independent controllers for their own purposes, under their own privacy policies.
7. International transfers
Most of our providers process data outside Brazil, mainly in the United States. These transfers are necessary to provide the Service you asked for (LGPD art. 33, IX; GDPR art. 49(1)(b)) and are covered by the data protection terms our providers offer to their customers.
8. Cookies and similar technologies
We use the minimum necessary:
- Strictly necessary: session cookies for login (HttpOnly, Secure), a short-lived cookie that ties a sign-in link to the browser that asked for it (1 hour), a "signed in" hint cookie with no personal data (30 days), a language preference cookie (1 year), and Cloudflare Turnstile on forms for bot protection.
- Analytics: our own visit counter, with no cookie (see 2.2).
- Advertising measurement: on public pages and on the purchase confirmation return, the Google tag may set first-party cookies with the ad click identifier (such as
_gcl_aw/_gcl_au) to measure our Google Ads conversions, never for remarketing or personalised ads. Not set for visitors in the EEA, UK and Switzerland (see 2.1). - Advertising measurement (Meta): outside the EEA, UK and Switzerland, the Meta Pixel may set first-party cookies (
_fbp, and_fbcafter a Meta ad click) on public pages, after your first sign-in and on the purchase confirmation return, to measure our Facebook and Instagram ads, never for advanced matching. We also setcc_meta_reg(up to 10 minutes, random ID only) to send the sign-up event once, andcc_mp(1 day, value1only) so public pages know the pixel is allowed in your country (see 2.1.1).
You can delete or block cookies in your browser settings; the login will not work without the strictly necessary cookies.
9. Your rights
Under the LGPD, the GDPR and similar laws, depending on where you live, you may ask to: confirm that we process your data and access it; correct it; delete or anonymise it; receive it in a portable format; object to or restrict processing; withdraw consent at any time (without affecting prior processing); get information on who we shared it with; and request review of automated decisions. You may also complain to your data protection authority (in Brazil, the ANPD; in the EU, your national authority).
To exercise your rights, write to privacy@getclonecode.com from the account e-mail. We may need to verify your identity. We answer within 15 days. Some data must be kept by law (for example tax records) and cannot be deleted on request; we will tell you when that is the case.
10. Security
We use access controls, row-level security in the database, private storage, short-lived signed download links, isolated per-job execution, filtered network egress, and logs without sensitive data. No system is perfectly secure. If a security incident may cause relevant risk or harm to you, we will notify you and the competent authorities (in Brazil, the ANPD) within the deadlines set by law.
11. Children
The Service is for people aged 18 or over and is not directed to children or teenagers. We do not knowingly collect their data; if we learn that an account belongs to someone under 18, we close it and delete its data.
12. Changes
We will update this policy as the Service evolves. We will announce material changes by e-mail or on the site at least 15 days before they take effect. The version date is at the top.
13. Contact
Codai Tech (38.927.150 Eduardo Felipe Freire, CNPJ 38.927.150/0001-18) · São José dos Campos, SP, Brazil · privacy@getclonecode.com · DPO/Encarregado: Eduardo Felipe Freire, privacy@getclonecode.com.