Privacy policy

1. Scope and responsibility

This policy is effective September 29, 2026 and describes how Chiefora processes information through getchiefora.com. Chiefora operates the service from Pakistan for users worldwide. Privacy questions and requests may be sent to support@getchiefora.com. This product has no affiliation with chiefora.com.

Workspace administrators choose what meeting information to add and who may access it. If someone includes your information in a workspace, its administrator may also be an appropriate first contact. Depending on the context and applicable law, Chiefora may act as a controller or business for account and service data and as a processor or service provider for organization workspace content.

2. Information processed by the service

Information may come from you, other workspace members, or a Fathom account you connect.

• Account information: name, email address, authentication identifiers, and workspace membership. The authentication service handles sign-in credentials and sessions.
• Workspace content: meeting titles, dates, participants, transcripts, notes, source links, projects, commitments, decisions, questions, risks, and reviewed AI output.
• Integration information: Fathom authorization tokens, connection status, meeting identifiers and metadata, sync state, and webhook records. Tokens are encrypted in the application’s database.
• Service information: session cookies, theme preferences, locally stored demo changes, and technical request, security, or error information handled by Chiefora and its hosting and service providers.

3. How information is used

The application uses account and workspace information to sign you in, control access, store meeting records, support search, generate requested analysis and briefs, track follow-up work, and create in-app reminders. Integration information enables meeting sync, selected imports, and optional automatic updates.

Where applicable law requires a legal basis, processing may be necessary to provide the service you request, pursue legitimate interests such as security and product reliability, comply with law, or act with consent. You may withdraw consent for future processing where consent is the applicable basis. Chiefora does not use workspace meeting content for advertising.

4. Chiefora AI

When you request analysis, Chiefora AI sends relevant meeting text from the server to its configured model provider. Long transcripts may be processed in sections. Requested executive briefs also use relevant workspace information. AI output is saved for review; importing a transcript alone does not confirm commitments or decisions.

Model and infrastructure providers process requests outside your browser under their applicable agreements and account settings. Their retention, training use, and processing locations may differ. Do not submit information that you are not authorized to process, and review AI output before relying on it. You can use manual import and tracking without requesting AI analysis.

5. Access and service providers

Authorized workspace members can access imported workspace meetings and associated records. Your Fathom connection and pre-import meeting list are scoped to your user and organization; a meeting becomes workspace content when you import it.

Chiefora uses service providers including Supabase for authentication and database services, Vercel for hosting, configured model providers for Chiefora AI, and Fathom when you connect it. Because Chiefora is available worldwide and uses international providers, information may be processed outside your country. Chiefora handles cross-border processing according to applicable law and any required contractual or legal safeguards.

6. Cookies and browser storage

Session cookies support sign-in. A short-lived OAuth cookie helps validate Fathom connection attempts. Browser local storage remembers the light or dark theme and changes made to the sample demo workspace.

Clearing browser storage can sign you out or reset local preferences and demo changes. Chiefora does not currently use advertising cookies. Hosting and security providers may process technical request information needed to operate and protect the service.

7. Retention and disconnecting Fathom

Account and workspace records are generally retained while the relevant account or workspace remains active and until they are deleted by an authorized user or through a verified request, subject to legal, security, backup, and dispute-resolution needs. Meeting records do not currently expire automatically. Operational logs and backups follow the retention schedules of Chiefora and its providers.

Disconnecting Fathom deletes the locally stored connection credentials and private meeting catalog; it does not delete previously imported workspace meetings or revoke the provider authorization. Revoke Chiefora’s access in Fathom settings as well. Browser-storage removal does not erase records stored on the server.

8. Security and your choices

The application checks workspace membership, uses database access controls, and encrypts stored integration tokens. These controls do not guarantee that every security incident can be prevented.

Depending on applicable law and the circumstances, you may have rights to access, correct, delete, or obtain a copy of personal information, restrict or object to processing, withdraw consent, or complain to a regulator. Send requests to support@getchiefora.com. Chiefora may verify your identity and authority, and workspace administrators can help identify organization records containing your information.

9. Contact and policy updates

Chiefora may update this policy when providers, data uses, legal requirements, or user controls change. The effective date will be updated, and material changes will be communicated through the service or another reasonable channel when required by law.

Contact Chiefora at support@getchiefora.com with privacy questions, requests, or complaints. Do not send passwords or unnecessary sensitive meeting content by email.