Privacy policy

Last updated: 23 October 2026

This policy describes how Scrollify ("we", "us") handles personal data when you use scrollify.io (the "Service").

1. Data we collect

  • Account data: email address, password hash (never the raw password), plan, and optional profile fields you provide. If you sign in through Google, GitHub, X, or Discord, we receive your name, email, and account identifier from that provider. We do not receive your password for those services.
  • Sign-in activity: a record of sign-ups, sign-ins, sign-outs, and failed sign-in attempts. Each record includes the email address used, the sign-in method, the outcome or failure reason, the IP address, the browser user agent, and the time. We use these records to detect account takeover and abuse.
  • Plan and trial data: your current plan, billing status, and, if you redeem a Pro trial code, which code you redeemed, when, and when the trial ends.
  • Dark Web (.onion) capture records: if you use .onion capture, we record your acceptance of the acceptable-use attestation (account, attestation version, IP address, user agent, and time). We also log every .onion capture attempt (account, URL, outcome, and time).
  • In-app notifications: service messages we show you in the app, such as export-ready alerts, and whether you have read them.
  • Job data: the public URLs you submit for export, the configuration you choose (preset, format, duration), job status, and the output files we generate. URLs are stored to show your export history and to allow re-queueing.
  • Image uploads: product or other photos you upload for Image Auto-Crop and E-Commerce Image Preparation (JPG, PNG, WebP, or ZIP batches), plus the processing options you choose (crop, padding, canvas, format, marketplace preset) and the derived output files we generate. These files may include personal or product imagery you choose to upload.
  • Guest demos (no account): if you try a free watermarked scroll export or guest image convert without signing in, we process the public URL or uploaded images you submit, generate a short-lived output file, and store a temporary job record so you can preview, download, or later claim the file into an account. Guest demos are watermarked and time-limited.
  • IP address: we collect your IP address (or the address reported by our CDN / reverse proxy) on API requests, including guest demos, authentication, exports, and contact submissions. We use it for security, rate limiting, abuse prevention, and to bind anonymous guest-demo quotas so clearing cookies or changing network identity alone does not reset fair-use limits. We store a one-way hash of the IP for guest-demo quota and event records rather than the raw address in those tables; raw IPs may still appear briefly in technical server logs.
  • Session data: an HTTP-only session cookie and a short-lived token issued on login. These are used solely for authentication and expire on logout or after a period of inactivity.
  • Guest demo cookie: an HTTP-only sl_guest cookie that identifies your anonymous demo session in the browser. It does not sign you in. Combined with your IP hash, it enforces per-visitor demo limits. Clearing site cookies starts a new browser identity, but IP-based limits may still apply.
  • Contact form: name, email address, and message content when you contact us.
  • Technical logs: server-side request logs (IP address, timestamp, endpoint) retained for security, abuse prevention, and operational diagnosis.
  • Landing-page analytics: when you visit our marketing pages, we record page views and funnel steps (for example, a button click, starting a tool, or downloading a demo export). Each record includes the page path, a random visitor key, a one-way hash of your IP address, and the time. We use these records only in aggregate, to understand which pages work. They are not used for advertising or shared with ad networks.
  • Cookie consent: your consent or refusal for optional analytics cookies, stored locally.

2. How we use your data

  • Providing the Service: processing export jobs, storing outputs, authenticating sessions, and sending transactional emails (password reset, export-ready notices).
  • Content moderation, research and improvement: content processed through the Service — including submitted URLs, uploaded files, and the exports we generate — is moderated. That means our team and automated systems may view it to enforce our terms and keep the Service safe, and may use it for research and to improve the Service (for example, capture quality, failure handling, and new features). Moderation access is limited to people who need it, and we do not sell your content.
  • Guest try-before-signup: running a limited number of watermarked demos, enforcing fair-use quotas (per guest cookie and per IP), offering a short download window, and optionally attributing a later signup to a prior demo session so we can improve onboarding (aggregate metrics only for CMS operators).
  • Image preparation: running server-side image processing on uploaded files to crop, normalize canvases, convert formats, and deliver a ZIP download for your batch.
  • Security and abuse prevention: rate limiting, IP-level blocking of private-network access attempts, guest-demo quota enforcement, sign-in monitoring, prevention of repeat trial or free-account abuse, and detection of misuse.
  • Legal compliance: keeping .onion attestation and capture records, enforcing our terms of use, and responding to valid legal requests.
  • Service improvement: aggregated, internal analysis of failure patterns to improve export reliability. No individual URL or personal data is shared externally for this purpose.
  • Billing: subscription management via our payment processor(s). We do not store full card details on our servers.
  • Communication: responding to contact form submissions and sending service notices where necessary.

3. Legal bases (GDPR)

We process your data to perform our contract with you (providing exports, maintaining your account), to pursue legitimate interests (security, fraud prevention, fair-use enforcement for free demos, service improvement), and where required by law. Pre-contractual steps — such as a free guest demo before you create an account — are processed on that basis or on legitimate interests in preventing abuse of free compute. Transactional emails are sent on a contract basis. Optional analytics cookies rely on your consent, which you can withdraw at any time by clearing site data or adjusting your browser settings.

4. Public share links

When you generate a public share link for an export, the linked file becomes accessible to anyone who has the URL. Share links do not expose your account details, email, or any metadata about you. You can stop sharing at any time by removing the share link from your library.

5. Third-party processors

