Privacy at 100 Questions
This notice explains which data the service needs, why it is used, which processors help operate it, and which controls are available to account owners.
Effective
Data the service processes
- Account details such as an email address and authentication records.
- Benchmark inputs such as a subject name, public domain, description, market, locale, and selected competitors.
- Generated questions, provider answers, source URLs, analysis labels, scores, coverage records, and report exports.
- Payment identifiers, purchased-credit records, and fulfillment metadata. Full card details are handled by Stripe rather than stored by 100 Questions.
- Operational and analytics data needed to secure, diagnose, and understand use of the public website and application.
How the data is used
Data is used to create and operate an account, run the benchmark, preserve evidence, calculate results, generate exports, fulfill purchases, send service notifications, prevent abuse, and improve reliability. Private benchmark runs are not published as public profile pages.
Service providers
The service relies on specialist processors for hosting and workflows (Vercel), database and authentication services (Neon), payments (Stripe), transactional email (Resend), AI model access and routing (Vercel AI Gateway and the selected model providers), and website analytics (Google Analytics, DataFast, and Vercel Analytics). Those services process data under their own applicable terms and privacy commitments.
Retention and account controls
The default answer-evidence retention window is 30 days. The service may retain account, billing, security, and minimum explanatory records for longer when they are needed to operate the account, fulfill a purchase, prevent abuse, resolve a dispute, or meet legal obligations. Account owners can delete individual benchmark runs from their private workspace.
Public website checks
The free readiness checker fetches only publicly reachable website resources supplied by the user. Do not submit secrets, private network addresses, or personal data. See the checker documentation for the scope and limitations of that service.
Questions and requests
Use the contact page for privacy, account, or payment questions. Include only the minimum information needed to identify the request and never post receipts or account details in a public issue.