← Authflow home

Privacy

Last updated: October 19, 2026

Authflow LLC operates this website and Authflow Rails. This policy explains the information we handle to provide sign-in, MCP access, subscriptions and support. Contact privacy@authflow.ai or write to Authflow LLC, 900 State St, Ste 1, Erie, PA 16501, United States.

Sign-in and account information

Google sign-in provides your account identifier, email address and basic profile, including your name. GitHub provides your user ID, public profile and email addresses; we select a verified address, preferring your primary address. We store your Authflow user ID, linked provider identifiers, signup email, editable display name, and signup, last-sign-in and provider-link dates.

We request Google’s openid, profile and email scopes and GitHub’s read:user and user:email, not mailbox, Drive or repository access. Provider access tokens are used only during sign-in; we don’t store provider access or refresh tokens. Session cookies, server-side sessions and authorization records keep you signed in and connect clients you approve.

Subscriptions and MCP requests

We keep workspace, resource, client-authorization, subscription and credit-usage records, including which tool used credits. Subscribing sends your email and Authflow user ID to the creator’s Stripe account for Checkout and customer records. Stripe sends us payment, invoice and subscription events; we store customer, subscription and checkout identifiers, status and paid-through dates. Stripe handles card details; our forms do not collect card numbers. Stripe’s own uses, including fraud prevention, follow its Stripe Privacy Policy.

Our gateway forwards requests and responses between your client and the creator’s MCP server, including tool arguments, results, submitted personal information and client headers such as user agent. It does not forward your IP address, cookies or Authflow token. Rails does not record arguments or results of calls to a creator’s server.

Creators receive your Authflow user ID, resource and access tier with each request, and remaining credits when reporting usage. The same user ID reaches each creator you use, so creators sharing information could link your activity. Refused-call records, including tests of settings that would refuse a call, show creators your user ID and AI client ID; we retain them for 30 days. An AI client’s MCP access token contains your user ID and access information, but not your email or display name. Creators and AI clients are responsible for their own use of this information under their own terms and privacy policies.

If you’re a creator

Connecting Stripe gives us your account ID and status. We read Checkout sessions, subscriptions, invoices, payments, charges, refunds, disputes and application fees for Rails-created subscriptions to show earnings, maintain access, check fees and prevent fraud. We share account information with Stripe as needed to provide Rails or prevent misuse. Stripe’s privacy policy covers information you give it when opening or connecting an account.

Logs, feedback and support

Hosting logs record requests to our websites and Rails, including IP addresses, URLs and query strings, referring pages, browser or client details, and request headers. Where HTTP log filtering is enabled, it removes cookies and recognized sign-in credentials from new records; older records and other logs may still contain them. Rails logs also contain account, workspace and resource identifiers, errors and usage events. Microsoft Application Insights reports service performance and errors; its browser monitoring reports page loads and browser details and sets ai_user and ai_session cookies.

Where diagnostic correlation is enabled, a separate first-party session cookie holds a pseudonymous diagnostic identifier. Request and session identifiers help us connect related events and investigate failures without using raw authentication cookies or credentials as tracking identifiers. The diagnostic cookie does not sign you in or grant account access. This does not remove the account information described above.

For calls to the Authflow MCP and our documentation MCP server, we log the tool, arguments, search terms, client name and user agent, but not results. We remove recognized secrets, such as fields named like keys, tokens or passwords; this may not catch every sensitive value. Avoid secrets and unnecessary personal information in tool arguments, feedback and support requests.

Feedback includes your submission, client and version, and workspace if signed in. Unsuccessful documentation searches may become feedback with their search terms. Support, abuse and security reports retain your submission and investigation context. Copyright notices and counter-notices, including contact details, are shared with the other party.

Why we use and share information

We use information to authenticate users, enforce access, process subscriptions and credits, answer support requests, investigate failures and abuse, and meet accounting and legal obligations. We share information with service providers for those purposes, with the creators and clients you choose, and when required by law or necessary to protect rights and security. See our service provider list. We do not sell personal information, and we do not use it for targeted advertising. If the business is transferred, relevant records may transfer with it, subject to this policy and applicable requirements.

Email updates and optional website analytics

When you sign up for email updates, including launch updates, Mailchimp stores your email and sends the updates you requested. It may record email opens and link clicks. Unsubscribe using the link in any update.

This marketing website loads Google Analytics and allows its cookies only after you accept analytics. It measures visits, traffic sources, campaigns, device and browser information, and approximate location over time. Advertising storage, personalization and Google signals are disabled in this integration. See Google’s partner-site information.

The site works if you decline. With no saved choice, Global Privacy Control or Do Not Track defaults to declining analytics. A saved choice takes precedence; change it in Preferences below. Withdrawing consent stops this integration’s collection and clears its accessible analytics cookies, but does not erase data already sent to Google. Browser settings can clear saved data. Our host may set ARRAffinity, a routing cookie unrelated to analytics. This website sets no referral cookies. Avoid personal information in campaign links.

Storage, retention and your choices

Authflow LLC is based in the United States. Servers, databases and logs run on Microsoft Azure in Central US; backups may use another US region. Other providers may process data in other countries. We retain account, workspace and subscription records while your account exists; refused-call records for 30 days; logs, backups, feedback and support records for limited periods; and credit, payment and tax records as accounting, dispute and legal obligations require. Backups and required financial or security records may remain after deletion. Safeguards reduce risk but cannot guarantee complete security.

Email privacy@authflow.ai to access, correct, delete or obtain a copy of your information, or exercise other rights available where you live. We may verify your identity and will explain records we must keep. Reply to a declined request to ask for reconsideration. We won’t treat you differently for exercising your rights. To delete your account, email support@authflow.ai or privacy@authflow.ai. Before deletion, we identify active paid subscriptions and, if requested, arrange cancellation at the end of their paid period. Contact creators and AI clients for information they hold.

If you’re in the EEA, UK or Switzerland

Authflow LLC is the controller of the information this policy describes. We rely on these legal bases: performing our contract with you for sign-in, access, subscriptions, credits and forwarding MCP requests; our legitimate interests in securing and improving Rails, preventing abuse, keeping records and complying with US law; and your consent for website analytics and requested email updates, which you can withdraw at any time. You can ask to access, correct, delete, restrict or object to our use of your information, and to get a portable copy. You can also complain to your local data protection authority.

Children

Rails is for adults 18 and older; we don’t knowingly collect children’s information. We delete personal information we learn belongs to a child under 13. We close accounts of anyone under 18, retaining only required billing, security or legal records. Report a child’s information to privacy@authflow.ai. Creators may set a higher age; AI clients have their own age rules.

Updates

We post changes here with an updated version date and email your account address before material changes take effect, telling you when they apply. We ask for consent before materially changing how we use information we already hold, or using Google or GitHub account information in a new way.