What gets collected
Only what you explicitly connect or send. Account information. Your email, name, and authentication tokens via Clerk. Standard for any web product. Connected app data. When you connect Gmail, Fluso reads your email. When you connect Calendar, it reads your events. When you connect Slack, it reads messages in the channels you authorised. The scope is exactly what you approved on the OAuth screen — no more. Workspace content. Files you upload, conversations you have with Fluso, tasks created (manually or automatically), and the projects you organise work into. Knowledge graph entries. The connected map of people, projects, decisions, and topics that Fluso builds from the items above. See Memory for what goes into it. Usage information. Typical product analytics: which features you use, how often, error logs. Used for improving the product, never for advertising.What doesn’t get collected
- Your passwords. OAuth flows mean Fluso never sees them.
- Apps you haven’t connected. If Slack isn’t connected, Fluso has no idea what you’ve discussed there.
- Anything outside the permissions you approved. Gmail authorisation grants read and send. There’s no path to delete or modify account settings, even if Fluso wanted one.
- Behavioural tracking for advertising. Fluso doesn’t sell ads.
What it’s used for
Answering your requests. The obvious one. Summarising your inbox requires reading your inbox. Building your knowledge graph. The graph is what enables recall, meeting prep, and pattern surfacing. It’s stored in your isolated workspace. No other user sees it. Product improvement. Aggregate usage signals. Specific content (your emails, your transcripts, your messages) is never used for this. Account operations. Billing, support, security alerts.What it isn’t used for
Training AI models. Your private data — emails, transcripts, files, conversations — is never used to train Fluso’s models or anyone else’s. No exceptions. Sale to third parties. Your data isn’t sold. Period. Cross-tenant analysis. Per-user isolation means your data is never combined with another user’s for any purpose. Ads. Fluso has no advertising business.Where data lives
In your isolated workspace, on encrypted infrastructure operated by Prem AI. The technical specifics — TLS, at-rest encryption, OAuth token vaults, sandbox containers — are at Security. Default region: US. Enterprise customers can request alternative data residency as part of their plan.Sub-processors
Fluso uses a small set of vendors to operate the service. Each is bound by contract to handle your data with the same standards.| Vendor | Purpose |
|---|---|
| Clerk | Authentication and user management. |
| Anthropic | Underlying LLM (anonymised; not used for training). |
| OpenAI | Underlying LLM (anonymised; not used for training). |
| Stripe | Billing and payments. |
| AWS | Infrastructure hosting. |
Your rights
Access. Request a copy of everything Fluso has on you. Export comes as JSON plus the raw files in your workspace. Deletion. Three levels available, all reversible only by re-doing the work:- Delete individual entries from your knowledge graph by asking: “Forget what you know about Project X.”
- Disconnect a connected app to delete all OAuth tokens immediately. Fluso loses access from that moment.
- Delete your account to permanently remove every piece of data Fluso holds about you. This is the nuclear option and it’s not reversible.
Knowledge graph privacy
The graph is the thing most worth understanding here, because it’s the thing that turns Fluso into something more than a chatbot. It’s yours alone. Stored in your isolated workspace, never shared with other users, never used to train models, deletable in pieces or in whole at any time. It only ever builds from apps you’ve connected. Disconnect Slack and Slack data stops contributing. Disconnect everything and the graph stops growing. You can scope it. “Don’t track anything related to Project X” tells Fluso to leave that out. “Forget everything about this vendor” removes existing entries. Team plans share within projects. When a project is shared with a teammate, both of you see the same graph for that project — the same memory, the same decisions. Personal projects stay personal.On Team plans
Admins can:- See which apps members have connected (for managing access).
- Set security policies.
- Manage user access and seat allocation.
- Read members’ messages, drafts, or files.
- Access members’ personal knowledge graphs.
- See content of a member’s private projects.