Legal
Privacy Policy
Last updated: September 27, 2026
1. Who we are
Rowe AI (“Rowe,” “we,” “us”) provides a multi-channel social scheduling and assistant product. This Privacy Policy explains what information we collect when you use the Rowe website, dashboard, APIs, and related services (the “Service”), how we use it, and the choices you have.
Contact: support@rowe.ai. Also see our Contact page.
2. Information we collect
Account data. Email address, display name, authentication identifiers from Supabase Auth (including Google sign-in if you choose it), and profile settings.
Social channel data. When you connect Instagram, Facebook, LinkedIn, X (Twitter), Gmail, or Outlook, we receive OAuth tokens and basic account identifiers (such as handle, page ID, or email address) required to publish, schedule, read insights, or manage inbox/comments as you authorize.
Content you create. Captions, media URLs, drafts, schedules, assistant chat threads, agent memory notes, webhooks, and personal access tokens you generate.
Usage & diagnostics. Approximate logs needed to operate the Service (API errors, publish job status, rate-limit events). We do not sell personal data.
3. Social platforms & API data
Rowe uses official provider APIs (including Meta Graph API for Instagram and Facebook Pages). We only request scopes needed for features you use. Platform data is used to:
- Publish, schedule, and cancel posts on your behalf
- Display calendars, analytics, inbox, and comments in the dashboard
- Power the in-app assistant and optional MCP / Agent API tools
Meta permissions (Facebook Login path). When you connect Instagram / Facebook, Rowe may request:
instagram_basic,pages_show_list,pages_read_engagement,business_management— discover and link your Professional Instagram account and Facebook Pageinstagram_content_publish,pages_manage_posts— create Feed, Reels, Stories, and Page posts you approve in Roweinstagram_manage_insights— show post and account analytics in the dashboardinstagram_manage_messages,pages_messaging,pages_manage_metadata— receive and reply to Instagram Direct messages in Inboxinstagram_manage_comments— list, reply to, and moderate comments on your media
We do not sell platform data. Tokens are used only to perform the actions you initiate (or schedule) in Rowe.
Google / Gmail. When you connect Gmail under Channels, Rowe requests Google OAuth scopes needed to identify your mailbox and send email you compose in the dashboard:gmail.send, userinfo.email, and openid. We use the Gmail API to send messages only when you publish or schedule a Gmail send in Rowe. We do not sell Gmail content. You can disconnect Gmail anytime in Channels and revoke access in your Google Account security settings.
3a. Google API Services — Limited Use
Rowe AI’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Google Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
- Google user data (your Gmail address and the OAuth tokens that let Rowe send on your behalf) is used only to provide the user-facing Gmail send feature you enable in Channels.
- Rowe does not read, index, or store the contents of your Gmail mailbox. The requested scopes only allow sending messages you compose.
- We do not transfer Google user data to third parties except as necessary to provide the feature, for security, to comply with law, or as part of a merger or acquisition with your notice.
- We do not use Google user data to serve advertisements, and we do not sell it.
- We do not use Google user data, raw or derived, to develop, improve, or train generalized or non-personalized AI or machine-learning models. Google user data is not sent to AI providers.
- Humans at Rowe do not read Google user data unless you give explicit consent for a specific message (for example, a support request), it is needed for security or abuse investigation, or it is required by law.
3b. How we protect sensitive data
- Encryption at rest. OAuth access and refresh tokens for Gmail and every other connected channel are encrypted with authenticated symmetric encryption (Fernet: AES-128-CBC with HMAC-SHA256) before they are written to the database. The encryption key is held as a secret on the Rowe AI API server and is never shipped to the browser.
- Encryption in transit. All traffic between your browser, the Rowe website, the Rowe AI API, our database, and provider APIs (including Gmail) uses HTTPS/TLS.
- Access controls. Tokens are only decrypted server-side at the moment an action you requested runs. Application data in Supabase is protected by row-level security so each account can only access its own rows. Service credentials are restricted to server environments and limited to the staff who operate the Service.
- No client-side token storage. Provider tokens are never placed in browser localStorage, cookies readable by scripts, or desktop MCP clients.
- Minimal scopes. We request only the scopes needed for features you use (for Gmail: send-only).
- Deletion. Disconnecting a channel deletes its stored tokens. Deleting your account removes your tokens and associated data as described in section 7.
- Incident response. If we become aware of unauthorized access to your data, we will investigate, revoke affected credentials, and notify you and regulators as required by law.
3c. Token storage & disconnecting
Token storage. Social access tokens are stored on the Rowe AI API vault (hosted on Railway), not in the browser localStorage and not in the Cursor MCP desktop client. The website authenticates you and calls the vaulted API to perform channel actions.
You can disconnect a channel at any time in the dashboard under Channels. Disconnecting revokes Rowe’s stored connection for that platform; you should also revoke access in the provider’s security settings if desired.
4. How we use information
- Provide, secure, and improve the Service
- Authenticate users and enforce rate limits
- Generate assistant drafts and analytics-derived playbooks you control
- Respond to support and compliance requests
- Comply with law and platform developer terms
Optional AI providers (for example Anthropic for in-app chat, or media helpers such as stock image / video generation services you enable) process prompts and outputs needed to fulfill your requests. Do not submit secrets or data you are not allowed to process with those providers.
5. Processors & subprocessors
We use trusted processors to run the Service, including:
- Supabase — authentication and application database / storage
- Railway — Rowe AI API and token vault hosting
- Vercel (or your chosen host) — website hosting
- Meta, LinkedIn, X, Google, Microsoft — connected social / email APIs
- Anthropic and similar AI vendors — when the assistant or compose tools are used
6. Retention
We retain account and content data while your account is active. Publish jobs, metrics, and logs may be kept for a reasonable period for reliability and abuse prevention. You may request deletion as described below.
7. Your rights & deletion
Depending on your location, you may have rights to access, correct, or delete personal data. To delete your Rowe account data and connected social tokens, follow the steps on our Data Deletion page or email support@rowe.ai with the subject “Data deletion request.”
8. Children
The Service is not directed to children under 13 (or the minimum age required in your jurisdiction). We do not knowingly collect data from children.
9. International transfers
We may process data in the United States and other countries where our processors operate. By using the Service you understand that your information may be transferred to those locations.
10. Changes
We may update this Policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the Service after changes means you accept the updated Policy.