Security & trust

Security and privacy

How Fido protects your data: encryption, role-based access, organization isolation, an append-only history, backups, and how the AI assistant handles your data.

5 min read Updated

Book a demoContact sales

See it on fetchfido.ai

Interpreting organizations handle sensitive information, and Deaf consumers trust them with their schedules, preferences and accommodations. Fido protects confidentiality at every layer of the platform.

Controls in place

  • Encryption in transit and at rest
  • Role-scoped access control across all portals
  • An append-only audit log, where entries cannot be edited or deleted
  • Organization-scoped data isolation in a multi-tenant architecture
  • Login identity kept separate from profile data, so a person's login identity is never exposed to an organization
  • Independent deletion of an organization's data on offboarding
  • Soft delete with history versioning

Your data stays yours

Under Fido's Terms of Use, you own the data you put into the service. Fido does not sell your data, does not share identifiable data except to operate the service for you, and does not use the data an organization puts into Fido to compete with that organization. The only use beyond running Fido is aggregated, de-identified statistics that never identify you, your organization or any individual.

You can export your data while your account is active and during a wind-down window after your agreement ends.

Encryption

  • In transit. The Fido app is served over TLS 1.2 or higher.
  • At rest. Data, files and backups are encrypted using AES-256.
  • Keys. Encryption keys are managed by the cloud provider's key-management service and rotated on a regular schedule.

Access control

  • Role-based access. Organization admins, schedulers, providers, clients and consumers each see only what their role allows. A consumer never sees billing, and a client never sees provider pay.
  • Role permissions. Admins set what each scheduler and staff role can do in every module, with Read, Write, Edit and Delete, then fine-tune for an individual person. Admin accounts keep access to everything. Permission changes are written to History & Logs.
  • Single sign-on. People can sign in with Google or Microsoft.
  • Least privilege. Fido staff access to production data is limited to the people who need it and is revoked promptly on a role change or departure. Staff with access are bound by confidentiality obligations.
  • Logged access. All access to sensitive data or actions is logged.

Organization isolation

Every organization operates in its own logically isolated environment on shared, continuously maintained infrastructure. One organization cannot see, query or modify another organization's data. Access is scoped on every request to the signed-in user's organization and role.

Data is shared across organizations only when a provider or customer opts in through the Fido Network, and only to the extent they choose.

What each stage shares

A request carries what is needed to schedule the job. A broadcast shows when, where, the setting and travel. After a provider accepts, they receive the detail the job requires. Consumers never see billing, and clients never see provider pay.

Audit and history

History & Logs is a read-only record of who changed what and when, with the earlier and new value of each field. The record covers status changes, sign-ins, imports, exports and automatic changes made by the system. Financial records keep the rate and currency they were created with.

Infrastructure and availability

Fido runs on Amazon Web Services, and customer data is hosted in the United States. Organizations that need their data hosted in their own country can request regional hosting.

  • The application runs in containers with no public IP address behind load balancers.
  • The application load balancer uses a TLS 1.3 and 1.2 security policy.
  • The production database is encrypted with a customer-managed encryption key, has deletion protection on and is not publicly accessible.
  • Secrets are stored in AWS Secrets Manager.
  • AWS GuardDuty monitors for threats, and AWS CloudTrail records account activity across regions with log-file validation.
  • Container images are scanned for vulnerabilities on push.
  • Storage buckets block public access.
  • Database storage is replicated across multiple availability zones, and failed application containers are replaced automatically.
  • The platform is under continuous health monitoring.

Backups and recovery

Encrypted backups run continuously and are stored redundantly, so data can be restored to any point in the last 7 days. Fido's recovery objectives are to restore service within 24 hours with no more than 15 minutes of data loss.

Monitoring and incident response

Fido monitors for unauthorized access and anomalous activity, retains audit logs, and responds to security incidents through detection, containment, remediation and notification. If a security incident affects your data, Fido notifies affected customers without undue delay and in line with applicable law and contractual commitments.

Vulnerability management

Fido checks and tests the system for vulnerabilities through automated scanning and internal review throughout product development, and acts promptly on what it finds.

The AI assistant and your data

  • The built-in assistant sends the model only the data the signed-in person is already allowed to see, plus the current conversation.
  • Data from other organizations, deleted records and previous sessions is never used in an assistant session.
  • The assistant acts as the signed-in person, and every change waits for a confirmation.
  • Your data is not used to train AI models. The AI platform Fido uses does not train on data submitted through its API.
  • An organization can connect its own AI provider key instead, so AI runs under its own provider account.
  • Assistant conversations are saved in History & Logs for the organization's team.

How long data is kept

Data Retention
Account and service data Kept while the account is active. After the agreement ends, you can export for 30 days, then Fido deletes or de-identifies it within 90 days.
Financial and tax records Up to 7 years, for accounting and tax obligations.
Security and audit logs Up to 12 months, then archived or purged.

Some records are soft-deleted, which hides them while keeping them for audit, dispute resolution and historical accuracy. Permanent deletion can be requested.

Documents on request

Fido provides a Business Associate Agreement, a Data Processing Agreement, a FERPA addendum, a HECVAT Lite (under a mutual NDA), a subprocessor list and an accessibility self-assessment on request. Use the request form on the Security page. See Compliance for what each covers.

Responsible disclosure

Report a suspected vulnerability to security@fetchfido.ai. Fido acknowledges reports promptly, keeps the reporter updated and credits researchers who report responsibly. Privacy questions go to privacy@fetchfido.ai.

For a security review with the Fido team

A live walkthrough built around your kind of work.

Book a demoContact sales