FLUHFEE
Privacy Policy
How Fluhfee handles information when you prepare, share, and connect meetings.
Last updated: September 26, 2026
1. Who this policy covers
This policy describes how Fluhfee (“we,” “us,” or “our”) handles personal information through fluhfee.com and the Fluhfee application. It covers visitors, waitlist subscribers, account holders, and meeting participants. Contact us at privacy@fluhfee.com with privacy questions or requests.
A meeting host chooses what information to request and share. If you participate in a meeting organized by your employer or another organization, its own privacy practices may also apply. We handle account administration, billing, security, and our direct communications for our own service purposes; we process host-directed meeting content to provide the requested meeting features. Hosts remain responsible for the notices and permissions their activities require.
2. Information we collect
- Account and profile information: your name, email address, profile details you provide, account settings, authentication records, and records of acceptance of the legal terms when captured during registration. Passwords are stored as hashes.
- Meeting and People information: titles, dates, times, time zones, descriptions, joining links, agendas, contact names and emails, participant answers, optional profile details, notes, uploaded materials, and sharing settings. We also store generated preparation content and AI conversations used within the app.
- Communications: waitlist signups and optional feedback, support requests, and records of invitations, reminders, and other service emails.
- Billing information: plan, subscription, customer, and payment-status information. Stripe processes payment details; Fluhfee does not store full card numbers.
- Technical information: information needed to operate and secure the service, such as request logs, device or browser information, session identifiers, errors, and feature usage.
Where information comes from
We receive information directly from you, from hosts and participants who add meeting or contact information, from services you choose to connect, from payment and service providers, and through technical interactions with the app. Contact records may include information another user has supplied about you. We do not obtain access to your entire email inbox merely because you connect a calendar.
3. Google sign-in and Google Calendar
Google sign-in is separate from Calendar access. When you link or use Google sign-in, we receive your Google account identifier, verified email address, and basic profile information such as your name and profile picture, when provided. We use this information to identify you and authenticate your linked Fluhfee account. Google sign-in alone does not grant Calendar access.
If you separately connect Google Calendar, we receive your account identifier and email address, authorization tokens, and event information needed for the integration. Event information can include event IDs, titles, descriptions, start and end times, joining links, cancellation status, and attendee names and email addresses. The meeting browser currently lists upcoming timed events from your primary calendar.
We use this information to show your meetings, let you select meetings to import into Fluhfee, fill in meeting details, add imported guests to your People list where the import flow offers this, and refresh linked meeting information. Google Calendar access is read-only: Fluhfee does not create, edit, or delete Google Calendar events. Existing Google Meet links can be imported with an event. Changes you make to an imported meeting inside Fluhfee are not written back to Google Calendar. Connecting your calendar or browsing meetings does not itself send Fluhfee invitations.
We store connection details and encrypted authorization tokens so the connection can keep working without asking you to sign in for every refresh. Selected imports can be saved as drafts on your device and, when saved in Fluhfee, in your account. Imported information becomes part of the Fluhfee meeting and follows its sharing settings. Relevant imported content may also be processed by the preparation and AI features described below.
Fluhfee’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google user data, use it for advertising or credit decisions, or use it to train general-purpose AI or machine-learning models. We use it to provide the meeting features described here. Human access to Google user data is limited to your affirmative permission for specific data, security needs, legal obligations, or aggregated internal operations permitted by that policy. Transfers are limited to the purposes permitted by that policy, including providing features with your consent, security, legal obligations, or a business transfer with your prior explicit consent.
4. Other connected services
If you connect Microsoft Outlook / Teams or Zoom, we process the connected account details, authorization credentials, and meeting information made available by that service to provide browsing, importing, linking, refreshing, and meeting-creation features you use. Available fields and features differ by provider.
Apple Calendar and other calendar invitations can be imported from an .ics file or pasted invitation. That import processes the information you supply; it does not establish ongoing access to your Apple account. Connected services have their own privacy policies and permission controls.
5. How we use information
We use information to provide and maintain Fluhfee, authenticate accounts, prepare and organize meetings, manage contacts, deliver requested communications, process subscriptions, answer support requests, prevent abuse, troubleshoot problems, and meet legal obligations. Waitlist contact information is used for the launch updates you request; you can ask us to stop those updates.
AI features: Fluhfee uses Anthropic to generate features such as agenda and question suggestions, meeting preparation assistance, and meeting overviews. Relevant meeting content, participant responses, and chat messages may be sent to that provider when those features run. Outputs may be saved with your meeting or conversation. Review generated content before relying on or sharing it. We do not use Google user data to train general-purpose models or authorize that use by AI providers. Do not submit passwords, government identifiers, payment-card data, medical records, or information you are not authorized to share. Optional personal questions should remain optional.
7. Cookies, storage, and security
We use cookies and similar storage for sign-in, security, preferences, and draft recovery. Some meeting drafts and preferences are stored in your browser. You can clear them using the app’s draft controls or your browser’s site-data controls; doing so may sign you out or remove unsaved work. Resources such as fonts, hosted images, payment pages, and connected-service pages may also send technical request information to their providers when loaded.
Visitor analytics: Fluhfee’s built-in visitor analytics tracker is disabled. Operational and security logs still support the service. If we introduce optional analytics or advertising storage, we will update this notice and implement any required choices before enabling it.
Browser privacy signals: Fluhfee does not currently change its data handling in response to the older “Do Not Track” browser setting. We do not sell or share information for cross-context behavioral advertising regardless of whether Global Privacy Control is enabled. If our practices change, we will update this notice and implement any required consent or opt-out controls before that change.
We use measures such as encrypted connections, access controls, hashed passwords, and encryption of stored Google and Zoom integration tokens. No service can guarantee absolute security. Our service providers may process information in countries other than where you live.
8. Retention, disconnecting, and deletion
We retain information while needed to provide the service and for legitimate purposes such as security, resolving disputes, and legal or accounting obligations. The retention period depends on the information and purpose. Account and saved meeting records ordinarily remain until you delete them or close the account; authentication tokens remain while a connection is active; billing, support, security, and backup records may need different retention periods. We consider the sensitivity of the data, the feature it supports, legal duties, and the need to investigate problems. We do not promise that every copy disappears immediately when a deletion is requested.
To disconnect a calendar or meeting provider, open Account → Calendars → Disconnect. Disconnecting stops Fluhfee’s ongoing access through that connection and removes its stored connection credentials after successful disconnection. You can also remove Google access through your Google Account connections.
Disconnecting a provider does not automatically delete meetings, contacts, or drafts you already imported into Fluhfee. Delete those items separately, delete your account in Account → Security, or contact us for help. Account deletion removes the account and associated owned records and initiates cleanup of uploaded files and integrations. Browser drafts must be cleared on each device. Copies already shared with other people, records held independently by a meeting host, and records retained for legal or security reasons may remain. Backups and service-provider records may remain for their applicable retention periods.
9. Your choices and requests
You can update account information, manage email preferences, edit or delete your own content, and disconnect integrations using the available controls. Depending on where you live and applicable law, you may have rights to access, correct, delete, obtain a copy of, restrict, or object to processing of your personal information, or withdraw consent.
Send requests to privacy@fluhfee.com. We may need to verify your identity. If you submitted a guest response without an account, include the email address and meeting details so we can locate it. Where an organization controls the information, we may need to coordinate with its meeting host. You may also have a right to complain to your local data protection authority.
California and other regional privacy rights
Where the relevant law applies, California residents may request information about the categories and specific pieces of personal information collected, its sources and purposes, and the categories of recipients; request deletion or correction; opt out of sale or sharing; and limit certain uses of sensitive personal information. The categories, purposes, sources, and recipients used by Fluhfee are described above. We do not offer financial incentives for providing personal information.
You may submit a request through privacy@fluhfee.com without creating an account. An authorized agent may submit a request with evidence of authority; we may separately verify your identity where the law allows. We use verification information only to handle the request and protect against unauthorized access. We will respond within the period required by applicable law, explain relevant exceptions or denials, and explain any available appeal process. You will not be unlawfully discriminated against for exercising a privacy right.
If European, UK, or similar data-protection laws apply to our processing, the relevant basis may be providing a requested service, your consent, compliance with law, or legitimate interests such as securing the service, subject to your rights. You may ask us about the basis for a particular use and any applicable international-transfer safeguards at privacy@fluhfee.com. Withdrawing consent does not affect the lawfulness of earlier processing.
10. Children
Fluhfee is intended for adults and is not directed to children. If you believe a child has provided personal information, contact us so we can investigate and address it.
11. Changes to this policy
We may update this policy as the service changes. We will update the date shown above and provide additional notice when required. If we propose a new use of Google user data beyond what you authorized, we will provide notice and obtain any required consent before that use.