Privacy Policy

This Privacy Policy explains what information FLOR collects, how we use it, who we share it with, and the choices you have. We aim to keep this short and plain.

What we collect

• Account data: your name, email, sign-in identifiers from Google.
• Captures you create: text, voice recordings, transcripts, attachments, generated documents.
• Operational metadata: sign-in times, device info, IP address (stored as a salted hash for legal acceptance records).
• Workspace data: people you add, preferences, templates.

How we use it

• To provide, secure, and improve the Service.
• To generate the documents you ask FLOR to draft.
• To communicate about your account, security, and feature updates.
• To meet our legal obligations.

What we do not do

• We do not sell your data.
• We do not use your content to train AI models.
• We do not advertise to you.

FLOR Connect browser extension

FLOR Connect is an optional browser extension that connects an authorized FLOR workspace to an approved patient page. Before the first connection, FLOR identifies the data categories the enabled capability may read and requires the user to affirmatively authorize the selected workspace.

• Approved-page context: patient identity and encounter landmarks needed to match existing governed FLOR work. FLOR Connect does not use arbitrary browsing history or access arbitrary tabs.
• User-selected evidence: selected text and, only when separately enabled, an explicitly selected document. Document acquisition is disabled for the initial controlled beta.
• Safety and audit evidence: adapter and extension versions, page-signature compatibility, bounded action outcomes, revocation state, and verification evidence. A certification diagnostic contains page structure and landmark presence only, never field values, raw page text, screenshots, cookies, or patient identifiers.

Short-lived extension authentication remains in Chrome session storage and is cleared when the browser session ends, the authorization expires, access is revoked, or policy denies the connection. Patient-page content is not persisted in extension storage. Server records retain only the governed workspace data and minimum audit evidence required for security, policy, verification, and regulatory obligations.

FLOR Connect uses this data only to provide or secure its single purpose. We do not sell it, use it for advertising, use it for credit or lending, or transfer it for unrelated purposes. FLOR Connect follows the Chrome Web Store Limited Use requirements. External writes require separate platform certification, workspace policy, current patient and encounter validation, user authority, and human confirmation. Claim submission is prohibited.

Workspace administrators can disable FLOR Connect or revoke an installation. Account and workspace deletion requests follow the retention rules below; security, legal-acceptance, and regulated audit records may be retained for the applicable required period.

Subprocessors

We use carefully selected vendors to operate the Service: cloud hosting and database, AI model providers, email delivery, error monitoring, and telephony when you opt in. Each vendor is bound by appropriate contractual safeguards, including a Business Associate Agreement (BAA) where they handle protected health information.

Encryption

Data is encrypted in transit using TLS 1.2+ and at rest using AES-256 on the storage layer.

Retention

Your captures and generated documents are kept until you delete them or close your account. Audit logs and legal-acceptance records may be retained longer to meet regulatory obligations.

Your rights

• You can export or delete your data at any time from settings or by emailing us.
• If you are in a jurisdiction with additional rights (e.g., GDPR, CPRA), you may exercise them by contacting us.

Children

FLOR is not intended for anyone under 18.

Contact

Privacy questions: privacy@flor.app.