From 8de4d793ef9de6c546b6e861a15f42bf9daaf711 Mon Sep 17 00:00:00 2001 From: Lorenzo Dalmazzo Date: Tue, 15 Sep 2026 11:51:19 +0000 Subject: [PATCH 1/3] docs: consolidate privacy and security into Legal --- AGENTS.md | 2 +- content/docs/admin-panel.mdx | 2 +- content/docs/deployment-models.mdx | 4 +- content/docs/index.mdx | 4 +- content/docs/introduction.mdx | 2 +- content/docs/resources/faq.mdx | 4 +- content/docs/resources/legal.mdx | 13 ++ content/docs/resources/meta.json | 2 +- content/docs/resources/pricing.mdx | 2 +- content/docs/resources/privacy.mdx | 136 -------------------- content/docs/resources/security.mdx | 78 ----------- content/docs/workflows/knowledge-recall.mdx | 2 +- public/_redirects | 6 + 13 files changed, 31 insertions(+), 226 deletions(-) create mode 100644 content/docs/resources/legal.mdx delete mode 100644 content/docs/resources/privacy.mdx delete mode 100644 content/docs/resources/security.mdx create mode 100644 public/_redirects diff --git a/AGENTS.md b/AGENTS.md index a6d7f8b..baec624 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -18,7 +18,7 @@ The navigation keeps Home first, then sorts the top-level sections and the pages - **Deployment models** - `/deployment-models`. Current availability and operating boundaries for Fluso Cloud, dedicated AWS VPC, planned Azure VNet, and scoped on-premises deployments. - **Features** - `/features/*`. Approvals and permissions, Apps and MCP servers, Chat, Confidential mode, Imports, Memory, Projects, Skills, and Tasks. - **Get started** - `/going-deeper`, `/introduction`, `/quickstart`. These pages explain the path from first setup to daily use. -- **Reference** - `/resources/{faq, pricing, privacy, security}`. Security covers infrastructure; Privacy covers data handling; they're distinct pages. +- **Reference** - `/resources/{faq, legal, pricing}`. Legal links to the privacy policy on `https://fluso.ai/privacy`; do not duplicate the policy in the docs. - **Release notes** - `/release-notes`. Customer-facing changes, newest first. - **Remote access** - `/remote/*`. Ways to use Fluso away from the desktop app. - **Workflows** - `/workflows/*`. Six concrete stories: bug-to-PR, content launch, knowledge recall, meetings, morning brief, and research-to-deck. diff --git a/content/docs/admin-panel.mdx b/content/docs/admin-panel.mdx index 1e90e30..63ab80e 100644 --- a/content/docs/admin-panel.mdx +++ b/content/docs/admin-panel.mdx @@ -89,4 +89,4 @@ Use **Network egress** to review the origins available to egress-governed sandbo ## Next -Read [Privacy](/resources/privacy) for the admin content boundary and [Security](/resources/security) for authentication, isolation, and governance logging. +See [Legal](/resources/legal) for Fluso's privacy policy. diff --git a/content/docs/deployment-models.mdx b/content/docs/deployment-models.mdx index f7189f1..26f67ce 100644 --- a/content/docs/deployment-models.mdx +++ b/content/docs/deployment-models.mdx @@ -18,7 +18,7 @@ Your deployment model decides who operates Fluso and where its runtime, durable Fluso Cloud is the standard managed service. It runs on AWS with European hosting by default. Fluso operates the application services, Agent runtimes, storage, and platform updates; you manage your workspace, users, connected Apps, and approval policies. -Choose it when you want to start without operating infrastructure. See [Privacy](/resources/privacy) for data handling and [Security](/resources/security) for encryption and isolation. +Choose it when you want to start without operating infrastructure. See [Legal](/resources/legal) for Fluso's privacy policy. ## Dedicated AWS VPC @@ -45,7 +45,7 @@ Agree on these boundaries before treating the design as approved: | Connected Apps | Which external systems may be read or changed, and what returned data Fluso may persist | - Running Fluso on-premises does not automatically keep model inference or connected-App data on-premises. External providers keep their own processing boundaries. Confirm every provider and route as part of the deployment design; [Privacy](/resources/privacy#sub-processors) lists the current sub-processors. + Running Fluso on-premises does not automatically keep model inference or connected-App data on-premises. External providers keep their own processing boundaries. Confirm every provider and route as part of the deployment design. See [Legal](/resources/legal) for Fluso's privacy policy. ## Operational telemetry diff --git a/content/docs/index.mdx b/content/docs/index.mdx index 18dbf85..1fab2c1 100644 --- a/content/docs/index.mdx +++ b/content/docs/index.mdx @@ -63,7 +63,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. + + Read Fluso's privacy policy. diff --git a/content/docs/introduction.mdx b/content/docs/introduction.mdx index 50af60f..f31620d 100644 --- a/content/docs/introduction.mdx +++ b/content/docs/introduction.mdx @@ -62,7 +62,7 @@ You will see how Fluso reads context, where it finds evidence, and how much revi Your workspace runs inside a dedicated environment. Data is not used to train shared models, is hosted in Europe, and is grounded in Switzerland through Prem AI's infrastructure. -Enterprise deployments can be scoped for a dedicated AWS VPC or an on-premises environment. Azure VNet support is coming soon. Compare the current [deployment models](/deployment-models), then see [Privacy](/resources/privacy) and [Security](/resources/security) for the data and infrastructure boundaries. +Enterprise deployments can be scoped for a dedicated AWS VPC or an on-premises environment. Azure VNet support is coming soon. Compare the current [deployment models](/deployment-models), then see [Legal](/resources/legal) for Fluso's privacy policy. ## Next diff --git a/content/docs/resources/faq.mdx b/content/docs/resources/faq.mdx index 38e1881..fe6e722 100644 --- a/content/docs/resources/faq.mdx +++ b/content/docs/resources/faq.mdx @@ -76,7 +76,7 @@ description: The questions that come up most often. What Fluso is, how it works, Deleting your account deletes your dedicated sandbox and all associated data, including your files, conversations, connected-account credentials, and other records held by Fluso. We do not retain your data after account deletion. - It reads emails when you ask it to (e.g., *"summarise my inbox"*) and as part of auto-task extraction. It does not keep a separate mailbox copy; requested content is processed under the controls described in [Privacy](/resources/privacy). + It reads emails when you ask it to (e.g., *"summarise my inbox"*) and as part of auto-task extraction. It does not keep a separate mailbox copy. See [Legal](/resources/legal) for Fluso's privacy policy. Gmail send tools follow your effective **Allow**, **Ask**, or **Deny** policy. Use **Ask** to review each draft before it sends; **Allow** or **Don't ask permission** can continue without a per-action prompt. @@ -95,7 +95,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). +See [Legal](/resources/legal) for Fluso's privacy policy. ## Pricing diff --git a/content/docs/resources/legal.mdx b/content/docs/resources/legal.mdx new file mode 100644 index 0000000..6cf2605 --- /dev/null +++ b/content/docs/resources/legal.mdx @@ -0,0 +1,13 @@ +--- +title: Legal +icon: scale +description: Fluso's privacy policy. +--- + +## Privacy policy + +Read Fluso's privacy policy on the Fluso website for information about how your data is collected, used, and protected. + + + View the full privacy policy on fluso.ai. + diff --git a/content/docs/resources/meta.json b/content/docs/resources/meta.json index 2aa753b..9cc6b5c 100644 --- a/content/docs/resources/meta.json +++ b/content/docs/resources/meta.json @@ -1,3 +1,3 @@ { - "pages": ["faq", "pricing", "privacy", "security"] + "pages": ["faq", "legal", "pricing"] } diff --git a/content/docs/resources/pricing.mdx b/content/docs/resources/pricing.mdx index 7063a3c..2798ed8 100644 --- a/content/docs/resources/pricing.mdx +++ b/content/docs/resources/pricing.mdx @@ -113,7 +113,7 @@ Obligation detection scans your connected apps for things you have committed to: The model depends on the feature. Fluso uses open-weight models for some workloads and proprietary model APIs for others. Agent Studio currently uses Gemini through OpenRouter. - Fluso Cloud stores workspace data in the EU by default. Model inference and connected-App processing follow the provider boundaries in [Privacy](/resources/privacy#sub-processors). Enterprise customers can scope alternative data residency. Your data is never used to train shared models. + Fluso Cloud stores workspace data in the EU by default. Model inference and connected-App processing have their own provider boundaries. Enterprise customers can scope alternative data residency. Your data is never used to train shared models. See [Legal](/resources/legal) for Fluso's privacy policy. Plus is the daily-driver tier: all apps, the Skills Marketplace, artifact generation, obligation and task automation every 12 hours. Pro raises tokens 20×, runs that automation constantly, lifts the meeting-notes cap, and adds confidential computing. Move to Pro when the 12-hour cadence or the Plus token allowance starts being the bottleneck. diff --git a/content/docs/resources/privacy.mdx b/content/docs/resources/privacy.mdx deleted file mode 100644 index 732aa6a..0000000 --- a/content/docs/resources/privacy.mdx +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Privacy -sidebarTitle: Privacy -icon: eye-off -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: EU. 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 processing; not used for training. | -| OpenAI | Underlying LLM processing; not used for training. | -| OpenRouter | Model routing for Agent Studio. | -| Google | Gemini model processing for Agent Studio through OpenRouter. | -| 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 - -The current [Admin panel](/admin-panel) can: - -- Store team membership, workspace roles, Agent access policies, access requests, and Microsoft Entra tenant metadata in the authenticated account's backend governance record. -- Review the identity and access changes recorded there. - -Directory verification and import, application inventory, seat controls, SSO, and runtime authorization enforcement require their owning Enterprise integrations. - -Admins cannot: - -- Read members' messages, drafts, or files. -- Access members' personal knowledge graphs. -- See content of a member's private projects. - -The governance audit view records persisted identity and access changes, not the content of any user's work. It is scoped to the selected account and is not a complete organization-wide security log. - -## Compliance - -Fluso is built by Prem AI. Enterprise engagements can scope a Data Processing Agreement, custom data residency, broader server-backed audit logging, and SSO (SAML/OIDC). The current governance record is durable, but its Microsoft Entra metadata does not verify a directory or provide SSO by itself. Prem has attained SOC 2 Type I; Type II is underway. See the [current security posture](https://www.premai.io/security-at-prem). - -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/content/docs/resources/security.mdx b/content/docs/resources/security.mdx deleted file mode 100644 index b00ebb1..0000000 --- a/content/docs/resources/security.mdx +++ /dev/null @@ -1,78 +0,0 @@ ---- -title: Security -sidebarTitle: Security -icon: shield -description: How Fluso is built to protect your data. Encryption, authentication, infrastructure isolation, 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). - -## Encryption - -| Data | Protection | -|---|---| -| In transit | TLS 1.2+ on every connection | -| Workspace files | Encrypted at rest (AES-256) | -| Database | Encrypted at rest | -| OAuth tokens | KMS-encrypted before storage in the backend database | -| Conversations and chat history | Encrypted at rest | - -OAuth tokens are encrypted before persistence and decrypted only by the backend paths that broker or refresh a connection. They are not exposed to the browser as stored credentials. - -## Authentication - -**User auth runs through Clerk.** Passwords, multi-factor authentication, and social login. Fluso doesn't see or store user passwords directly. - -**Connected apps use OAuth2.** When you connect Gmail, Calendar, Slack, or GitHub, Fluso never sees those passwords either. Tokens are scoped to exactly the permissions you approved on the OAuth screen. - -**Per-user isolation.** One user's credentials cannot access another user's data. Tokens, files, conversations, and the knowledge graph are scoped to the authenticated user. - -## Infrastructure - -**Sandbox containers.** Each user gets a dedicated container. Network policies prevent cross-user communication. - -**Token refresh.** OAuth tokens are refreshed automatically before expiry. Failed refreshes show as a "Reconnect" option on the connection's row under **Plugins** instead of silent denial. - -**Secret delivery.** Hosted runtime secrets use a one-time bootstrap payload: Docker receives it over stdin, while ECS uses an authenticated one-shot HTTP handoff. The payload is kept out of mounted files and the final process environment. - -**Governance audit logging.** Authenticated identity and access changes are stored in the backend governance record and shown in the [Admin audit log](/admin-panel#audit-log). This log covers the governance actions shown there; account-lifecycle, OAuth, and deletion auditing require their owning server integrations. Governance records do not contain the content of your work. - -## Account security - -A few things to do, regardless of plan: - -**Enable multi-factor authentication.** In Clerk's account settings. Fluso doesn't enforce it by default, but it's the single biggest improvement to account security and takes a minute. - -**Review connected apps monthly.** **Plugins → MCP**. Disconnect anything you've stopped using. Fewer connected apps means a smaller attack surface and a more focused knowledge graph. - -**Watch for phishing.** Fluso will never ask for your password by chat or email. Genuine support requests come from `@premai.io`. If something looks off, [email security](mailto:security@premai.io) directly to verify. - -**Report devices you don't recognise.** Clerk's session list shows active sessions. End any you don't recognise. - -## What Fluso never does - -Product controls and contractual commitments set these boundaries: - -- Operate outside the OAuth scopes granted to a connected app. -- Bypass the effective **Allow**, **Ask**, or **Deny** policy for a connected-app tool. -- Sell your data or disclose it outside contracted subprocessors. -- Train models on your private data. -- Access apps you haven't connected. - -OAuth scopes and tool policy enforce the connected-app boundaries. Contractual commitments apply where a technical control cannot express the boundary. - -## Compliance - -Enterprise engagements can scope custom data residency, SSO (SAML/OIDC), broader server-backed audit logging, SLA-backed availability, and a Data Processing Agreement. The current Microsoft Entra configuration stores tenant metadata and governance history; it does not verify the directory or provide SSO by itself. Prem has attained SOC 2 Type I; Type II is underway. See the [current security posture](https://www.premai.io/security-at-prem). - -[Contact us](mailto:sales@premai.io) for the security questionnaire and detailed compliance documentation. - -## Reporting a vulnerability - -Found something? [security@premai.io](mailto:security@premai.io). We respond within 24 hours. - -Coordinated disclosure is appreciated. We'll acknowledge receipt, work on a fix, and credit you publicly if you'd like. - - - Don't share your account credentials with anyone, including teammates. If a teammate needs access, invite them through your Team plan instead. Fluso staff will never ask for your password. - diff --git a/content/docs/workflows/knowledge-recall.mdx b/content/docs/workflows/knowledge-recall.mdx index cdae38e..2653cf5 100644 --- a/content/docs/workflows/knowledge-recall.mdx +++ b/content/docs/workflows/knowledge-recall.mdx @@ -70,7 +70,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. See [Legal](/resources/legal) for Fluso's privacy policy. ## Related diff --git a/public/_redirects b/public/_redirects new file mode 100644 index 0000000..a38137d --- /dev/null +++ b/public/_redirects @@ -0,0 +1,6 @@ +/resources/privacy /resources/legal 301 +/resources/privacy/ /resources/legal 301 +/resources/security /resources/legal 301 +/resources/security/ /resources/legal 301 +/llms.mdx/docs/resources/privacy/content.md /llms.mdx/docs/resources/legal/content.md 301 +/llms.mdx/docs/resources/security/content.md /llms.mdx/docs/resources/legal/content.md 301 From 8d5c60bbf39b8d25c5606ba1ac7aaf61b84322c3 Mon Sep 17 00:00:00 2001 From: Lorenzo Dalmazzo Date: Tue, 15 Sep 2026 12:03:22 +0000 Subject: [PATCH 2/3] docs: add terms of service to Legal page --- AGENTS.md | 2 +- content/docs/index.mdx | 2 +- content/docs/resources/legal.mdx | 14 +++++++++++--- 3 files changed, 13 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index baec624..4d8593a 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -18,7 +18,7 @@ The navigation keeps Home first, then sorts the top-level sections and the pages - **Deployment models** - `/deployment-models`. Current availability and operating boundaries for Fluso Cloud, dedicated AWS VPC, planned Azure VNet, and scoped on-premises deployments. - **Features** - `/features/*`. Approvals and permissions, Apps and MCP servers, Chat, Confidential mode, Imports, Memory, Projects, Skills, and Tasks. - **Get started** - `/going-deeper`, `/introduction`, `/quickstart`. These pages explain the path from first setup to daily use. -- **Reference** - `/resources/{faq, legal, pricing}`. Legal links to the privacy policy on `https://fluso.ai/privacy`; do not duplicate the policy in the docs. +- **Reference** - `/resources/{faq, legal, pricing}`. Legal links to the terms of service at `https://fluso.ai/terms` and privacy policy at `https://fluso.ai/privacy`; do not duplicate the policies in the docs. - **Release notes** - `/release-notes`. Customer-facing changes, newest first. - **Remote access** - `/remote/*`. Ways to use Fluso away from the desktop app. - **Workflows** - `/workflows/*`. Six concrete stories: bug-to-PR, content launch, knowledge recall, meetings, morning brief, and research-to-deck. diff --git a/content/docs/index.mdx b/content/docs/index.mdx index 1fab2c1..052b6ce 100644 --- a/content/docs/index.mdx +++ b/content/docs/index.mdx @@ -64,6 +64,6 @@ Pick a workflow that matches a problem you have right now. Each one is a story, Plans, limits, billing. - Read Fluso's privacy policy. + Read Fluso's terms of service and privacy policy. diff --git a/content/docs/resources/legal.mdx b/content/docs/resources/legal.mdx index 6cf2605..9a2ac03 100644 --- a/content/docs/resources/legal.mdx +++ b/content/docs/resources/legal.mdx @@ -1,13 +1,21 @@ --- title: Legal icon: scale -description: Fluso's privacy policy. +description: Fluso's terms of service and privacy policy. --- +## Terms of service + +The Fluso terms of service govern your use of Fluso. + + + View the full terms of service. + + ## Privacy policy -Read Fluso's privacy policy on the Fluso website for information about how your data is collected, used, and protected. +The Fluso privacy policy explains how Fluso collects, uses, and protects your data. - View the full privacy policy on fluso.ai. + View the full privacy policy. From 8797b0236085c64a23fb53672c72c964fe9e8035 Mon Sep 17 00:00:00 2001 From: Lorenzo Dalmazzo Date: Tue, 15 Sep 2026 12:08:44 +0000 Subject: [PATCH 3/3] docs: open legal policies in new tabs --- components/mintlify.tsx | 9 ++++++++- content/docs/resources/legal.mdx | 4 ++-- 2 files changed, 10 insertions(+), 3 deletions(-) diff --git a/components/mintlify.tsx b/components/mintlify.tsx index 7912e75..11edc66 100644 --- a/components/mintlify.tsx +++ b/components/mintlify.tsx @@ -98,11 +98,13 @@ export function Card({ title, icon, href, + newTab = false, children, }: { title: string; icon?: string; href?: string; + newTab?: boolean; children?: ReactNode; }) { const inner = ( @@ -127,7 +129,12 @@ export function Card({ if (href) { return ( - + {inner} ); diff --git a/content/docs/resources/legal.mdx b/content/docs/resources/legal.mdx index 9a2ac03..1c82126 100644 --- a/content/docs/resources/legal.mdx +++ b/content/docs/resources/legal.mdx @@ -8,7 +8,7 @@ description: Fluso's terms of service and privacy policy. The Fluso terms of service govern your use of Fluso. - + View the full terms of service. @@ -16,6 +16,6 @@ The Fluso terms of service govern your use of Fluso. The Fluso privacy policy explains how Fluso collects, uses, and protects your data. - + View the full privacy policy.