Privacy Policy

Famant is a service operated by Antutive AB (“Famant”, “we”, “us”, “our”), a private limited company (aktiebolag) established and registered in Sweden. For the purposes of the EU General Data Protection Regulation (GDPR) and equivalent data-protection laws worldwide, Antutive AB is the data controller for the personal data processed through the Service, except where this Policy states otherwise. Because we are established in Sweden, our lead supervisory authority is the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, “IMY”).

Famant is available to users worldwide, excluding a small number of restricted countries and regions (see our Terms & Conditions). Wherever you use it, your personal data is processed mainly in the European Union, and we apply the protections in this Policy to all users, supplemented by any additional rights your local law gives you.

You can reach us, including on any privacy matter or to exercise your rights, at hello@famant.com. Our full company details are in section 20.

This Policy explains how we handle personal data when you use the Service. It should be read together with our Terms & Conditions.

Famant is organised around a family/household account. Within that account, members have the roles of owner, admin, or member (a member may be an adult or a child under parental supervision). Some data is personal (visible only to the member who created it, and, for a child, to their parent), and some is family/shared (visible to family members according to the visibility and permission settings you choose).

We act as the data controller for the personal data processed to deliver the Service. The family owner and admins control certain settings (for example, who is invited, role assignments, module permissions, and consent for child members); where they do so, they are responsible for using those controls lawfully and fairly toward other members.

3.1 Account and identity data

3.2 Family and relationship data

3.3 Application content you create

Content you and your family create in the Service. Each item carries a visibility setting (family/public, personal, role-admin, or parent-child).

3.4 AI and communication data

3.5 Device, notification and diagnostic data

3.6 Children’s data

Where a family includes child members, we process the child’s display name, role, date of birth (for age verification), the family content the child creates, and the parental-consent records associated with them. A child’s information may also appear within other content , for example in calendar events, documents you scan, or assistant conversations. See section 15.

We do not knowingly collect personal data directly from a child outside the family-account structure, and we do not create marketing or advertising profiles of children.

3.7 Connected-calendar data (optional)

If you are an adult member and choose to connect an external calendar (see 9.2), we also process:

Through this integration we do not read or store event descriptions, attendee or guest lists, locations, attachments, organiser details, or any other event field.

Some features can involve special-category data under GDPR Article 9, in particular dietary profiles and allergen information (which relate to health), and any health, identity, or similar sensitive information that may appear in documents or receipts you choose to scan into the document vault.

We process this data only to provide the features you ask for (for example, flagging allergens in a meal plan, or extracting data from a document you upload). Our lawful basis for processing special-category data is your explicit consent (GDPR Article 9(2)(a)), given when you choose to enter such information or scan such a document. You are not required to provide special-category data to use the core Service, and you can delete it at any time.

Please avoid uploading sensitive documents you do not need Famant to store.

• Directly from you, when you register, create or upload content, configure settings, use the AI assistant, or contact us.
• From your family owner/admin, who may create member profiles, send invitations, set permissions, and provide consent on a child’s behalf.
• Automatically, technical, session, device, notification, audit, and diagnostic data generated when you use the Service.
• From sign-in providers, if you choose Google or Apple sign-in, we receive identifiers and basic profile data from that provider through a native ID-token flow (we do not use Firebase Authentication).
• From connected calendar providers, if you are an adult member and choose to connect Google Calendar or Apple iCloud, we receive the limited event and account details described in 3.7 from the calendars you select.

We do not buy personal data from data brokers, and we do not enrich your profile with data purchased from third parties.

We process personal data for the following purposes, relying on the legal bases shown:

Where we rely on legitimate interests, we have weighed those interests against your rights and freedoms. You can object to such processing (see section 16). Where we rely on consent, you can withdraw it at any time without affecting processing already carried out.

Famant includes AI-powered features: the voice/text assistant, suggestions, receipt and document OCR (text/data extraction), and recipe generation. These features are provided with the assistance of Google’s Gemini models, accessed through Google’s API. We disclose this in line with transparency expectations under the GDPR and the EU AI Act.

What is sent to the AI provider (Google)

