Privacy Policy

We collect only what we need to run BIG Tools:

• Account data — the email and name you sign up with, plus any profile info you add. If you sign in with Google or another provider, we receive the basic profile that provider shares.
• Your content — prompts, insights, frameworks, pitches, notes, and anything else you create or upload while using the tools.
• Usage data — which tools you use, how often, how long requests take, error events, and basic device and browser metadata. We use this to keep the Service running and to improve it.
• Support data — if you contact us through the contact form or email, we keep the conversation and any context you share.

We don’t buy personal data from data brokers or assemble profiles beyond what you give us.

• To run the Service and respond to your requests.
• To send AI-generated output by calling large language models on your behalf.
• To improve BIG Tools — debug issues, tune prompts, and understand which tools help students most.
• To communicate with you about your account, service changes, or beta-program updates.
• To keep the Service safe — detect abuse, prevent fraud, enforce our Terms.

We don’t use your personal content to train foundation AI models. We may analyze anonymized, aggregated patterns across all users to improve the product.

BIG Tools is built from a small number of services. When you use the Service, some data passes through them:

• Vercel — application hosting and serverless functions (US/EU).
• Supabase — authentication, database, and file storage for your account and content.
• Vercel AI Gateway, OpenRouter, Anthropic, and Google (Gemini) — large language model inference. Your prompts and relevant context are sent to one of these providers to generate AI output. We pick providers per tool and disclose defaults in our recipe docs.
• Resend (or a similar transactional email provider) — to send account emails.
• Optional analytics or error-monitoring tools we enable in the future. If we add something that touches personal data, we’ll update this list and give notice.

These providers process data under their own terms and privacy practices; links are available on request through the contact form.

We keep your account data and content while your account is active. If you delete your account, we delete or anonymize your content within 30 days, except where we need to retain limited records for legal, security, or fraud-prevention reasons.

Server logs and short-term debug data roll off within 90 days. Beta data may be reset when we cut new major releases — we’ll try to warn you in advance when that affects you.

You can:

• See and update your account info in settings.
• Export your content (or request an export through the contact form if a self-serve export doesn’t exist for the tool you used).
• Delete your account, which triggers content deletion.
• Ask us to correct inaccurate data, restrict how we process it, or object to specific uses.

Residents of the EU/EEA, UK, California, and similar jurisdictions have additional rights under local law (GDPR, UK GDPR, CCPA/CPRA). To exercise them, use the contact form. We won’t discriminate against you for exercising your rights.

BIG Tools is designed for learners 16 and older. If you’re a teacher or school administrator bringing BIG Tools to a class with students under 16, contact us first so we can walk through how consent, data minimisation, and content controls work in your context.

We do not knowingly collect data from children under 13. If you believe we have, tell us and we’ll delete it.

We use industry-standard practices: HTTPS, database row-level security, secret management via Doppler, principle of least privilege for access. No system is perfectly secure; if we discover a breach that affects you, we’ll tell you and the appropriate regulators as law requires.

BIG Tools runs on US and EU infrastructure through Vercel and Supabase. If you’re outside those regions, your data may be transferred to and processed there. Where required, we rely on standard contractual clauses or equivalent mechanisms.

BIG Tools uses a small number of cookies and similar browser storage for authentication, theme, and locale. See the Cookie Policy for detail.

We’ll update this policy as BIG Tools changes. Material changes will be announced in-product or by email. The “last updated” date below is the authoritative version marker.

Privacy questions, data requests, or concerns: reach us through the contact form. Mark your message “privacy” and we’ll route it to the right place.