Site protection data
If you register a site for protection, we store your account ID, normalized hostname and homepage URL, public ownership-challenge token, verification timestamps, activation and pause state, and the one-time credit charge. For trusted Framer responses we also store the site's project identity to apply protection to its alternate domains. We fetch the public homepage when you request verification or activation, using bounded, public-network requests.
Paid registrations stay with the account while the service provides that registration so pause and resume remain free. You can remove unpaid drafts in the dashboard. Contact us about account data, ownership changes or a disputed registration. Credit transaction records follow our billing retention policy.
The optional inline capture helper sends no visitor telemetry, license calls or other network requests. It observes specific local page markers and can show a dismissible notice; it does not send visitor identities or capture attempts to Deframer.
Who we are
Deframer (deframer.co) is run by DeFramer, based in Pakistan, which is responsible for the personal data described here. For anything in this policy, write to mehdi@deframer.co.
Deframer is independent: it is not affiliated with Framer, and Framer receives nothing from us about you.
In short
- Sign-in is handled by Clerk, payments by Polar. We never see your Deframer account password or card details. A Framer site password you enter is used only in memory, to read that site, and never stored.
- We keep the sites you convert and check, linked to your account, so you can reopen them and we can prevent misuse.
- To verify a site, we fetch its published page and look for your code.
- Converted files are deleted 7 days after a conversion finishes. We keep your IP address only as a keyed hash.
- No advertising, no tracking cookies, and we don't sell your data.
What we collect
Your account
Sign-in is handled by Clerk. We receive your user id, your email address and, if your sign-in provider shares them, your name and profile picture. Clerk keeps your password or social sign-in; we never see it.
Your conversions
For each conversion: the address you submitted, the options you chose, its status and timing, the pages it found, diagnostic output (errors and the converter's log), and, once you download it, how you showed you may take the site's code (when your verification code was found, an admin's override, or your confirmation of ownership or permission for a direct download). This is linked to your account so you can reopen your conversions, so we can fix failures, and so we can handle misuse reports.
Site verification
Your verification code is derived from your account id, so we don't store it separately. When you check a site or choose a verified download, we fetch the site's published page, as any visitor would (with the password you enter, for a password-protected site), look for your code, and check that Framer's servers delivered the page. We record the sites your code was found on (when first verified and when last checked); a check that no longer finds it removes the site.
Password-protected sites
If your site is password-protected, you give us its password to convert it. We use it once, in memory, to sign in to the site as its password page does, then discard it. It is never stored in our database, job records, files or logs, and never sent to analytics or error reports. The site session that sign-in gives is held in memory only, until the conversion's worker takes it for that conversion. Wrong attempts are counted per account and per site to prevent guessing, and for a day we note that your account signed in to that site, so other people's wrong guesses can't lock you out.
Purchases and credits
Payments are handled by Polar as merchant of record. We receive the order: its id, the pack, amount, currency and status. Polar collects your payment and billing details; we never see your card. Your credit balance is kept as a ledger of purchases, project downloads, credits returned and adjustments.
Technical data
- IP address. Used to limit how many conversions can be started in a short time and to stop abuse. We store only a keyed hash of it, never the address itself. Our hosting and network providers process it to deliver the site, and Clerk records it with your sign-in sessions to protect your account.
- Cloudflare Turnstile checks that a conversion request comes from a person; Cloudflare processes browser signals to do this.
- Product analytics (PostHog). Which pages you view and key actions on Deframer (starting a conversion, opening the compare view, downloading, starting checkout), plus errors the app runs into, so we can see what works and fix what doesn't. It is kept in memory for the visit only: no cookies or local storage. It reaches PostHog through our own server, which passes on neither your cookies nor your IP address, so PostHog has no location for you either. When you are signed in, these events are linked to your account id and email. Our server also records outcomes linked to your account: your sign-up, the sites you verify, conversions that finish or fail (with the site's domain), projects you unlock for download, and credit packs you buy or get refunded. It never sees your payment details or the files of your conversions.
- Session recordings (PostHog). For some visits, a recording of how the pages were used: where you clicked and scrolled and what the page showed, so we can see where people get stuck. Everything typed into a field is masked, and so are the sign-in screens, your verification code and our admin pages. Recordings never include your browser's console logs. When you are signed in, a recording is linked to your account like the events above. PostHog deletes recordings after its retention period.
- Error reports (Sentry). When something breaks on Deframer, in your browser or on our server, a report of the error: what failed and where in our code, the page address (with any sign-in codes removed), your browser and operating system, and, when you are signed in, your account id. Never your IP address, cookies, email, request bodies (so never a site password you enter) or the files of your conversions. A small share of page loads and requests also report how long they took, so we can find slow ones.
The sites you convert
Deframer reads only what a site publishes to its visitors: for a password-protected site, what a visitor sees after entering the password. The converted project and its .zip are stored on our server or in Cloudflare R2 object storage, are private to your account, and are deleted 7 days after the conversion finishes; the storage bucket deletes any download left behind a day later. A live preview, when there is one, is deleted 10 minutes after it is ready, however long you view it.
Files fetched from a site may be kept on our server as a cache, so a repeat conversion of the same published version is faster: the site's published code and page data, and the files it loads from Framer's CDN and package registries. For a password-protected site, that includes what was read with its password, never the password itself. The cache is never shown to anyone, and a conversion uses it only after reading the live site again (for a protected site, with its password). It is emptied when it grows past its size limit.
How we use it
- To run the service: sign you in, verify sites, convert them, show your conversions, sell and track credits.
- To keep it safe and fair: rate limits, abuse prevention, handling misuse reports, fixing failed conversions, service statistics.
- To meet legal and accounting obligations for purchases.
Where data protection law asks for a legal basis, these are: performing our contract with you; our legitimate interests in a secure service free of misuse; and our legal obligations. We don't sell your data or use it for advertising.
Who processes data for us
- Clerk: accounts and sign-in, including the IP address and device of each session, for security.
- Polar: checkout, payments, tax, receipts and refunds, as merchant of record. Polar handles payment data as its own controller, under its privacy policy.
- Cloudflare: DNS, Turnstile, and R2 storage for downloads and database backups.
- Fly.io: hosting of the app, its database and working files, in the United States (Ashburn, Virginia).
- PostHog: product analytics and error reports, in the United States.
- Sentry (Functional Software, Inc.): error reports, in the United States.
- Google PageSpeed Insights: speed tests, when they are on. Google receives the address of the site you converted and of its converted preview, and loads those pages to measure them. Neither is sent for a password-protected site.
How long we keep it
- Converted projects and downloads: as above, 7 days after the conversion finishes (previews as described there).
- Your conversions (address, status, diagnostics, log, how ownership was shown): listed for up to 14 days after they end. After that, a minimal record (address, status, timing, errors, your user id and how ownership was shown) is kept for 400 days for service statistics and to handle misuse reports; the step-by-step timeline of each conversion for 90 days.
- Sites your code was found on: until a check no longer finds it, or your account is deleted.
- Rate-limit records (keyed hashes): removed once the 10-minute window has passed.
- Session recordings and product analytics events: deleted by PostHog after its retention period.
- Account data: while your account exists.
- Orders and the credit ledger: as long as accounting and tax law require.
- Records of actions our admins take (such as on a misuse report): as long as needed for security and to handle disputes.
- Database backups: daily snapshots, kept for 7 days.
Your rights
Depending on where you live, you can ask to access, correct, export or delete your data, and to object to or restrict how it is used. Write to mehdi@deframer.co from the email address on your account; we answer within 30 days. You can also complain to your local data protection authority.
Deleting your account
Ask us at mehdi@deframer.co from the email address on your account. We delete your account, your conversions and your verified sites. We keep orders and ledger entries that accounting law requires, and records needed to handle a misuse report that is open, for the periods above.
Children
Deframer is not for anyone under 18, and we don't knowingly collect data about children.
International transfers
We are based in Pakistan, and our providers process data in the United States and other countries. Where the law requires it, these transfers rely on the safeguards the providers offer, such as standard contractual clauses.
Security
Everything travels over HTTPS. Conversions are private to the account that made them; conversions run in isolated processes; our own records hold IP addresses only as keyed hashes; and only our admins can see the records described here.
Changes
We update this page when what we collect or who processes it changes, and change the effective date at the top. See also the terms of service and the refund policy.