• the text of your assistant prompts and voice commands (speech is transcribed on your device first);
• relevant family context needed to fulfil your request (for example, names and roles of family members, upcoming calendar events created in Famant, and member-scoped recent context retrieved from your family’s AI “memory”);
• images and documents you scan, for OCR text and structured-data extraction;
• web page content or dish names you provide for recipe extraction/generation; and
• text to be converted into embeddings for context and search.

What we store

• your conversations (prompts and the assistant’s responses) as threads and turns;
• OCR-extracted text and structured data linked to the relevant document or expense; and
• embeddings derived from your content, scoped to your family and member and filtered by visibility, so the assistant only retrieves context the requesting member is allowed to see.

Important transparency points

• AI output can be wrong. It may be inaccurate, incomplete, or unsuitable for your purpose. AI features are an assistant only and do not provide professional (legal, financial, medical, or nutritional) advice. Review AI output before relying on it.
• No training on your data. We do not use your User Content to train our own models. We use the paid tier of Google’s Gemini API, whose terms exclude the use of content submitted through the API to improve Google’s models.
• Connected-calendar events are excluded from AI. Events imported from a Google Calendar or Apple iCloud calendar you connect are never sent to our AI service, never indexed for AI search or assistance, and never used to train or improve any AI or machine-learning model. The assistant therefore does not see or take account of those events.
• Provider processing. We use Google’s Gemini API as a service provider to process your requests. We require our providers to process data only to provide the Service to us and to apply appropriate safeguards. Google’s processing of data submitted through its API is also subject to Google’s terms applicable to our account; see section 11 on international transfers.
• Access control for AI context. AI memory and embeddings are filtered by family, member, role, and visibility.
• We may apply rate limits and quotas to AI features.

The AI assistant may suggest actions (for example, proposing a calendar entry, a task, a recipe, or a multi-step action) and may use anonymised “learned patterns” to make those suggestions more relevant. These are suggestions only; they take effect only after a person confirms them.

We do not make decisions that produce legal effects concerning you, or similarly significantly affect you, based solely on automated processing within the meaning of GDPR Article 22. You can turn off the learning feature and delete learned data at any time in the app’s privacy settings.

We share personal data only as needed to operate the Service: with service providers acting on our behalf under a data processing agreement (9.1); with sign-in and calendar services you choose to use, which receive data at your direction (9.1 and 9.2); and in the limited cases described at the end of 9.1. We do not sell personal data, and we do not share it for advertising.

9.1 Service providers

We may also disclose personal data where required by law, to respond to lawful requests from public authorities, or to protect the rights, safety, and security of our users, the public, or Famant. If we are ever involved in a merger, acquisition, or asset sale, we will require the recipient to honour this Policy and will notify you of any change in control of your data.

Not used: Famant does not use payment processors, or advertising or attribution SDKs. Apart from Google Analytics for Firebase, which runs only if you turn it on (see section 14), we do not use third-party product-analytics tools such as Amplitude, Mixpanel, PostHog, or Segment.

9.2 Connected calendars (Google Calendar and Apple iCloud)

Connecting a calendar. An adult member can connect their own calendar from Google Calendar or Apple iCloud, so that their events appear alongside family events in Famant, and events in Famant can appear in their own calendar. Connecting a calendar is optional and is switched on only by the person whose calendar it is, from Settings → Connected Calendars. We ask for your consent at that moment, separately from signing up.

Connecting an account does not by itself sync anything. After connecting, you choose which individual calendars on that account should sync. Until you choose at least one, no event data moves in either direction.

Only adults can connect a calendar. Members under 18 cannot connect an external calendar, and a parent or guardian cannot connect one on a child’s behalf. Events created by, or assigned to, a member under 18 are never sent to an external calendar provider, even when they appear on a connected adult’s Famant calendar. Where we cannot establish that everyone attached to an event is an adult (for example, because a member has no date of birth on record), the event is not sent.

What we read. From the calendars you choose to sync, we read only the event title, start and end time, whether the event lasts all day, the repeat pattern of a recurring event, and the event’s time zone. We do not read or store event descriptions, attendee or guest lists, locations, attachments, organiser details, or any other field. We also store the email address of the account you connected and the identifiers of the calendars you select (see 3.7).

