Data and privacy

Privacy at Amplifying.

How we handle information when you visit our website, receive research updates, or use our products.

Last updated September 28, 2026

The essentials

We do not sell personal data.
Customer-specific reports and dashboards are private. We do not publish them without explicit permission.
You can request access, correction, export, or deletion of personal data at security@amplifying.ai.

See our trust center for the list of service providers, what they do, and the types of information they process.

What we collect

Contact and newsletter details: When you contact us, request a report, or subscribe to research updates, we collect the details you provide. These may include your name, email address, company, product, category, message, scheduling link, and subscription preferences.
Account and authentication data: Clerk manages sign-in information, including your email address, account identifiers, session data, and multifactor authentication metadata.
Account, plan, and billing metadata: We store the account metadata needed to operate the service, such as name, email, plan state, billing identifiers, timestamps, and access entitlements. Stripe handles checkout and payment processing; we do not store full payment card numbers.
Amplifying-generated customer reports: We generate customer dashboards and reports from benchmarks and research we create and run. We use customer-supplied benchmark data only when you specifically request it. Information shared in advisory discussions and account-specific records remain private unless we have explicit permission to publish or share them.
Amplifying-generated benchmark data: We store the prompts, test repositories, agent sessions, responses, results, and datasets from our own benchmarks. These research records are created by Amplifying rather than supplied by customers.
Usage, analytics, and operational logs: We collect request metadata, product usage events, page analytics, deployment events, authentication events, and error signals to operate, secure, debug, and improve the service.

How we use information

Provide the service and respond to you: We use contact, account, and billing information to respond to inquiries, manage access and subscriptions, deliver reports, and send research updates you request.
Operate and improve the service: We use usage events and operational logs to understand how the service is used, diagnose errors, protect accounts, and improve reliability.

Collection limits and sharing

Customer data ingestion: We do not ingest customer data unless you specifically request it. Amplifying creates the prompts, repositories, and benchmark runs used for its research.
No special-category or children's data: The service is not intended to collect health information, financial account details, biometric information, children’s data, or other sensitive personal information. Processing that information is outside the current service scope unless we explicitly agree otherwise.
No sale of personal data: We do not sell personal data. We also do not share private customer reports, dashboards, or inquiry details with competitors.

Public research and private customer reports

Public research: Published research, reports, dashboards, and datasets use benchmark data generated by Amplifying without customer data. Public datasets may include Amplifying-created benchmark prompts, repository fixtures, and model responses from our research runs, but not customer workspace content.
Customer reports and dashboards: Customer-specific reports and dashboards remain private even when they are based on benchmarks we created. We do not publish, redistribute, or use those materials in public research without explicit permission.

Data storage and retention

Account data: Authentication identity and account metadata are retained while the account is active and deleted within 30 days after account closure, unless a legal obligation requires longer retention.
Billing records: Billing and financial records may be retained for up to 7 years after account closure for tax and accounting requirements.
Operational logs and backups: Operational logs are retained on rolling provider windows, generally 30 days. Neon database backups use point-in-time recovery windows, generally 7 days, and then age out.
Newsletter and communications: Newsletter contacts are retained until you unsubscribe or ask us to remove them. Customer communications and operational email records are retained for the duration of the relationship and as needed for ordinary business records.

Your choices and rights

Request a copy, correction, or deletion: You can request access, export, correction, or deletion of personal data by emailing security@amplifying.ai. Where required by law, we respond within 30 days.
Stop non-essential email: You can opt out of non-essential emails by emailing us directly.
Security questions and disclosures: Email security@amplifying.ai with security questions, vulnerability reports, privacy requests, or requests for a data processing agreement.

Security practices

Encryption: Traffic is encrypted in transit with TLS. Data at rest is encrypted through managed providers such as Neon, Vercel, Clerk, and Stripe.
Access controls: Private benchmark data and Amplifying-generated customer reports and dashboards are access-controlled and not publicly accessible.
Security program: Amplifying maintains a documented security program and publishes a trust center at amplifying.ai/trust.

Privacy questions or requests?

Email security@amplifying.ai. For security controls and review materials, visit our trust center.

If we make material changes to this page, we will note them here and notify affected customers where required.