> For the complete documentation index, see [llms.txt](https://docs.fyxer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyxer.com/teams-and-admins/security-and-data.md). # Security and data What you need to know about how Fyxer handles your team's data, and what you can control. {% hint style="success" %} * [The short version](#the-short-version) * [What Fyxer accesses and why](#what-fyxer-accesses-and-why) * [AI training and your data](#ai-training-and-your-data) * [Privacy within your team](#privacy-within-your-team) * [Certifications and compliance](#certifications-and-compliance) * [Where data is stored](#where-data-is-stored) * [What happens when someone leaves](#what-happens-when-someone-leaves) * [For your IT or security team](#for-your-it-or-security-team) {% endhint %} ### The short version Fyxer only accesses what's needed to deliver the features you enable. * Your data is never sold, and is only shared with the service providers we need to run Fyxer * You choose whether your data helps train Fyxer's own AI models * Every team member's emails, drafts, and meeting notes are private to them by default For the full picture, visit the [**Fyxer Trust Center**](https://trust.fyxer.ai) and [**Fyxer Security page**](https://www.fyxer.com/security)**.** *** ### What Fyxer accesses and why Fyxer connects to email and calendar to do its job. Here's what it accesses and what it's used for: **Email**: read to categorize and prioritize incoming messages, generate draft replies, and support follow-ups. Email content is only shared with the service providers we need to deliver these features, and is never sold or made public. **Calendar**: used to check availability for scheduling and to draft scheduling emails. When someone books via your scheduling link, the meeting is confirmed automatically based on your availability. Outside of this, Fyxer only takes scheduling actions within the settings you choose. **Meetings**: recorded and transcribed only when Notetaker is enabled. If Notetaker is off, no meeting content is recorded or processed. Recordings, transcripts, and summaries are only visible to the person who owns the calendar event, team members invited to the meeting, and anyone the owner chooses to share them with. Learn more: * [**What Fyxer needs access to and why**](https://support.fyxer.com/article/what-fyxer-needs-access-to-and-why) * [**APIs and permissions Fyxer uses during setup**](https://support.fyxer.com/article/apis-and-permissions-fyxer-uses-during-setup) *** ### AI training and your data Fyxer trains its own AI models to improve features like drafting, inbox sorting, and transcription. These models are private to Fyxer, and we never let other AI providers train their own general models on your data. Before any content is used, we replace names and email addresses with codes and remove sensitive information. You can opt out at any time from [Dashboard](https://app.fyxer.com/) → Settings → Account → Allow Fyxer to use my data to train and improve its AI models, and admins can opt out their whole organization. On the Enterprise plan, we don't use your content or data to train models that serve other customers, and the setting to opt out is on by default. Fyxer also learns each user's writing style and preferences so it can draft in their voice. This doesn't change any AI model, and it keeps working if you opt out of training. Learn more: [**AI training and your data: our commitment.**](https://support.fyxer.com/article/ai-training-and-your-data-our-commitment) *** ### Privacy within your team Being in the same organization does not give team members visibility into each other's data. Every person's emails, drafts, and meeting notes are private to them. This applies to admins too: Super Admins control settings and billing, but cannot read any team member's inbox, view their drafts, or access their meeting notes. Learn more: [**What team members can and can't see.**](https://support.fyxer.com/article/what-team-members-can-and-cant-see) *** ### Certifications and compliance Fyxer holds the following certifications: * **SOC 2 Type II**: audited controls for security, availability, and confidentiality * **ISO/IEC 27001**: international information security management standard * **UK GDPR and EU GDPR**: compliant for all users * **HIPAA**: eligible for healthcare organizations on Enterprise plans * **CASA Tier 2**: Cloud Application Security Assessment Fyxer works with organizations in regulated industries including healthcare, legal, and financial services. Our [Data Processing Agreement](https://app.fyxer.com/terms/dpa) is available online. If your organization requires a formal security questionnaire or SOC 2 report, contact Learn more: [**Compliance and certifications.**](https://support.fyxer.com/article/compliance-and-certifications) *** ### Where data is stored Fyxer stores data in secure cloud infrastructure. For details on server locations and data jurisdiction, see: [**Where Fyxer data is stored.**](https://support.fyxer.com/article/where-fyxer-data-is-stored-server-locations-jurisdiction) It's particularly relevant if your organization has data residency requirements. To see the service providers we use, and where they process data, visit our [sub-processor list.](https://app.fyxer.com/legal/sub-processors) *** ### What happens when someone leaves When you remove someone from your organization, their access is revoked immediately. If their account uses your company email domain, their content, including meeting recordings and transcripts, stays with your organization. If they joined with a personal email address, their account goes back to being an individual account. They may still see folders or labels in their inbox that Fyxer previously created. These are native to their email provider and can be removed manually. Their presence does not indicate ongoing access. Learn more: [**What happens to data after canceling Fyxer.**](https://support.fyxer.com/article/what-happens-to-your-data-after-cancelling-fyxer) *** ### For your IT or security team Direct your security team to the [**Fyxer Trust Center**](https://trust.fyxer.ai) and [**Fyxer Security page**](https://www.fyxer.com/security) for certifications, compliance documentation, and detailed security information. For questions about data handling, security reviews, or Enterprise security requirements, contact For privacy questions or requests, contact . To see the service providers we use, visit our [sub-processor list.](https://app.fyxer.com/legal/sub-processors) *** ### Next up Ready to spread the word? * Next: [**Roll out Fyxer – a manager's guide**](/teams-and-admins/roll-out-fyxer-a-managers-guide.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.fyxer.com/teams-and-admins/security-and-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.