Who in your family can see imported events. Events imported from your connected calendars are added to your family’s Famant calendar with the family-wide visibility setting. This means every member of your family, including any child members, can see them , their title, time, whether they last all day, their repeat pattern, and their time zone. Select only calendars whose events you are content for your whole family to see.

What we write. For eligible events, we create, update and delete the matching event in the calendars you have selected, using only the event fields listed above. Eligible events are:

• shared family events that appear on your Famant calendar, whoever in your family created them, but only where the person who created the event and every person assigned to it can be established as an adult; and
• events you created yourself in Famant that are not shared with the whole family.

Events imported from an external calendar are never written back out to another calendar. We never create or delete an entire calendar.

This also means that if another adult member of your family connects their calendar, shared family events that you create in Famant (where everyone attached to them is an adult) may be written to that member’s Google or iCloud calendar, where they are held in that member’s account with the provider.

Shared calendars. We write only to the calendars you have selected. If one of those is a calendar that somebody else has shared with you, events from Famant will appear in it and will be visible to the other people who can see it, so select only calendars you are content for Famant to write to.

Access credentials. Connecting a calendar gives Famant an access credential: an OAuth token issued by Google, or an app-specific password you generate yourself for Apple iCloud. We store these credentials in encrypted form, use them only to run your calendar sync, and do not share them with anyone.

Who your calendar data is shared with. When you connect a calendar, the relevant provider acts as the recipient of the event details we send to your connected calendar, and as the source of the event details we receive from it:

These providers handle the data held in your account with them under their own terms and privacy policies. Apart from these providers and the members of your family who can see imported events as described above, we do not share your calendar data with anyone, we do not sell it, and we do not use it for advertising.

Disconnecting. You can disconnect a calendar account at any time from Settings → Connected Calendars. When you do, we stop syncing that account and delete our copy of its access credentials. Once you have no calendar accounts connected at all, we also record your connected-calendar consent as withdrawn.

• Google: we additionally revoke Famant’s access to your Google Account directly with Google. You can confirm this at myaccount.google.com/permissions.
• Apple iCloud: Apple provides no way for an application to revoke its own access. We delete our copy of the credential and stop syncing; you should also remove the app-specific password you created for Famant at appleid.apple.com.

After you disconnect an account:

• Imported events from that account are no longer shown in Famant, but we keep them in our database, together with the connected account’s email address and the identifiers of the calendars you had selected, until you delete your Famant account or ask us to erase your data (see section 18). Part of this record is kept so that, if you reconnect the account, events you had deleted do not reappear.
• Events Famant created in your external calendar stay there. Disconnecting removes Famant’s access, not the events Famant wrote while it had access; you can delete them in your calendar.

Deleting your Famant account. If you delete your Famant account, we revoke and delete your calendar credentials and erase the calendar data we hold, including imported events kept from calendar accounts you previously disconnected, as part of the deletion described in section 18. Events that Famant previously created in your own Google or iCloud calendar are left in place: those events live in your account with that provider, under your control, and you can delete them there.

• Databases. Your primary application database and the separate AI-context database are hosted on Google Cloud SQL in the European Union (Finland, europe-north1).
• Servers. Our backend services run on Google Cloud Run in the European Union (Finland).
• Uploaded files. Files you add to the document vault are stored as encrypted blobs in Google Cloud Storage in the European Union (Finland, europe-north1).
• On your device. Your sign-in session, your user profile record, and your family’s file-encryption key are held in your device’s secure credential storage (iOS Keychain / Android Keystore). Separately, the app keeps a local offline cache, a database on your device holding items such as calendar events (including those marked personal, together with their locations), list items, and changes waiting to be synced. That cache is not separately encrypted by the app; it is protected by your device’s built-in encryption (iOS Data Protection / Android file-based encryption), so keeping your device locked and passcode-protected matters.
• In your connected calendars. Events held in a Google Calendar or Apple iCloud account you connect, including events Famant writes there, are stored by that provider under its own terms, not by Famant (see 9.2).