We use third-party services to operate the Service. These include payment processors, email delivery providers, sign-in providers (Google, GitHub, Discord), hosting and infrastructure providers, and network or proxy providers through which pages are loaded for capture. Capture providers receive the URL being captured, not your account details. These processors handle data only as we instruct and under appropriate data protection agreements. We do not sell or rent your personal data, and we do not share it for cross-context behavioural advertising.

We may also disclose data when the law requires it, when we receive a valid legal request, or when needed to protect the safety, rights, or property of our users, the public, or Scrollify. This includes reporting illegal content to the relevant authorities. If we are involved in a merger, acquisition, or sale of assets, your data may transfer to the new owner under this policy, and we will notify you.

6. Retention

  • Account and job data: retained while your account is active. When you delete your account, your exports, uploaded files, presets, and API keys are removed immediately and the account record is anonymised. Copies may persist in backups for a limited period.
  • Account deletion record: when an account is deleted we keep a short record (email address, plan, sign-up and deletion dates, number of exports, and whether a subscription was cancelled) to prevent abuse of free plans and to handle billing questions.
  • Billing records: a log of payment events from our payment processor (plan changes, invoice amounts, payment failures) is kept for accounting, dispute handling, and legal obligations, including after account deletion.
  • Export files: retained until you delete them or your account is closed; we may apply storage limits with notice.
  • Guest demo outputs: anonymous download is typically available for about 1 hour after the demo is ready. Files may be kept on disk for a short reclaim window (typically up to about 72 hours) so you can create a free account and save the export to your library. After that window, files are removed by our normal storage cleanup. A minimal record of each demo (the URL submitted, the time, and a hashed IP address) is kept so we can count usage accurately and prevent abuse. Guest quota and event records (hashed guest identity and hashed IP) are retained for the rolling fair-use window (typically 24 hours) and for limited operational / abuse analysis, then deleted or overwritten.
  • Image-prep uploads and outputs: original uploads, working files, and batch ZIP outputs for Image Auto-Crop / E-Commerce Image Preparation are stored on our servers for a limited retention window (typically up to 48 hours), then deleted automatically. You may also delete a batch earlier from your library. Guest image converts follow the guest demo retention rules above when used without an account.
  • Password reset tokens: single-use, expire after one hour, deleted automatically.
  • Session tokens: expire on logout or after the configured inactivity window.
  • Guest demo cookie (sl_guest): persists for up to about 30 days unless you clear cookies earlier.
  • Contact messages: processed and delivered by email only — no database record is created. Messages are retained in the operator's email inbox only as long as needed to respond. Deletion requests must be submitted by contacting us directly.
  • Technical logs (including IP addresses): retained for a limited period for security and operational purposes, then deleted or anonymised.
  • Sign-in activity records: retained for a limited period for security and abuse investigation. Because they protect against account takeover, they may be kept for a limited time after account deletion.
  • Trial redemption records: retained while your account exists, so one trial per account can be enforced.
  • .onion attestation and capture records: retained, including after account closure, for as long as reasonably needed to show lawful use of the feature and to establish, exercise, or defend legal claims.
  • Landing-page analytics: kept only in pseudonymous form (random visitor key and hashed IP), and aggregated or deleted once they are no longer useful for reporting.

7. Your rights (EEA / UK)

You have the right to access, correct, or erase your personal data; to restrict or object to processing; and to data portability where applicable. You may also lodge a complaint with your local supervisory authority. You can erase your account yourself at any time under Settings → Delete account. This also cancels any subscription. To exercise your other rights, contact us via the contact form.

Note on contact form submissions: messages sent via the contact form are forwarded by email and are not stored in our application database. A Subject Access Request (SAR) response will include a manual review of the operator's email inbox in addition to any data held in the application. To request deletion of a contact message, please contact us and include the approximate date and subject of the original message.

Note on guest demos: because guest demos are anonymous, we may only be able to locate related records if you provide enough detail (approximate time, demo type, and that you still have the sl_guest cookie or a demo ID). Clearing cookies removes our ability to match your browser identity; hashed IP records may remain until their retention window ends.

Limits on erasure: we may keep some records after an erasure request when we have a legal obligation or a legitimate need to keep them, such as payment records, sign-in security logs, and .onion attestation records. We will tell you what we kept and why.

8. Your rights (United States)

Depending on your state, you may have the right to know what personal data we hold about you, to access, correct, or delete it, and to opt out of its sale or use for targeted advertising. We do not sell personal data or use it for targeted advertising. To make a request, use the contact form. We will verify your request using your account email, and we will not treat you differently for exercising your rights.

9. Security

We use reasonable technical and organisational measures to protect your data. These include hashed passwords, HTTP-only session cookies, encrypted connections, hashed IP addresses where raw ones are not needed, and access controls on administrative tools. No system is completely secure. If a breach affects your personal data, we will notify you and the relevant authorities as the law requires.

10. International transfers

Where we use processors or infrastructure outside your region, we implement appropriate safeguards such as standard contractual clauses where required by applicable law.

11. Children

The Service is not directed at children under 16. We do not knowingly collect personal data from children. If you believe a child has provided us data, please contact us and we will delete it promptly.

12. Changes to this policy

We may update this policy, and the "Last updated" date will change when we do. For material changes, we will notify account holders by email or in the app before the changes take effect. Where the law requires your consent to a change, we will ask for it.

13. Contact

For privacy questions or data requests, use the contact form on the home page.