Privacy Policy
Last updated: September 27, 2026
1. Introduction
This Privacy Policy explains how Autofiller ("we," "us," or "our") collects, uses, stores, and protects your personal information when you use our service. We are committed to protecting your privacy and handling your data responsibly.
By using Autofiller, you agree to the collection and use of information in accordance with this Privacy Policy.
2. Information We Collect
2.1 Account Information
When you create an account, we collect:
- Email address (required for all account types)
- Name (optional for email/password accounts; provided by Google for OAuth accounts)
- Profile image URL (for Google OAuth accounts)
- Password hash (for email/password accounts only; we do not store plaintext passwords)
- Account creation and last update timestamps
- Terms acceptance timestamp and version when you accept our Terms
2.2 Authentication Data
- OAuth tokens (access tokens, refresh tokens, token expiry) for Google sign-in users
- Session tokens for maintaining logged-in state
- OAuth provider account IDs
2.3 Form and Batch Data
When you use Autofiller to test forms, we store:
- Original form URLs you submit
- Normalized form URLs for deduplication
- Form structure: questions, question types, field IDs, available options, and option IDs
- Form titles (fetched from form metadata when available)
- Batch settings: response count, mode (random/weighted), answer preferences, natural language instructions
- Cloned form URLs (when using form cloning for access)
- Service email addresses used for form access (typically autofillerr@gmail.com)
- Form access verification metadata and timestamps
- Generated response data: captured answers for each submitted response
- Batch execution logs and events (timestamps, status changes, success/failure counts)
- CSV exports you generate (stored temporarily for download)
We read form structure but not existing responses. When you share a form with Editor access, form APIs may technically grant broader read permissions, but Autofiller only reads question metadata needed to generate test responses. We do not import, read, or store responses that other users submitted to your form before you connected it to Autofiller.
2.4 Credit and Payment Information
- Credit wallet balance, reserved credits, and daily free credit allowance
- Transaction history: credit purchases, reservations, captures, and adjustments with timestamps
- Stripe checkout session IDs and payment event IDs
- Stripe webhook event payloads (for payment confirmation and processing)
Payment card details are never sent to or stored by Autofiller. All payment processing is handled securely by Stripe. We only receive confirmation of successful payments and session identifiers.
2.5 Usage and Preference Data
- Notification preferences (whether you want batch completion emails)
- Setup path choices (quick vs. guided onboarding)
- Whether you've seen the first-run celebration
- User role (standard user or admin)
2.6 Analytics Data (PostHog)
We use PostHog for product analytics. PostHog collects:
- Page views and navigation patterns
- User ID and email address (when logged in)
- Feature usage events (actions you take in the application)
- Device and browser information
- General location data (derived from IP address, typically city-level)
PostHog analytics help us understand how the service is used so we can improve it. For more information about PostHog's data practices, see PostHog's Privacy Policy.
2.7 Email Communications (Resend)
We use Resend to send transactional emails including:
- Batch completion notifications
- Password reset links
- Email verification messages
- Account-related notifications
Resend processes your email address and the content of these transactional messages. Email delivery logs are retained by Resend according to their retention policies. For more information, see Resend's Privacy Policy.
2.8 Natural Language Processing (Anthropic)
When you use the natural language answer preference feature (describing desired answer distributions in plain English), your instructions and the form's field and option labels are sent to Anthropic's Claude API for parsing into weight distributions.
Anthropic processes this data to provide the service but does not train models on it. For more information, see Anthropic's Privacy Policy and their Commercial Terms.
2.9 Audit and Security Logs
- IP address hashes (for rate limiting, fraud prevention, and terms attestation)
- Action logs (significant account events for security and support purposes)
3. How We Use Your Information
We use collected information for the following purposes:
- To provide the Service: Process batches, generate responses, manage your account, and handle authentication
- To process payments: Track credit purchases and usage, reserve and capture credits for batches
- To communicate with you: Send batch completion notifications (when enabled), password reset emails, and important account updates
- To improve the Service: Analyze usage patterns to fix bugs and add features that users need
- To ensure security: Detect and prevent fraud, abuse, and unauthorized access
- To comply with legal obligations: Respond to legal requests and enforce our Terms
4. Data Retention
4.1 Active Account Data
While your account is active, we retain the data described in Section 2 indefinitely to provide ongoing service. This includes:
- Account information and authentication credentials
- Credit wallet balance and transaction history
- Form URLs, batch configurations, and batch history
- Generated response data and CSV exports
- Form access sessions and verification status
4.2 Deleted Account Data
When you delete your account through Settings, our database immediately removes:
- Your account record (email, name, password hash, profile information)
- All authentication sessions and OAuth tokens
- Credit wallet
- All form runs (batch configurations, settings, status)
- All batch events and logs
- All form access sessions
- Pending email notifications
Database records retained for our record keeping (anonymized, no personal data):
- Credit transaction records: Your transaction history (credits purchased, reserved, captured) is retained but anonymized. We remove the link to your wallet and clear any metadata that might contain form URLs or other context. The transaction amounts, types, timestamps, and Stripe event IDs are preserved for financial reconciliation and auditing. These records contain no personal information after anonymization.
- Audit logs: Action logs are retained with your user ID removed and all metadata cleared. These anonymized logs support security analysis and debugging but contain no personal information.
We do not set fixed retention periods for these anonymized records. They are kept indefinitely for financial record keeping, regulatory compliance, and operational purposes.
Third-party services retain their own data under their own policies:
- Stripe: Payment records, customer data, and transaction history are retained by Stripe according to their data retention policies and regulatory requirements (typically 7 years for financial records). We cannot delete data stored by Stripe.
- Resend: Email delivery logs are retained by Resend according to their retention policies. We cannot delete data stored by Resend.
- PostHog: Analytics events may be retained in anonymized or aggregate form according to PostHog's retention policies. We cannot delete data stored by PostHog.
4.3 Submitted Form Responses
Important: Deleting your Autofiller account does not delete responses that were submitted to forms during batches. Those responses remain in your form as regular responses and must be managed through the form provider's interface. We have no ability to delete responses from forms after they are submitted.
5. Data Sharing and Third Parties
We do not sell your personal information. We share data with third-party service providers only as necessary to operate the Service:
- Supabase (Database Hosting): All application data is stored in a PostgreSQL database hosted by Supabase. Supabase has access to all data described in Section 2.
- Vercel (Application Hosting): The application is hosted on Vercel's platform. Vercel may have access to request logs and application data in transit.
- Stripe (Payment Processing): Payment information is processed directly by Stripe. We never see your full payment card details.
- Google (OAuth sign-in): When you sign in with Google, Google processes your authentication request.
- PostHog (Analytics): Usage data and analytics events are sent to PostHog's analytics platform.
- Resend (Email Delivery): Email addresses and transactional message content are processed by Resend.
- Anthropic (Natural Language Processing): Form structure and your natural language instructions are sent to Anthropic's API when you use this feature.
All third-party service providers are contractually obligated to protect your data and use it only for providing their services to us.
5.1 Legal Requirements
We may disclose your information if required by law, regulation, legal process, or governmental request, or to protect the rights, property, or safety of Autofiller, our users, or others.
6. Data Security
We implement reasonable security measures to protect your information from unauthorized access, disclosure, alteration, or destruction:
- All passwords are hashed using bcrypt before storage (we never store plaintext passwords)
- All web traffic is encrypted using HTTPS/TLS
- Database connections use encrypted channels
- OAuth tokens are securely stored and refreshed as needed
- IP addresses are hashed for rate limiting and fraud prevention
- Access to production data is restricted to essential personnel only
However, no method of transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.
7. Your Rights and Choices
7.1 Access and Correction
You can access and update your account information through your Settings page. This includes your name, email address, and notification preferences.
7.2 Data Portability
You can download your batch data as CSV files from the batch results page. For a complete export of your data, contact us at support@autofiller.co.
7.3 Account Deletion
You can request account deletion through your Settings page. This will permanently delete your account and most associated data as described in Section 4.2. This action cannot be undone, and any remaining credits will be forfeited.
7.4 Email Preferences
You can opt out of batch completion notification emails in Settings. You cannot opt out of essential transactional emails (e.g., password resets, security notifications) while maintaining an active account.
7.5 Revoke Form Access
You can revoke Autofiller's access to your forms by removing autofillerr@gmail.com from the form's Share settings. Note that this does not delete batch data or generated responses already stored in Autofiller or submitted to the form.
8. Cookies and Tracking
We use essential cookies and similar technologies for:
- Authentication: Maintaining your logged-in session (NextAuth.js session cookies)
- Analytics: PostHog uses cookies to track user sessions and behavior patterns
We do not use advertising cookies or sell data to advertisers. You can disable non-essential cookies through your browser settings, but this may affect service functionality.
9. Children's Privacy
Autofiller is not intended for users under the age of 13 (or the applicable age of consent in your jurisdiction). We do not knowingly collect personal information from children. If we become aware that we have collected information from a child without proper consent, we will delete that information promptly.
10. International Data Transfers
Your data may be processed and stored in the United States and other countries where our service providers operate. These countries may have data protection laws that differ from those in your jurisdiction.
By using Autofiller, you consent to the transfer of your information to countries outside your country of residence, which may have different data protection rules.
11. California Privacy Rights (CCPA)
If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA):
- Right to know what personal information we collect, use, and share
- Right to request deletion of your personal information (subject to certain exceptions)
- Right to opt out of the "sale" of personal information (note: we do not sell personal information)
- Right to non-discrimination for exercising your privacy rights
To exercise these rights, contact us at support@autofiller.co. We will verify your identity before processing requests.
12. European Privacy Rights (GDPR)
If you are located in the European Economic Area (EEA), UK, or Switzerland, you have rights under the General Data Protection Regulation (GDPR) and equivalent laws:
- Right to access your personal data
- Right to rectification of inaccurate data
- Right to erasure ("right to be forgotten")
- Right to restrict processing
- Right to data portability
- Right to object to processing
- Right to withdraw consent at any time
- Right to lodge a complaint with a supervisory authority
To exercise these rights, contact us at support@autofiller.co.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by:
- Updating the "Last updated" date at the top of this page
- Sending an email notification to your registered email address
- Displaying a notice when you next log in
Your continued use of Autofiller after changes become effective constitutes acceptance of the updated Privacy Policy. We encourage you to review this Privacy Policy periodically.
14. Data Breach Notification
In the unlikely event of a data breach that affects your personal information, we will notify you and relevant authorities as required by law. Notifications will be sent to your registered email address and may be posted on our website.
15. Contact Us
If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us:
Email: support@autofiller.co
Website: https://www.autofiller.co
We will respond to your inquiry within a reasonable timeframe, typically within 30 days.