Famant is available worldwide, but our core databases and servers are located in the European Union. This means that if you use Famant from outside the EU/EEA, your personal data is transferred into the EU for processing. In addition, some service providers, notably Google (for the Gemini AI features, OCR, Places, and, if you turn it on, product analytics), our push-notification provider (OneSignal), and our email-delivery provider (Resend), the latter two established in the United States, may process personal data outside the European Economic Area (EEA).

Where personal data is transferred outside the EEA, we rely on a lawful transfer mechanism under the GDPR, such as an adequacy decision or the Standard Contractual Clauses (SCCs), together with appropriate supplementary measures. For users in other regions, we apply the cross-border transfer safeguards required by local law (for example, the UK International Data Transfer Agreement/Addendum for UK users) where applicable. You can ask us for more information about the safeguards in place by emailing hello@famant.com.

Connected calendars. If you connect Google Calendar or Apple iCloud, the event details we send are delivered, at your request, to your own account with that provider, and the event details we read come from it. Those providers store and process the data in your account under their own terms and privacy policies, and may do so outside the EEA.

We use technical and organisational measures appropriate to the risk, including:

• Encryption in transit. All communication between the app and our servers uses HTTPS/TLS.
• Encryption at rest. Our cloud provider encrypts stored data at rest. In addition, files you upload to the document vault are encrypted on your device before upload using AES-256-GCM with a per-family key. A copy of that key is held in your devices’ secure storage (iOS Keychain / Android Keystore), and a copy is also held on our servers, so that members of the same family can open shared vault files and so that access is not lost with a single device. Because we hold both that key and the encrypted files, our systems are technically able to decrypt vault files. Our application does not use the server-held key to decrypt vault files; they are encrypted and decrypted on your family’s devices, but this is a matter of how our software operates, not a technical barrier.
• Password protection. Passwords are stored only as cryptographic hashes (scrypt), never in plain text. Email verification and reset codes are short-lived, hashed, single-use, and rate-limited.
• Calendar credentials. Access credentials for connected calendars (Google OAuth tokens and Apple iCloud app-specific passwords) are stored in encrypted form, used only to run calendar sync, and deleted when you disconnect the account or delete your Famant account.
• Family-data isolation. Strict multi-tenant isolation is enforced at the database level using PostgreSQL Row-Level Security, so one family cannot access another family’s data.
• Access controls. File uploads and downloads use short-lived signed URLs scoped per family and per member; sensitive operations on child-account data are gated by parental-consent authorisation checks.
• Audit logging. Security- and privacy-relevant actions are recorded in append-only audit logs.
• Monitoring. Errors and operational logs are recorded in Google Cloud Logging in the EU and monitored to keep the Service reliable and secure.

We do not currently offer multi-factor authentication (MFA). We recommend you protect your account with a strong, unique password and keep your device secure.

We maintain procedures to detect, investigate, and respond to personal-data breaches. Where a breach is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority within 72 hours where required, and we will inform affected users without undue delay where the breach is likely to result in a high risk to them, in line with GDPR Articles 33 and 34.

Famant is primarily a mobile application and does not rely on advertising cookies or third-party advertising trackers. We use:

• Essential session tokens required to keep you signed in and to operate the Service; and
• Diagnostic/operational data (server-side error and operational logging) to keep the Service reliable and secure (see 3.5 and section 9).

Product analytics (optional). We use Google Analytics for Firebase to understand which parts of the app people use, so that we can improve them.

• It is off until you allow it. Nothing is sent unless you choose to turn analytics on, and you can turn it off again at any time in the app settings.
• Adults only. Only adult family owners and admins can be included. We do not collect analytics events from or about child members.
• What is sent. The screens you open and the actions you take in the app, together with a random identifier created for your app installation. That identifier is not linked to your name, email address, or account, and it is reset when you log out. We do not send your name, email address, messages, or any other content you type.
• Your IP address is not stored. Google uses it only to work out which country an event came from, and then discards it.
• No advertising. Google Signals and ads personalisation are switched off, and we never collect the advertising identifier. We do not use analytics data for advertising, and we do not build advertising profiles from it.
• Kept for 2 months. Google deletes analytics data automatically two months after it is collected.

Apart from this, we do not use third-party product-analytics or behavioural-tracking SDKs (no Amplitude, Mixpanel, PostHog, or Segment). Any cookies used on our marketing website, if applicable, are limited to those strictly necessary to operate the site; any non-essential cookies would be used only with your consent.

