diff --git a/AGENTS.md b/AGENTS.md index 128633b..3bde173 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -16,7 +16,7 @@ The IA tracks the user's journey from "just landed" to "pro user". Five sidebar - **Workflows** — `/workflows/*`. Six concrete stories: morning brief, meetings, research-to-deck, content launch, bug-to-PR, knowledge recall. - **Features** — the five primitives: `/features/{chat, connectors, skills, tasks, memory}`. Everything Fluso does is some combination of these five. - **Connector setup** — `/integrations/{gmail, google-calendar, slack, github}`. Per-app permissions and prompts, not feature pages. -- **Reference** — `/resources/{pricing, security, privacy, faq}`. Security covers infrastructure; Privacy covers data handling; they're distinct pages. +- **Reference** — `/resources/{pricing, security, faq}`. Security covers both infrastructure and data handling. The home page (`/`) is a router into the journey, with three sections: just landed, already set up, daily user. diff --git a/docs.json b/docs.json index a8962a6..0c5a624 100644 --- a/docs.json +++ b/docs.json @@ -60,7 +60,6 @@ "pages": [ "resources/pricing", "resources/security", - "resources/privacy", "resources/faq" ] } diff --git a/features/connectors.mdx b/features/connectors.mdx index db74458..1c04908 100644 --- a/features/connectors.mdx +++ b/features/connectors.mdx @@ -73,7 +73,7 @@ There's no "auto-send" mode. You're always the one who clicks send. **Per-user isolation.** Your tokens cannot access another user's data, and theirs cannot access yours. Same for Team plans — admins manage seats but cannot read messages or files. -For the longer security and privacy picture, see [Security](/resources/security) and [Privacy](/resources/privacy). +For the longer security picture, see [Security](/resources/security). ## Managing connections @@ -106,4 +106,4 @@ GitHub only if you write code. The features it enables are powerful, but they're -The longer take is at [Privacy](/resources/privacy). +The longer take is at [Security](/resources/security). diff --git a/index.mdx b/index.mdx index c6bdb28..19989f6 100644 --- a/index.mdx +++ b/index.mdx @@ -56,7 +56,7 @@ Pick a workflow that matches a problem you have right now. Each one is a story, Plans, limits, billing. - - What's collected, what isn't, your rights to delete. + + Encryption, isolation, account security, data handling. diff --git a/resources/faq.mdx b/resources/faq.mdx index 0d6ee7c..84049cd 100644 --- a/resources/faq.mdx +++ b/resources/faq.mdx @@ -84,7 +84,7 @@ description: The questions that come up most often. What Fluso is, how it works, -The full picture is split across [Security](/resources/security) (infrastructure, encryption, account safety) and [Privacy](/resources/privacy) (what's collected, what isn't, your rights to delete). +The full picture is at [Security](/resources/security). ## Pricing diff --git a/resources/privacy.mdx b/resources/privacy.mdx deleted file mode 100644 index 667df1e..0000000 --- a/resources/privacy.mdx +++ /dev/null @@ -1,132 +0,0 @@ ---- -title: Privacy -sidebarTitle: Privacy -description: What Fluso collects, what it stores, what it doesn't, and your rights to access, delete, and export. The full picture, plainly. ---- - -Your data is yours. The infrastructure side of that promise (encryption, isolation, account security) is at [Security](/resources/security). This page is the data side: what Fluso collects, what it does with it, and what you can do about it. - -## 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](/features/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](/resources/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. | - -The full list and most current versions are available on request from Enterprise customers. [Email us](mailto:privacy@premai.io) for details. - -## 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. - -**Correction.** If something in your knowledge graph is wrong, tell Fluso. The graph updates. - -**Portability.** Your files are downloadable from your workspace at any time. Your knowledge graph can be exported as JSON. - -**Restriction and objection.** You can scope what Fluso tracks. *"Don't track anything related to Project X"* means it doesn't. - -For GDPR data subject requests, email [privacy@premai.io](mailto:privacy@premai.io). We respond within 30 days, typically faster. - -## 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. - -Admins cannot: - -- Read members' messages, drafts, or files. -- Access members' personal knowledge graphs. -- See content of a member's private projects. - -Audit logs record administrative actions (seats added, policies changed) but not the content of any user's work. - -## Compliance - -Fluso is built by Prem AI. For Enterprise customers we offer a Data Processing Agreement, custom data residency, audit logging, SSO (SAML/OIDC), and SOC 2 (in progress). - -GDPR (EU/UK) and CCPA (California) data subject rights are honoured for all customers. Requests go to [privacy@premai.io](mailto:privacy@premai.io). - -## Changes to this policy - -When we update this policy in a way that meaningfully affects your rights, we'll notify you by email at least 30 days before the change takes effect. Minor edits (clarifications, formatting, broken links) get fixed without notice. - -## Contact - -For privacy questions: [privacy@premai.io](mailto:privacy@premai.io). - -For security vulnerabilities: [security@premai.io](mailto:security@premai.io). - -For everything else: [support@premai.io](mailto:support@premai.io). diff --git a/resources/security.mdx b/resources/security.mdx index 4ae1bb2..72815bb 100644 --- a/resources/security.mdx +++ b/resources/security.mdx @@ -1,10 +1,10 @@ --- title: Security sidebarTitle: Security -description: How Fluso is built to protect your data. Encryption, authentication, infrastructure isolation, and how to report a vulnerability. +description: How Fluso protects your data. Encryption, authentication, infrastructure isolation, what's never done, and how to report a vulnerability. --- -This page is about the infrastructure side: how data is encrypted, how authentication works, how user environments are isolated, and how to report a problem. For the data side — what's collected, what isn't, and your rights — see [Privacy](/resources/privacy). +How data is encrypted, how authentication works, how user environments are isolated, what Fluso never does with your data, and how to report a problem. ## Encryption diff --git a/workflows/knowledge-recall.mdx b/workflows/knowledge-recall.mdx index 2bebb57..539066a 100644 --- a/workflows/knowledge-recall.mdx +++ b/workflows/knowledge-recall.mdx @@ -69,7 +69,7 @@ Gmail connected (see [Gmail](/integrations/gmail)). Calendar connected so meetin ## Privacy -The graph is yours alone. Lives in your isolated workspace. Never shared with other users. Never used to train models. Delete individual entries or wipe the whole thing whenever you want. Full picture at [Security & privacy](/resources/security). +The graph is yours alone. Lives in your isolated workspace. Never shared with other users. Never used to train models. Delete individual entries or wipe the whole thing whenever you want. Full picture at [Security](/resources/security). ## Related