Privacy Policy

Effective date: April 5, 2026 ยท Last updated: July 21, 2026

Quiet Search is a personal job search automation tool for senior Revenue Operations and GTM professionals. This policy explains what data Quiet Search collects, how it is used, and your rights as a user. We have written it to be readable, not just legally defensible.

1. Who we are

Quiet Search has been privately developed and founder-used to date. It has not had a public beta or customer cohort. Contact: support@quietsearch.app

2. What data Quiet Search collects

Account data โ€” when you sign in with an enabled identity provider, we receive the account details that provider shares, typically an account identifier, name, email address, and profile photo. Apple may provide a private relay email address when you choose Hide My Email. This data is used to create your account and populate available profile fields.

Profile data you enter โ€” your target job titles, current role, current company, salary floor, remote preferences, and resume text (if you choose to add it). All stored in your Supabase account.

Job pipeline data โ€” jobs you save, move through stages, annotate with notes or contacts, and track offers. This is your data; it lives in your account only.

Usage interactions โ€” jobs you open and actions you take, such as applied, passed, or watchlisted. These decisions may be stored in your account so Quiet Search can sync your pipeline and learned preferences. When PostHog is configured, manual product events may include your account UUID and coarse audience, provider, action, status, or performance-rating labels. Analytics exclude email addresses, URLs, profile text, notes, resumes, messages, and job or company identifiers.

AI API keys (optional) โ€” keys you add for Groq, OpenRouter, Gemini, Anthropic, or OpenAI are kept in browser session storage and excluded from profile sync and data exports. A request made with your key goes directly from your browser to that provider. If you use included keyless AI, the request goes through Quiet Search's authenticated Supabase Edge Function and then to a configured AI provider. In either path, the selected provider receives the prompt content needed for the feature.

Error and performance data โ€” if configured, Quiet Search sends error reports to Sentry. These may include browser version, component names, and error messages. No personal data is intentionally included.

3. What Quiet Search does not collect

4. Third-party services

Quiet Search relies on the following third-party services to operate:

5. How long we keep your data

You can request account deletion from Settings โ†’ Privacy & data โ†’ Delete account. After recent-authentication and typed-confirmation checks pass, Quiet Search deletes the Supabase Auth user and the user-scoped database records covered by account-deletion cascades. Browser data is then cleared on that device. Service logs, analytics or error-monitoring records, and backups may follow separate retention schedules; contact us for an access or deletion request covering those systems.

6. Your rights

If you are located in the EU, UK, or California, you have the following rights:

To exercise any of these rights, email support@quietsearch.app. We will respond within the period required by applicable law.

7. Security

Your data is encrypted in transit (TLS) and stored in Supabase-managed infrastructure. Row-level security protects user-scoped tables; deliberately public catalog data and redacted marketplace views have separate access policies. Authentication is handled by Supabase Auth, and Quiet Search does not receive your identity-provider password.

Quiet Search remains in private development and has been founder-used to date. You should not use it to store highly sensitive personal information beyond what is necessary for job searching.

8. Cookies and local storage

Quiet Search stores session tokens and bounded profile and pipeline caches in browser storage for sign-in, offline access, and performance. Optional AI keys and resume text are kept in sessionStorage; AI keys are excluded from server profile sync. When configured, PostHog uses browser local storage for analytics persistence and respects the browser's Do Not Track preference. Quiet Search does not enable PostHog autocapture.

9. Changes to this policy

We will update this page if our data practices change and note the updated date at the top. For material changes, we will notify you via email or an in-app notice.

10. Contact

Questions about your data or this policy: support@quietsearch.app

โ† Back to Quiet Search