Famant is designed for family use. A child may use the Service only as a member of a family account, set up and supervised by a parent or guardian, and only with the required parental consent.

• Adult account holders must be at least the age of digital consent in their country. This varies worldwide, for example, 16 in Germany, 15 in France, 14 in Spain and Italy, and 13 under U.S. COPPA, and we apply the threshold set by local law (defaulting to 16 in the EEA where not otherwise specified).
• Setting up a child member. The family owner/admin (a parent or guardian) creates the child member, provides the required parental/guardian consent, and supervises the child’s use.
• Age verification. We record the child’s date of birth to determine whether they are a minor and to apply the correct age threshold for their country.
• Consent records. We keep records documenting the consent status, method, and lifecycle (granted, verified, revoked, expired).
• Access controls. Sensitive operations on a child’s account data are gated by parental-consent authorisation checks, and visibility rules restrict a child’s personal content to the child and, where applicable, their parent.
• Connected calendars are adults-only. Members under 18 cannot connect an external calendar, a parent or guardian cannot connect one on a child’s behalf, and events created by or assigned to a member under 18, or any event where we cannot establish that everyone attached to it is an adult, are never sent to an external calendar provider (see 9.2).
• No analytics from children. Product analytics is available only to adult family owners and admins; we do not collect analytics events from or about child members (see section 14).
• Parental rights. A parent/guardian can review, manage, or withdraw consent and request deletion of the child’s data (see sections 16–18).
• We do not build advertising or marketing profiles of children.

Because Famant is available worldwide, we process children’s data in line with GDPR Article 8, the U.S. Children’s Online Privacy Protection Act (COPPA) for U.S. children under 13, and other applicable children’s-privacy laws. If you believe a child has provided us personal data without the required parental consent, contact hello@famant.com and we will take appropriate steps to delete it.

Subject to applicable law (including the GDPR), you have the right to:

We will respond to rights requests without undue delay and within one month (extendable by two further months for complex requests, where we will tell you). We do not charge a fee unless your request is manifestly unfounded or excessive. We may need to verify your identity before acting.

Because Famant is available worldwide, you may also have rights under the law of your own country. The protections in this Policy apply to everyone; the paragraphs below describe additional region-specific rights. To exercise any of them, email hello@famant.com.

16.1 European Economic Area and United Kingdom

If you are in the EEA or the UK, you have the GDPR / UK GDPR rights set out in the table above. You may lodge a complaint with a supervisory authority: our lead authority is the Swedish Authority for Privacy Protection (IMY, imy.se), and you may also contact your local authority (find yours via edpb.europa.eu) or, in the UK, the Information Commissioner’s Office (ico.org.uk).

UK representative. Under Article 27 of the UK GDPR, Antutive AB has appointed a representative in the United Kingdom: Prakash Lekshmanan, uk@famant.com. If you are in the United Kingdom, you (and the Information Commissioner’s Office) may contact our UK representative on any matter relating to our processing of your personal data under the UK GDPR. Antutive AB remains the data controller, and contacting the representative does not replace the contact routes in section 20 or affect your rights.

16.2 United States: California and other states

If you are a California resident, the California Consumer Privacy Act, as amended by the CPRA, gives you the right to know/access, delete, and correct your personal information, and to opt out of the “sale” or “sharing” of personal information and of targeted advertising. We do not sell your personal information, and we do not share it for cross-context behavioural advertising or for money , so there is nothing to opt out of, and we do not knowingly sell or share the personal information of minors. We will not discriminate against you for exercising your rights, and you may use an authorised agent. The categories of personal information we collect, our purposes, and the parties we share them with are described in sections 3, 6, and 9. Residents of other U.S. states with comparable privacy laws (for example, Virginia, Colorado, Connecticut, and Texas) have similar rights, which we honour where they apply.

16.3 Brazil (LGPD)

If you are in Brazil, the Lei Geral de Proteção de Dados (LGPD) gives you rights to confirmation and access, correction, anonymisation or deletion, portability, information about sharing, and to withdraw consent. Our person in charge of personal-data processing (encarregado) is Vinayak Panchaman. To exercise these rights, contact hello@famant.com.

