Last updated: July 11, 2026
FakeSignup ("we", "us") helps developers and QA teams test signup flows with form filling, disposable email inboxes, and verification handling. This policy explains what data we collect, where it is stored, and your choices.
Scope
This policy covers:
- The FakeSignup Chrome extension
- The website at fakesignup.com (accounts, dashboard, billing)
Data stored on your device (Chrome extension)
Most extension data stays in your browser using Chrome's local storage (chrome.storage). We do not upload the following to our servers unless you sign in (see below):
- Extension settings (mail provider, poll interval, automation toggles)
- Per-site field templates and element mappings
- Saved account credentials (email, password, username, domain) when you use the Accounts feature
- Anonymous usage counters for daily limits (fills, inboxes)
- Auth session token after you sign in (to sync your tier and limits)
You can clear this data by removing the extension or clearing extension storage in Chrome settings.
Account data (website & signed-in extension)
If you create a free or premium account, we store on our servers:
- Email address and hashed password (authentication)
- Subscription tier, daily usage counts, and premium expiry date
- Stripe customer and subscription IDs when you purchase Premium (billing is processed by Stripe; we do not store card numbers)
Account data is hosted on our PocketBase backend at db.fakesignup.com. The extension communicates with this service when you sign in to enforce plan limits and Premium features.
Data we access on websites you visit
When you click Fill, Pick, or run Full Auto, the extension reads and modifies form fields on the active tab only after you invoke the action. We use this to:
- Detect signup form fields and insert test data
- Click mapped checkboxes or submit buttons you configure
- Read page text for optional success/error detection in Auto mode
We do not browse pages in the background, track your browsing history, or collect page content for advertising.
Third-party services
- Disposable email providers (Mail.tm, Mail.gw, TempMailc) — when you create a temp inbox, requests go directly from your browser to their APIs. Their privacy policies apply to those inboxes.
- Stripe — payment processing for Premium subscriptions and lifetime plans on our website. Stripe handles card data; we receive payment status and customer identifiers only.
- Vercel — hosts the marketing site and billing API routes.
Clipboard
With your permission (clipboardWrite), the extension copies OTP codes, email addresses, or passwords to your clipboard when you use copy actions in the UI.
How we use data
- Provide form-filling, inbox, and automation features
- Enforce free and premium usage limits
- Process subscriptions and manage your account
- Respond to support requests
We do not sell your personal data.
Retention
- Local extension data remains until you clear it or uninstall the extension
- Account records remain while your account is active
- You may delete your account from the dashboard; this removes server-side account data
- Billing records may be retained by Stripe according to their policies
Your rights
Depending on where you live, you may have rights to access, correct, or delete personal data we hold. Contact us at support@fakesignup.com and we will respond within a reasonable time.
Children
FakeSignup is not directed at children under 13 (or 16 in the EEA). We do not knowingly collect data from children.
Changes
We may update this policy from time to time. The "Last updated" date at the top will change when we do. Continued use after changes means you accept the revised policy.
Contact
Questions about privacy: support@fakesignup.com