Privacy information
Know what your workspace keeps.
SearchScribe is a beta writing workspace. Here is what it stores and which services support it.
Start writing ↗Account and articles
The application stores your account details, article content, SEO fields, and version history in its database so you can return to your work. Passwords are stored as hashes, not readable passwords.
Optional Google sign-in
If you choose Google sign-in, SearchScribe receives your verified email, name, and stable Google account identifier to create or identify your account. It does not request access to Gmail or Google Drive. Linking Google to an existing password account requires your password and an explicit linking action.
Sessions and generation
A short-lived access token and an HttpOnly refresh cookie keep you signed in. When you request generation or a rewrite, your topic or article content is sent to the configured AI provider. Google Gemini is the primary service; Groq can process the same request if an optional fallback is enabled and the primary service is unavailable. Avoid entering sensitive personal or confidential information.
For web research, Tavily receives your search topic. Source excerpts are passed to the selected AI provider to help write the draft; source links and research dates are saved with your article versions and exports. Search results do not establish that every claim is correct or that coverage is complete.
Account emails
Brevo sends verification, password reset, and password-change notices. It receives your email address, name, and the security message, including any single-use verification or reset link or code. SearchScribe stores only hashes of these secrets and requests that Brevo not track opens or clicks for security emails. Brevo still processes email contents and delivery records. Do not share your security links or codes. Account emails do not subscribe you to a marketing list.
Hosting and beta limitations
Vercel hosts the website, Render runs the API, and Neon stores account and article data in Postgres. Self-service account deletion and a published retention schedule are not yet available. You can inspect the current implementation and raise questions in the open-source repository.