16.4 Canada (PIPEDA)

If you are in Canada, you may access and correct your personal information and withdraw consent (subject to legal or contractual limits), and you may complain to the Office of the Privacy Commissioner of Canada.

16.5 Other countries

Wherever you are, we aim to honour the data-protection rights available to you under your local law. If your country grants rights not listed above, contact us at hello@famant.com and we will respond as required by applicable law.

We keep personal data only for as long as necessary for the purposes in this Policy, after which it is deleted or, in the limited cases described below, retained in pseudonymised form:

You can delete your account and personal data from within the app: Settings → Privacy → Delete account/data, or by emailing hello@famant.com.

• Confirmation window. Account deletion is subject to a 30-day confirmation window. A request moves through pending → confirmed → processing → completed and can be cancelled before it is confirmed.
• Scope. You can choose the scope of deletion: your personal data, a member (where a parent deletes a child’s data), or the entire family (owner only).
• What is removed. Once the confirmation window has passed, an automated daily process carries out the erasure, removing your personal data across the application database, the AI-context (embeddings) database, and your uploaded files in object storage. During erasure, the family is “fenced” so no new file-upload links are issued.
• Connected calendars. When your Famant account is deleted, or, where the family owner deletes the entire family, when each member’s data is erased; we revoke and delete the calendar access credentials (for Google, access is also revoked with Google) and erase the calendar data we hold. Events Famant previously created in your own Google or iCloud calendar are not removed: they remain in your account with that provider, under your control. If you connected Apple iCloud, you should also remove the app-specific password you created for Famant at appleid.apple.com.
• Product analytics. If you had analytics switched on, the app stops sending analytics events and resets the random app-installation identifier. Analytics events already sent are deleted by Google on the usual two-month cycle; because they are not linked to your account, we cannot single them out and delete them sooner.
• What remains, and why. Pseudonymised consent records (proof of lawful basis, including parental consent) and security audit logs (kept for about 90 days, with your identity pseudonymised, see section 17) are retained. Data already written to backups persists until the backup window expires, after which it is no longer recoverable.

How shared family data is handled. Content shared within a family workspace belongs to the family context. Deleting your individual account removes your personal data and your authored personal content; family-shared content may remain for the rest of the family unless the family owner deletes the entire family. If you are the family owner, you can delete family-wide data.

Retention exceptions. We may retain limited data where required for legal compliance, to establish or defend legal claims, or for security and fraud prevention , specifically the pseudonymised consent records and (for about 90 days) pseudonymised security audit logs described above.

For step-by-step instructions, see the Delete Account & Data page.

We may update this Policy from time to time. We will post the updated version with a revised “Last updated” date and, where required by law, notify you (for example, in-app). For material changes affecting how we process your personal data, we will give you appropriate notice and, where the law requires, seek your consent. Your continued use of the Service after an update takes effect constitutes acceptance of the revised Policy, except where additional consent is required.

For any privacy question, or to exercise your rights, contact us:

• Email (all privacy and support enquiries): hello@famant.com
• Data controller: Antutive AB, c/o Vinayak Panchaman, Övralidsgatan 11, LGH 1103, 422 47 Hisings Backa, Sweden, Swedish company registration number (organisationsnummer) 559576-7228
• UK representative (UK GDPR Article 27): Prakash Lekshmanan, uk@famant.com, for data-protection matters concerning individuals in the United Kingdom. Antutive AB remains the data controller.
• Designated privacy contact (person in charge of privacy matters, including under Brazil’s LGPD and Singapore’s PDPA): Vinayak Panchaman, hello@famant.com. We have not appointed a formal Data Protection Officer under GDPR Article 37.

You also have the right to lodge a complaint with a data protection supervisory authority. As we are established in Sweden, our lead authority is the Swedish Authority for Privacy Protection (IMY, imy.se). EEA users may also complain to their local authority (identify yours via the European Data Protection Board, edpb.europa.eu), UK users may complain to the Information Commissioner’s Office (ico.org.uk), and users elsewhere may contact their national data-protection regulator. We would, however, appreciate the chance to address your concerns first.

You can also contact our support team.