Privacy Policy

We collect account information such as your name, author or pen name, email address, password through Supabase Auth, primary genre, invite-code status, and account settings.

We store the information you add to AuthorReach, including books, relationship records, creator profile URLs, handles, notes, research snapshots, outreach drafts, timeline activity, follow-up dates, campaign details, feedback, and usage events.

Using AuthorReach or its extension also creates technical request data processed by our hosting and authentication providers, such as IP addresses, approximate IP-based region, browser information, request paths, timestamps, response status, and errors. We use these operational logs to run, secure, and troubleshoot the service. The extension does not request GPS or precise device location. Operational log retention varies by provider, service, plan, and configuration.

When you open the extension or click its capture button on a supported TikTok or Instagram profile, post, or feed, it reads available creator details such as the handle, display name, profile URL, profile image, and bio. It checks your AuthorReach account for an existing relationship. Profile details and any notes you enter are saved to your account only when you confirm Save to AuthorReach. On feeds it identifies one visible post's author; when that author is unclear, it asks you to open the creator's profile. It does not bulk collect profiles or send outreach messages.

Version 0.2 and later store the connection token in the extension's local Chrome storage, not Chrome sync. This storage is not an encrypted password vault. Supported website pages do not receive the token; authenticated requests are sent by the extension to app.getauthorreach.com. You can disconnect in the extension and revoke tokens in AuthorReach Settings. Updating an older extension removes its previously synced token from sync storage; rotating that token is recommended after reconnecting.

Successful extension saves record a setup-confirmation usage event for your account. AuthorReach also records a token's last-used time to help you manage connections. These signals distinguish a created token from a completed creator capture; they do not track your general browsing history.

AuthorReach complies with the Chrome Web Store User Data Policy, including the Limited Use requirements, for information handled through the extension. Extension data is used only to provide, maintain, secure, or improve the creator-capture and connected relationship-workspace features described in our listing and interface. We do not sell it or use it for advertising, unrelated profiling, creditworthiness, or lending.

We share this data only with services needed for those features, when required by law, or to address malware, fraud, or abuse. AuthorReach personnel may read it only with your explicit permission for specific data, when required for security or legal reasons, or in aggregated and anonymized form for internal operations.

We use your information to provide the AuthorReach product, keep each user workspace separate, generate one-at-a-time outreach drafts, show reminders, improve the beta experience, troubleshoot issues, and respond to feedback.

Product usage events help us understand where beta users get stuck and which workflows are useful. These events are used to improve AuthorReach, not to send automated outreach.

We do not sell your personal information. We use Supabase for authentication and data storage, Vercel for application hosting, Resend to deliver beta invitations, account verification, and password-recovery emails, and Sentry for technical error monitoring. These providers process the information needed to deliver their respective services. During beta, creator intelligence sharing remains dormant. Any future feature must respect the extension-data restrictions described above.

Our web application is configured to send Sentry technical error categories, timestamps, application release identifiers, and restricted code locations. We remove free-text error messages, account identities, request bodies, cookies, headers, URL query strings, and user-entered content from these reports before transmission. We do not use Sentry session recordings, screenshots, console-log capture, or source-code uploads in this configuration. The Chrome extension does not include the Sentry SDK.

Sentry receives network connection information when a report is delivered. We enable its setting to prevent IP addresses from being stored with error events. Error data is processed in Sentry's United States region; retention and operational-log handling depend on the service, plan, and configuration. Error monitoring is separate from the product usage events stored in AuthorReach.

AuthorReach uses Supabase authentication and row-level security so each user works in their own workspace. Your books, relationships, campaigns, notes, timeline activity, feedback, and usage data are not intended to be visible to other users.

You can request deletion of your AuthorReach account and workspace data at any time by emailing nwfloutdoors@gmail.com. During beta, deletion requests are handled manually so we can confirm the correct account before removing data.

Questions about privacy, feedback, or data deletion can be sent to nwfloutdoors@gmail.com.