# Security and data

{% 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, shared with third parties, or used to train AI models. Every team member's content stays private to them, including from admins.

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 processed within your account only and never shared externally.

**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 never creates or sends calendar invites unprompted.

**Meetings**: recorded and transcribed only when Notetaker is explicitly enabled. If Notetaker is off, no meeting content is recorded or processed. Recordings, transcripts, and summaries are only visible to the individual who owns the calendar event – other team members only receive the summary if the owner explicitly shares it.

Learn more:

* [**What Fyxer needs access to and why**](https://support.fyxer.com/en/articles/13110675-what-fyxer-needs-access-to-and-why)
* [**APIs and permissions Fyxer uses during setup**](https://support.fyxer.com/en/articles/11130784-apis-and-permissions-fyxer-uses-during-setup)

***

### AI training and your data

Fyxer does not use your emails, meetings, or documents to train public or shared AI models – now or in the future. Your data is never sold, licensed, or used to improve outputs for other customers.

Fyxer does learn within each user's own account so it can improve draft tone, follow-up suggestions, and prioritization. On Starter and Professional plans, that learning is strictly individual and isolated from all other users. On Enterprise plans, Fyxer can learn patterns across a group to improve suggestions and automation, without exposing individual emails or content.

Learn more: [**AI training and your data: our commitment**](https://support.fyxer.com/en/articles/13193851-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/en/articles/13185411-what-team-members-can-and-can-t-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
* **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. If your organization requires a formal security questionnaire, SOC 2 report, or Data Processing Agreement, contact <support@fyxer.com>.

Learn more: [**Compliance and certifications**](https://support.fyxer.com/en/articles/11040069-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/en/articles/11099253-where-fyxer-data-is-stored-server-locations-jurisdiction). It's particularly relevant if your organization has data residency requirements.

***

### What happens when someone leaves

When you remove someone from your organization, their access is revoked immediately. Fyxer can no longer read, process, or generate drafts from their data.

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 cancelling Fyxer**](https://support.fyxer.com/en/articles/10922460-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 <support@fyxer.com>.

***

### Next up <a href="#next-up" id="next-up"></a>

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: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.fyxer.com/teams-and-admins/security-and-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
