Forkpage ← Back to Forkpage

Privacy Policy

Last updated: [INSERT DATE]

This Privacy Policy explains how [Forkpage / your legal entity name — TO BE CONFIRMED] ("Forkpage," "we," "us," or "our") collects, uses, shares, and protects information when you use forkpage.io, forkpage-production.up.railway.app, and related services (the "Service").

1. Information We Collect

Account information. When you sign up or sign in — including via Google sign-in — we (through our authentication provider, Supabase) collect your name, email address, and a unique account identifier. If you use Google sign-in, Google shares the profile information you authorize (typically name, email, and profile picture) with us for authentication purposes.

Payment information. If you subscribe to a paid plan, billing is handled by Stripe. We do not store your full card number ourselves; Stripe processes and stores your payment details under its own privacy policy and security standards. We receive limited billing metadata from Stripe (such as subscription status and transaction history) to manage your account.

Content you submit. This includes the URLs of pages you choose to fork, the resulting Forked Output (the HTML/Tailwind reconstruction), and any edits, project names, or other content you create or save in your account.

Automatically collected information. Like most web services, we automatically collect IP address, browser and device type, referring pages, timestamps, and general usage/log data (such as which features you use) when you use the Service. We may use cookies or similar technologies for authentication (keeping you signed in) and basic analytics.

2. How We Use Information

We use the information above to: provide, operate, and maintain the Service (including forking pages you submit and rendering your account's Forked Output); authenticate you and secure your account; process subscription payments and manage billing; respond to support requests; monitor for abuse and enforce our Terms of Service, including the acceptable-use restrictions on what may be forked; and improve and troubleshoot the Service.

We do not sell your personal information.

3. How We Share Information

We share information only as needed to operate the Service, specifically with:

We may also disclose information if required by law, subpoena, or legal process; to protect the rights, property, or safety of Forkpage, our users, or others; or in connection with a merger, acquisition, financing, or sale of assets (with notice to you where required).

4. Forked Content and Third-Party Pages

A core function of the Service is reconstructing publicly accessible pages you submit. Any personal data that happens to appear on a page you choose to fork (for example, names or images on a public team page) is not data we collect about you — it originates from the third-party page you submitted, and you are responsible for forking only pages you're permitted to reproduce, consistent with our Terms of Service. We are not responsible for, and this Privacy Policy does not cover, the privacy practices of third-party websites you choose to fork or that a Forked Output may reference or link to.

5. Cookies

We use a limited set of cookies necessary to keep you signed in and to remember basic preferences, and may use cookies for aggregate, non-identifying usage analytics. You can control cookies through your browser settings; disabling essential cookies may prevent you from staying signed in.

6. Data Retention

We retain account information and Forked Output for as long as your account is active, or as needed to provide the Service. If you delete your account, we will delete or anonymize your personal information within a reasonable period, except where we are required to retain it for legal, tax, billing, or dispute-resolution purposes.

7. Your Rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal information, and to object to or restrict certain processing (for example, under the EU/UK GDPR or U.S. state privacy laws such as the CCPA). To exercise any of these rights, contact us at privacy@forkpage.io. We will respond within the timeframe required by applicable law. If you are in the EEA/UK, you also have the right to lodge a complaint with your local data protection authority.

8. Data Security

We use reasonable technical and organizational measures — including relying on the security practices of Supabase, Stripe, and Railway — to protect your information. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

9. Children's Privacy

The Service is not directed to children under 18 (or the age of digital consent in your jurisdiction), and we do not knowingly collect personal information from children. If you believe a child has provided us information, contact us so we can delete it.

10. International Data Transfers

Depending on where you and our service providers (Supabase, Stripe, Railway) are located, your information may be transferred to and processed in countries other than your own, including the United States. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for such transfers. [Confirm hosting/data regions with Supabase and Railway and update this section accordingly.]

11. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be notified via the Service or by email; the "Last updated" date above reflects the most recent revision. Continued use of the Service after changes take effect constitutes acceptance of the revised policy.

12. Contact Us

Questions about this Privacy Policy or requests regarding your personal information can be sent to privacy@forkpage.io.


This document was drafted based on common structures used by comparable AI/SaaS tools and general privacy-policy practice. It is not legal advice. If you have or expect to have users in the EU/UK or California, we recommend a licensed attorney or compliance service confirm whether you need additional mechanisms — such as a cookie consent banner or a formal Data Processing Agreement with Supabase/Stripe/Railway — before relying on this policy.