Skip to main content
Case Familiale

Privacy

Privacy policy

Case Familiale keeps a family’s memory, bonds and life. This information is intimate: this policy explains plainly which personal information we process, why, with whom, for how long, and how you stay in control.

Version
2026-11-21.1
In force since

1. Who is responsible for your information

Case Familiale is operated by KTMA Solutions Inc., a business corporation established in Quebec, Canada (IT services) (full details in the legal notice), which acts as the controller for the processing described in this policy. For any question or request: contact@ktmasolutions.com.

To exercise your rights or contact the person in charge of the protection of personal information of KTMA Solutions Inc., use the following address: contact@ktmasolutions.com. Representative in the European Union (GDPR, Art. 27): designation in progress; their contact details will be published here. Where the GDPR requires the designation of a data protection officer, their contact details are provided in accordance with that regulation.

The personal information governance policy of KTMA Solutions Inc., published with the other legal information on the site (“Personal information governance policy” page), describes roles and responsibilities, the retention and destruction of information, privacy impact assessments, and the handling of confidentiality incidents, requests and complaints.

Within each family, authorised members (administrators, council, successor) make decisions about family information: validating a link, correcting a record, publishing a memory. They act within the family rules and the tools we give them; KTMA Solutions Inc. remains the contact for exercising your rights.

2. The information we process

We seek to limit collection to what is necessary for the purposes described below. Depending on your use:

  • Account: email address (verified by a code); a phone number may be used once phone verification becomes available; password stored as an Argon2id hash (never in clear); language, time zone, notification preferences; two-step verification secret (encrypted) and recovery codes (stored as hashes).
  • Identity and profile: given names, family name, name used in everyday life, sex at birth, dates and places of birth or death, city and country of residence, bio, profile photo.
  • Family links: parentage, unions, adoptions, paternal or maternal side, join requests and supporting documents submitted for validation.
  • Content: messages, memories, photos, documents, audio recordings (including language contributions), cultural knowledge, events, shared resources.
  • Governance: requests, votes, decisions, challenges, delegated roles and rights, sealed designation of a successor (family succession feature), administration handover offers (identities of the people concerned, responses, dates, decisions and history), and optional pre-designation of an administration successor.
  • Exceptional deletion review (when requested by a person who no longer has access to their email or phone): results of the verifications, type of identity document presented during a video call and date, account of the administrator whose confirmation we request and their answer, log of notices, any objection and decisions (never a copy of an identity document, any authentication code or complete card details); see section 13.
  • Subscription and transactions: the family’s regime and plan, interval, trial and due dates, amounts, currencies, payment status, invoices and receipts, contributions, refunds; country, postal code and time zone used to calculate taxes and dates; proof of your payment authorisation (text and version accepted, maximum amount, date, truncated IP address and browser fingerprint); billing notices sent; for a card, the identifiers assigned by Stripe, the brand, the last four digits and the expiry date; for a refund by Mobile Money, a fingerprint of the wallet number, a masked label and the operator. Case Familiale neither receives nor stores your full card number or its security code.
  • Proof of use of a paid feature: for each paid period of the subscription regime, the date and time of the first write operation performed in the family space during that period, the type of the operation (from a catalogue of operation types of the application), the account that performed it and the period concerned; neither the content of the operation nor its parameters are recorded.
  • Dispute file (chargeback): Stripe identifiers of the dispute, the charge and the payment, reason, amount, status, response deadline, balance movements relating to the dispute (withdrawal, reinstatement, fees), decisions, qualifications and notes of our team, and the items of the evidence file described in section 8. These items contain neither the content of the family space nor your IP address.
  • Reports and moderation: for each report, the account of its author, the date, the target (content, profile or person reported), the reason chosen, any free-text comment, the version of the reported content (as a cryptographic fingerprint only, never the content in clear), the status of the report and the handling decision (date and person who handled it); the author’s identity is visible to the authorised people who handle the report (family administrators and moderators; the Case Familiale team when the report is addressed or forwarded to it). The free-text comment may mention other people: include only what is necessary.
  • Location (mobile app): when you choose to add a place on the map, you may allow access to your device’s location, in the foreground only. We do not track your location continuously; an exact position is only saved after you confirm it, and its visibility remains subject to your family’s visibility rules.
  • Notifications (mobile app): if you enable push notifications (by accepting your device’s system permission request), your device’s notification token (a technical identifier assigned by Google on Android or by Apple on iOS), the platform, language, app version and system version; this information is processed only if you enable notifications. The token is tied to your sign-in session: the app asks our servers to unregister your device when you sign out or when it detects that notifications have been denied or disabled, and our servers delete the token when that request is received, when the session is revoked (for example after signing out other devices, a password reset, a suspension) or when the account is deleted; an expired session is no longer used for sending and its token is deleted when session records are purged, normally within 30 days after expiry; a token that Google or Apple reports as invalid is deleted; if that request does not reach our servers, the token may remain registered until another deletion mechanism described above applies, including session revocation or purging after expiry.
  • Content of notifications (mobile app): When you enable Case Familiale notifications, our servers send Google (Android) or Apple (iOS) your device’s push notification token, a generic title and message based on the notification category, and technical information needed for delivery, identification, grouping and unread notification counts. This technical information may qualify as personal data. Based on the controls implemented in our notification services, the information sent to Google or Apple does not include message text, people’s names, event locations, amounts or health-related details. Some notifications may indicate the number of new messages. When a notification is received, a component of the app installed on your device may request a detailed preview directly from our servers. Depending on the category, this may include the sender’s first name, conversation name, a message excerpt or attachment type, or an event’s title, date, time and location, or a vote’s title and deadline. Before providing a detailed preview, our servers check the recipient’s access rights. If access is no longer permitted or retrieval fails, the notification retains its generic content. Certain categories, including security, rights and roles, billing, account procedures, departures, disputes, claims and contributions, remain generic. Categories that have not been expressly approved for detailed previews also remain generic.
  • Display of notifications (mobile app): Detailed previews may be displayed by your device’s operating system, including on the lock screen, depending on its notification and privacy settings. Detailed previews are on by default; you can turn them off at any time, without turning off notifications, with the app’s “Show notification details” setting (Settings, Notifications): notifications received on that device then show only the generic text. Detailed previews are never displayed for an account whose recorded date of birth indicates an age under 18. Anyone who can see your screen, access your unlocked device or use a shared device may see notification details without opening Case Familiale. To reduce this risk, you can hide previews or sensitive notification content in your device settings, or disable the app’s notifications. Previously displayed notifications may remain visible in your device’s notification centre, history or other system features after access rights change in Case Familiale. Revoking access prevents new retrievals through our API but does not guarantee that previously displayed details will be erased. Depending on your device’s features and settings, connected accessories such as smartwatches, as well as notification summaries, history or synchronization features, may also display, process or retain these details. Such processing may depend on third-party providers and their settings.
  • Preview token (mobile app): The app uses a technical token designed to restrict preview retrieval to notifications associated with the relevant account and session. This token is stored in a private area of the app on your device, using the protections available on the operating system. It is revoked on logout, session revocation or renewal of the push notification token. The app also provides for its local removal when you log out or disable notifications. A preview can be retrieved from our servers for up to 72 hours after the notification, subject to access rights. This limit does not determine how long the underlying message or event is retained, or how long a previously displayed notification remains on your device.
  • Help assistant and support requests: the questions you ask the help assistant and its answers (only if you are signed in); if you ask to be called back or to schedule a call: how to reach you (number or address), a confirmation email (without an account), your first name if you give it, the topic chosen from a list, the chosen time or slot, your device time zone, the page you came from and, if you are signed in, the family shown; the text of your question only if you tick the box provided; the version of the information notice displayed and, where applicable, of your agreement.
  • Pricing zone: country of the billing address, country of the connection (deduced from the IP address, which is not retained), card-issuing country (supplied by Stripe), zone and country retained, version of the geolocation database used and cryptographic fingerprint of the decision; in the event of a contestation: the country of residence you state, your reason, the decision of our finance team and its reason (see section 8).
  • Technical data: conversation-display signal (when you view a conversation in the foreground of the app, our server temporarily maintains a technical signal linking your session, connection and conversation, to avoid sending you a notification while you are viewing it; this signal is periodically renewed while the conversation remains displayed, and each activity indication expires after 30 seconds without renewal; the app also requests its removal when you leave the conversation or sign out, and if that request fails automatic expiration limits how long the signal is used; the associated technical record, kept within our infrastructure, may briefly remain until its key expires, configured at 60 seconds after its last renewal; this signal is not transmitted to any third party, including Google and Apple); sessions and devices (browser or app type, random device identifier), IP address stored as a fingerprint, security and audit logs, and the record of your consents and of your acceptance of the legal texts (with their version).
  • Integrity check (Android app): at sign-up, sign-in, when a code is requested, on forgotten password, when a visitor contact message is sent and when the visitor assistant is used, the app asks Google Play for an integrity verdict (signals used to assess app authenticity, recognition by Google Play and device integrity, depending on the available checks) in the form of an encrypted token, which our servers submit to the Google Play Integrity API for decryption. We do not keep this token, only aggregate counters of the results. When the integrity check is required, the operation requested from the Android app is refused if the token is missing, invalid or reused, if the result does not meet the applicable security criteria, or if the verification service is unavailable. When the check is performed for observation purposes only, its result is counted without causing a refusal on that basis. If you experience difficulties, you may contact us at contact@ktmasolutions.com. Google processes information about your device and the app on this occasion, according to its own documentation (“Play Integrity API data disclosure”).
  • Referral: the family’s referral code; the link between the referring family and the referred family (technical identifiers of both families and of the administrator account that entered the code, date of attachment, state of the link); the state and dates of each family’s complimentary months (pending, held, granted, applied, cancelled, revoked, and the reason) and their value (amount and currency); the references of the payment that triggered the complimentary month; the opaque card fingerprint supplied by Stripe (never the card number), compared between the two families to prevent fraud; the history of decisions (automatic or by our finance team, with the reason); the proof of the calculation that allowed application. No name, email or other information about members of the referred family is shown to the referring family: it sees anonymous statuses only. These statuses describe the technical tracking of rewards; no cancellation or revocation allows an already applied complimentary month to be clawed back.

Information about you may also be provided by another family member, for example when creating a record, a family link or a memory (including where the person has no account or is deceased). Where the person concerned is living and the law requires us to inform them directly of this indirect collection, we do so in the manner and within the time limits that apply, subject to the exceptions provided by law.

Case Familiale does not seek to systematically collect special categories of personal data protected by law, including health information, religious or political beliefs, or information concerning sex life or sexual orientation. However, freely submitted content (stories, documents, recordings, family information) may reveal such data, including data concerning another person, as well as origins, languages or regions. Where the GDPR applies, processing falling within Article 9(1) is carried out only where a lawful basis under Article 6 and an applicable condition under Article 9(2) have been established; explicit consent is obtained where it is the applicable ground and can lawfully be given; if no applicable legal condition exists, the relevant processing must not take place. Visibility settings restrict access to information but do not replace the legal requirements governing its processing.

3. Profile photo and face-presence check

When a profile photo is provided or required in the applicable journey (creating or activating an account), it helps your family recognise you and limits fake profiles.

To check that the photo shows a person, we automatically check for the presence of a human face:

  • the check runs on our own servers, with local detection software; the photo is not sent to any third-party service;
  • it only checks that a face is present (and that there are not several of similar size): it is not facial recognition; no comparison with other photos is made;
  • no biometric template or facial feature point is kept: computations stay in memory for the duration of the check and are then erased;
  • only the result (accepted or refused, and the reason for refusal) is logged, with no image data;
  • a refused photo is deleted immediately.

Before any processing, each photo is scanned by an antivirus and its metadata (including GPS position) is removed. The photo is then visible according to your family’s visibility rules. You can replace it at any time; deceased people and elders without an account keep the family emblem.

NOTE: Legal bases: performance of the contract (recognition within the family) and legitimate interest (preventing fake profiles). The check only detects that a face is present; it creates no template used to authenticate or identify a person. The exact legal characterisation of this processing under the rules specific to biometric data depends on the applicable law.

4. Why we process it

The legal basis depends on the processing and on the person concerned. For the account holder:

  • Provide the service (create the account, sign you in, maintain the tree, share content, run governance) — performance of the contract.
  • Send you, if you choose to enable them, push notifications about activity relating to your account and families (new messages, events, governance decisions and security alerts) — for optional notifications, your consent, which you may refuse or withdraw at any time by disabling notifications in your device settings (or in the app), without losing access to other features; the purposes, the technical information used and its transmission to Google or Apple depending on your device are described in this policy, which is accessible from the app. Category preferences can be changed in the app, but the “Security” category cannot be disabled separately there; disabling notifications at the system level prevents them from being sent. Sending security alerts by other means (for example email) relies on the security necessary to operate the service and does not depend on enabling push notifications. When notifications are enabled, displaying their detailed content on your device (detailed previews, section 2) is based on our legitimate interest in clearly informing you of your family’s activity, as a messaging service does; we have balanced it against your interests and rights (sensitive categories always generic, no previews for an account whose date of birth indicates an age under 18, content not included in the payloads sent to Google or Apple), and you can object at any time, without turning off notifications, with the “Show notification details” setting.
  • Secure accounts and the platform (passwords, codes, lockout, sign-in alerts, antivirus, logs, integrity check of the Android app against fraud and automated abuse) — security necessary for the operation of the service and compliance with applicable legal obligations; where the GDPR applies, legitimate interests in preventing fraud and abuse, subject to applicable legal requirements.
  • Verify family links through authorised relatives — performance of the contract. Supporting documents are used only to process the join request and are accessible only to the people authorised to validate it.
  • Manage the family’s subscription or plan, the trial, payments, billing notices, contributions and refunds — performance of the contract and accounting and tax obligations.
  • Keep proof of your payment authorisation and of the notices sent, handle payment disputes and limit the free trial to one per family and one per paying administrator over 12 months — legitimate interest and the establishment, exercise or defence of legal claims.
  • Establish whether a paid feature has been used during a paid period, in order to apply the 14-day commercial refund guarantee in a verifiable way, and keep that proof — performance of the contract and legitimate interest (applying the guarantee fairly and verifiably), establishment, exercise or defence of legal claims, to the extent permitted by applicable law and subject to the conditions of necessity and consent it provides. This record is used only for the guarantee, for the proportionate calculation of a statutory refund where the law so provides, and for the dispute file; it is never set against your statutory rights of withdrawal, cancellation, termination or refund.
  • Handle a chargeback (bank dispute): re-read the dispute at Stripe, adjust access to the family space, build and submit the evidence file, account for the outcome and keep the necessary items — performance of the contract, legitimate interest and establishment, exercise or defence of legal claims, accounting obligations.
  • Receive and handle reports of content or behaviour, protect members and enforce the terms of use (hiding, removal from display, suspension) — legitimate interest (members’ safety and compliance with community rules), performance of the contract and legal obligations where they apply.
  • Inform you of important events (validations, votes, security) — performance of the contract.
  • Respond to your requests and to authorities where the law requires — legal obligations.

Where personal data concerns someone other than the account holder, including a parent, child, spouse, living person without an account or deceased person, we separately determine the lawful basis for processing that person’s data. A contract concluded with another family member does not, by itself, establish a contractual legal basis for that individual. Depending on the processing activity and applicable law, the basis may include valid consent, a legitimate interest established after balancing the individual’s rights and freedoms, or a legal obligation; where special categories of personal data are involved, the additional applicable conditions are also assessed.

Your general acceptance of this text at sign-up or when a new version is published does not replace the specific consents the law requires for certain processing: these are requested separately (Settings › Privacy) and can be withdrawn at any time. For the purposes offered on that screen (appearing in the family tree, publishing photos, audio and cultural recordings, being contacted by members), withdrawing a consent stops the processing concerned for the future (applied by the server); where processing relies on legitimate interests, you can separately exercise your right to object; withdrawal does not affect lawful processing carried out before it; it does not erase information already published or kept on another legal basis (see sections 11 and 13).

Where the GDPR applies, processing necessary for the contract relies on Article 6(1)(b); processing necessary to comply with a legal obligation, on point (c); processing justified by a legitimate interest, on point (f), after weighing the interests and rights of the people concerned: for preventing trial abuse, security, proof of authorisations and the defence of rights, those interests are respectively preventing misuse of the service, system security, proof of contractual commitments and the handling of disputes. Where processing relies on consent, the applicable basis is Article 6(1)(a), without prejudice to the additional conditions required for special categories of data.

We do not sell or rent your data, do not run targeted advertising and do not train any artificial-intelligence model on your content.

Help assistant. The help assistant is a search tool over the Case Familiale help, run on our servers: it does not generate text, does not use any generative artificial-intelligence model and does not send your question to any external service. Search combines text retrieval methods with a multilingual encoding model run on our servers; this model helps retrieve relevant help articles and does not generate new answers. The assistant only suggests the screens and help articles that your rights give you access to. If you are signed in, your exchanges are kept encrypted so that you can find them again (section 11); a visitor’s exchanges are not kept. The text of questions is not written to our technical logs. A conversational assistant based on a generative artificial-intelligence model remains switched off; before it is enabled, this policy will be updated to describe the data involved and any providers.

Human support requests (“Call me back”, “Schedule a call”). The information you provide is used to handle your request and arrange the call, never for marketing; after closure, some information is erased or undergoes a process intended to anonymise it so that we can produce support activity statistics and plan our support team’s capacity (section 11). These statistics are never used to build individual profiles. Without an account, the request is passed on to the team only after you confirm your email address through a single-use link (30 minutes). The text of your question is passed on to the team only if you agree by ticking the box provided; you can withdraw this agreement, or cancel the request, at any time from the follow-up link received by email. Only authorised members of the support team can access it, and every access is logged. Our email service, hosted in Canada, receives only the information necessary to deliver confirmation and follow-up messages. To request a call, a way to reach you, the topic and, for an appointment, the chosen slot are required (and, without an account, an email address to confirm the request); your first name, the preferred time and the text of your question are optional.

Legal bases where the GDPR applies: for account holders, processing necessary to provide support as part of the service is based on performance of the contract (Article 6(1)(b)). For visitors, processing necessary to respond to a pre-contractual request is based on the same legal basis where its conditions are met; other visitor requests are based on our legitimate interest in responding to support enquiries (Article 6(1)(f)), subject to your rights and freedoms. The optional sharing of the text of your question with the support team is based on your consent (Article 6(1)(a)), which you may withdraw at any time without affecting the lawfulness of processing already carried out. Producing support activity statistics from information undergoing the anonymisation process, for as long as its anonymisation has not been demonstrated, is based on our legitimate interest in planning support capacity (Article 6(1)(f)). Operations necessary for service security and for the technical accountability of erasures (erasure register, section 11) are based on our legitimate interest in securing the service and ensuring that your erasures are effective (Article 6(1)(f)). Where processing is based on our legitimate interests, you may object on grounds relating to your particular situation under Article 21 GDPR, subject to compelling legitimate grounds or other applicable exceptions, by writing to contact@ktmasolutions.com; for a support request, you can also cancel it from the follow-up link.

5. Minors and legal representatives

A minor may appear in their family tree, represented by an adult. The rules for opening and using an account as a minor depend on the country of residence: in Quebec, collecting information directly from a child under 14 in principle requires the consent of the holder of parental authority or the guardian; in the European Union, where processing relies on consent in connection with an information-society service offered directly to a child, the age at which the child may consent on their own depends on the Member State, within the limits set by Article 8 GDPR; for persons subject to Cameroonian law, the consent of a person under 18 must be supported by their parents or legal representative. Case Familiale applies age 18 as the age of majority for its adult-only functions. To create and use an account you must be at least 16: each account holder states this at sign-up (or at the first sign-in for an account created earlier); this statement is recorded with its date, without identity verification. A younger person may appear in the tree, represented by an adult, without an account.

A minor’s account must only be opened and used with the agreement and, where required by law, under the responsibility of their legal representative. The representative may exercise or assist with the minor’s rights as provided by applicable law. Within the application, an adult with a verified parentage link or an active guardianship link is recognised as a representative for the application’s purposes; this functional recognition does not replace legal verification of parental authority where required by law.

  • a minor’s profile is never public and only shows the family what is necessary;
  • for certain governance decisions (removing a false record, paternity…), authorised members only see a minimal card: name, photo and family link;
  • the legal representative may at any time request correction or deletion of the minor’s information.

6. Family data, deceased people and visibility

Your profile is private by default. It becomes visible to your family once your link has been validated by authorised relatives, paternal and maternal sides separately. You then choose, field by field, what you show. Nothing is indexed by search engines.

Information about other people (parents, children, spouses, deceased people) must be accurate and shared respectfully; a living person may ask for what concerns them to be corrected or hidden.

Records and memorials of deceased people are processed in accordance with the rules that apply to information about the deceased: directions left by the person, rights of relatives or successors, legal obligations. Where the applicable law requires processing to stop at death absent a legal ground to keep it, we apply that rule. Depending on the applicable law, certain relatives may exercise rights over this information (in Quebec, for example, a spouse or close relative may in some cases request information that may help them in their grieving process, unless the deceased refused in writing).

7. Family governance

Votes, decisions and challenges are recorded in an append-only, hash-chained audit log designed to make any alteration detectable, which authorised people can consult so everyone can check that decisions were regular.

The secret designation of a successor is encrypted: only the current successor can see or change it. Neither members, nor the council, nor administrators, nor platform staff can access it in the application; it is revealed only upon the successor’s validated death, then submitted to the family for confirmation.

8. Payments

The payment methods actually available depend on your country and are shown to you before any payment. Subscription payments are processed as follows:

  • Card, Apple Pay or Google Pay: by Stripe, on its secure page. Your card details are entered with Stripe and do not pass through our servers. To save the card and bill the subscription, we send Stripe your email address, your given names and surname, your country, your postal code, your language and opaque technical identifiers of the family and the account; we receive from Stripe the identifiers of the customer, payment method, invoices and payments, the card brand, last four digits, expiry date and issuing country, as well as amounts, taxes and statuses.
  • Mobile Money: by CinetPay, on its secure page. We send CinetPay your email address, your telephone number and the operator where you provide them, as well as the amount, currency and a payment reference (no name: generic values are sent in its place); your wallet details are entered with CinetPay or your operator, and we receive the payment reference, amount, currency and status; a payment is treated as confirmed only after its status has been checked with CinetPay. To refund you by Mobile Money, we send CinetPay the number of the wallet to be credited; we keep only a fingerprint of it and a masked label.

Stripe and CinetPay also process this information under their own legal obligations, in particular for fraud prevention and anti-money-laundering purposes, and may send you payment or refund receipts directly. Payments between members (family marketplace) are not currently available.

Pricing zone and automated price decision. The price of a new contract (start of a trial or resubscription) depends on the pricing zone, which our systems determine automatically, without human intervention at the time of calculation, from: (a) the country of the billing address you enter; (b) the country of your connection, deduced from your IP address; (c) for a card payment, the country that issued the card, which we receive from Stripe after the card is registered; (d) where applicable, the decision of our finance team following a contestation. Where these indications fall under grids of different levels, the highest grid applies; the CFA franc rate is applied only if all the available indications point to a country of the CEMAC or UEMOA zones. Purposes: determining the regional pricing grid applicable to a new contract based on the indications described above, and preventing misuse of regional pricing. The zone retained may differ from your country of habitual residence and may result in a higher price than that of the address you entered. Any country outside the CEMAC and UEMOA zones falls within the higher level; where several indications fall within the same level, the zone is determined by priority from the billing-address country, then the card-issuing country, then the connection country, subject to an applicable decision by our finance team. It concerns only the conclusion of a new contract: a concluded contract keeps the zone and price accepted.

Information and rights. The zone retained and the indications it relies on (address, connection, card, decision of our finance team) are displayed on the quote screen, before you agree and before anything is charged. You may request, by writing to contact@ktmasolutions.com, the personal information used, the reasons and the principal factors and parameters of the decision, and the correction of inaccurate information. You may also submit your observations and contest the zone from the quote screen, stating your country of habitual residence and a reason: the request is reviewed by a person on our finance team, other than you, who has the power to change the zone retained and gives a reasoned decision; if the request is accepted, the grid of the country established applies to your next quotes for 12 months, without retroactive effect. You may continue at the price applied during the review. Where the GDPR applies and the decision falls within Article 22, we rely on the exception for necessity to enter into a contract only where the conditions of that Article are met. You may request human intervention, express your point of view and contest the decision, through the procedures described above. Where Cameroonian law applies, you also have the right to object to a decision based solely on automated processing, subject to the conditions laid down by that law, as well as the rights to human intervention, to express your views and to challenge the decision; you may exercise these rights by writing to contact@ktmasolutions.com.

IP address and geolocation database. For this determination, the IP address of your connection is read only to derive a country, at the time of calculation, and is then neither stored in the decision record nor logged by this function; only the country code is kept. Keeping a fingerprint of the IP address for session security (section 2) remains governed by its own rules. The country is derived from a geolocation database (DB-IP “IP to Country Lite”, CC BY 4.0 licence; “IP Geolocation by DB-IP”) which is a file hosted on our servers and consulted offline: no IP address or other information is sent to DB-IP or to any other third party for this operation, and DB-IP receives no information about you. This database is credited on the Credits page and on the pricing and quote screens.

Chargeback (bank dispute). When you or your financial institution dispute a card payment, Stripe sends us the information about the dispute: identifiers of the dispute, the charge and the payment, reason, amount, status, response deadline, balance movements (withdrawal, reinstatement, fees). We re-read this information at Stripe using read-only access to disputes.

Access decisions and human intervention. When a formal chargeback is reported, our system may automatically apply a temporary restriction on access to the family space, based on the dispute status, the period concerned and the payments validly allocated to that period, in accordance with the terms of use (section 15). This restriction may affect family members other than the payer, without attributing any fault to them. This temporary restriction prevents write operations within the family space while it remains in effect, including adding or modifying content, subject to the limits and exceptions set out in the Terms of Use; it does not delete any data, does not by itself terminate the contract, and does not imply wrongdoing by other family members.

Where this measure constitutes a decision based solely on automated processing of personal information, each affected individual is informed in accordance with applicable law, no later than when the decision is communicated to them. They may write to contact@ktmasolutions.com to request the personal information used, the reasons for the decision and its main factors and parameters, request correction of inaccurate information, submit observations and obtain a genuine review by an authorised person empowered to change or lift the restriction. The continued need for the restriction is reassessed when relevant new information becomes available, including the resolution of the dispute, correction of a payment or a reasoned request from an affected individual; a restriction that is no longer justified is lifted without undue delay.

Final termination of the contract following a lost chargeback is not decided solely through automated processing: it requires an individual assessment and a reasoned human decision under the terms of use.

Where the GDPR applies, any automated measure falling within Article 22 is implemented only if an applicable legal exception has been established and the required safeguards are met; otherwise, meaningful human involvement precedes the relevant decision, in accordance with applicable law. Functions necessary for exercising statutory rights and exporting data remain available as required by applicable law.

Evidence file. To answer the dispute, an authorised member of our team prepares, reviews and then manually submits in Stripe’s dashboard a file assembled, according to the nature and reason for the dispute, from the following categories and limited to necessary and relevant items: the versions of the texts you accepted (date, fingerprint); the recorded payment authorisation (text, conditions, amount, date); the invoice (number, amount, link) and the payment references; the period concerned; the date, the type of operation and the author account of the first use of a paid feature, without the content; the list of billing emails sent (type, date, transmission identifier), without their content; and the refunds. Evidence of paid-feature use is transmitted only where its relevance to the particular dispute can be demonstrated. This file is intended for Stripe and, through it, for the financial institution that issued the card and the card network concerned; these recipients may process it outside Quebec (section 10). It contains no family content and no IP address.

Referral. When a family enters a referral code, we process the information necessary to establish the referral relationship, verify eligibility, prevent abuse and determine whether a complimentary month may be granted or applied.

Certain decisions are made solely through automated processing. They take into account, among other factors, payment and subscription status, expiry of the commercial guarantee, refunds and disputes, fees, taxes and provisions, programme limits, incompatibility with the “Founding Families” offer, and antifraud checks. Certain cases presenting a risk are instead held for review by the finance team, including where the same card is detected, no card fingerprint is available, or a payment requires verification.

You may contact contact@ktmasolutions.com to request the personal information used in a decision concerning you, obtain its reasons and the main factors and parameters considered, request correction of inaccurate information, submit observations to a person authorized to review the decision, and request such review.

We do not send referral invitations or collect the email addresses of people invited by users. Users share their referral codes themselves.

When a complimentary month is applied, a service email confirming the transaction is sent to the payer in the language of the contract, without additional promotional content. The programme does not provide for commercial invitation emails sent by the platform.

For these checks, we use technical card identifiers made available by Stripe in connection with payment processing. We do not collect complete card numbers for this comparison.

9. Who can access your information

Depending on the features you use, your information may be accessible to or shared with:

  • members of your family, according to your visibility settings and their rights;
  • our cloud hosting, storage, backup, security, email delivery and technical support providers, as well as payment service providers. Where they act on our behalf, these providers process personal data within the scope of their services and applicable contractual and legal obligations; certain providers, particularly payment service providers, may also process personal data for their own legally permitted purposes, according to their respective legal roles and obligations;
  • OpenFreeMap, when your browser or the app displays a map, or downloads an offline map pack that you requested: this service receives, among other things, your connection IP address and the map tiles requested, which show the geographic area viewed (including, depending on the precision chosen by your family, the area of a family place). Case Familiale does not directly transmit your account identifier or the name of a place to it; it nevertheless receives technical information (IP address, requested tiles) that may reveal a geographic area viewed, and its processing is also subject to the terms and privacy policy applicable to that service;
  • Google (Firebase Cloud Messaging, on Android) or Apple (Apple’s push notification service, on iOS), depending on your device, when you enable notifications in the mobile app: our servers send them directly the device token, the generic title and text of the notification (which may state the number of new messages in a conversation, with no name or content), its category and opaque technical identifiers, the number of unread notifications, a non-reversible grouping identifier and the technical parameters needed for delivery (including priority and validity period), so that they relay the notification to your device; these providers may know the destination device, notification category and time of sending or processing, without this necessarily establishing receipt or reading. Google and Apple also process, for registering the device and for that delivery, the technical identifiers of the device or installation that their service needs, and may keep certain information for their own purposes in accordance with their terms; deleting a token on our side does not immediately erase information held by Google or Apple, which apply their own retention periods. The notification payloads sent by our servers to Google (Firebase Cloud Messaging) or Apple (APNs) do not include message text or people’s names. They contain technical information required to deliver notifications. Detailed previews are retrieved directly from our servers by the app installed on your device and are not included in the payloads sent to Google or Apple. Subsequent processing by your device, its operating system or connected accessories depends on their respective features and settings (section 2);
  • Google (Google Play Integrity API, on Android), when you sign up, sign in, request a code or initiate a password reset, write to the visitor contact or use the visitor assistant from the app: Google receives the integrity verdict request and processes information about the device and the app, including to decrypt the verdict at the request of our servers, according to its own terms; Google provides this security verification service. The respective data protection responsibilities of Google and KTMA Solutions Inc. depend on the processing activities concerned and the applicable contractual terms; Google may also process certain data in accordance with its own terms;
  • your device’s map applications, or the Google Maps or OpenStreetMap websites, when you ask for directions to a place: the chosen place is sent to them at your request, and they act under their own terms;
  • payment providers: Stripe (card, Apple Pay, Google Pay) and CinetPay (Mobile Money), for the information described in section 8, when you use these methods, and, for Stripe, to verify a payment in the exceptional deletion review (section 13) and, for a chargeback, Stripe and, through it, the financial institution that issued the card and the card network concerned, for the evidence file described in section 8;
  • the Case Familiale team, on a specific need (support, security, handling a report), with traced access;
  • authorities, only on a request based on law.

Where a provider acts as a processor for KTMA Solutions Inc., its processing is governed by the contractual and security safeguards required by applicable law. Some third-party services may act under a different legal role, as described in their applicable terms or policies. No SMS delivery service is currently used.

10. Hosting and international transfers

Hosting and location of information. Case Familiale’s applications, application databases and backups are hosted in Canada. Files uploaded by users, including photos, documents, audio files, supporting documents and export files, are stored in the European Union, in France. These storage locations do not mean that all processing takes place exclusively in these countries: some payment, notification or mapping providers process the information needed for their services from other countries, as described in this policy.

Transfers outside Quebec and international transfers. Where personal information is entrusted to a service provider located outside Quebec, KTMA Solutions Inc. must implement the measures required by Quebec privacy legislation, including a prior privacy impact assessment where required and contractual safeguards designed to ensure adequate protection of the information.

Where the European Union General Data Protection Regulation applies, transfers of personal information from the European Economic Area to Canada are carried out in accordance with Chapter V of the GDPR. Where the European Commission adequacy decision applicable to Canadian commercial organisations covers the relevant transfer, the transfer relies on that decision. Where that decision does not cover a transfer, KTMA Solutions Inc. relies on another transfer mechanism provided for in Chapter V of the GDPR, notably standard contractual clauses, together with the required appropriate safeguards. Transfers taking place within the European Economic Area are not transfers to a third country within the meaning of the GDPR.

Payment providers. Depending on the method used, personal information is sent to Stripe or CinetPay to manage payments and refunds (section 8). These providers may process this information outside Quebec, in particular in the countries where their facilities, the entities involved or the financial operators concerned are located. Before any communication of personal information to these providers, KTMA Solutions Inc. must carry out the privacy impact assessment required by Quebec legislation, ensure that the information will receive adequate protection and enter into the written agreement required by law; where a transfer falls under the GDPR, it must also comply with the applicable mechanism of its Chapter V. As part of the exceptional deletion review (section 13), our team may also consult at Stripe the data of a payment already made, using technical identifiers we have already recorded; this consultation is subject to the same prior privacy impact assessment. The same applies to the communication of the dispute file described in section 8 to Stripe, the issuing financial institution and the card network, which may process it outside Quebec and outside Canada.

Geolocation of the connection. To determine the pricing zone (section 8), no IP address is sent outside our servers: the geolocation database is consulted offline.

Notification, mapping and integrity-check services. To provide notifications, maps and the integrity check, certain technical information may be processed outside Quebec, including outside Canada, by Google (Firebase Cloud Messaging and Google Play Integrity), Apple (push notification service) and OpenFreeMap, for the purposes described in section 9, without excluding processing that these providers may carry out for their own purposes in accordance with their terms and applicable laws. For push notifications, the information given to Google and Apple is that described in section 9 (including device token, generic content, opaque technical identifiers, delivery parameters) and does not include the content of your messages, any name or any health information. KTMA Solutions Inc. is required to assess in advance the privacy impact of these communications outside Quebec and to ensure adequate protection of the information, including through the contractual safeguards required by law. Where the GDPR applies, transfers are also subject to the requirements of its Chapter V.

Additional information regarding categories of service providers, processing locations and safeguards applicable to international transfers may be obtained from the person responsible for the protection of personal information, by writing to contact@ktmasolutions.com.

11. Retention periods

  • Account and profile: as long as the account is active. When you delete your account, access is disabled immediately and several items directly attached to the account are deleted or dissociated (email, phone, password, two-step verification, devices, preferences). Your family record may be kept in pseudonymised form (“Removed member”) where needed to preserve verified family links; only the year of birth is then kept. Your private content becomes inaccessible immediately and its content is erased from our active systems; deletion of the corresponding files (and their variants) is triggered without delay. If a storage incident prevents that deletion, it is retried automatically: our operational objective is to complete it within 30 days of the account deletion; a deletion pending for more than 24 hours triggers a technical alert and, if the objective is exceeded, the attempts and the follow-up of the incident continue until it is resolved. This technical objective does not replace the legal time limits for responding to your requests (backup copies follow the separate cycle described below).
  • Deferred deletion requests and administration handovers: a deferred deletion request is kept until it is executed or cancelled. Once the request is closed, we keep a minimal record (type of request, status, dates, decision, authorized person who made it, technical reference) for 3 years so that we can demonstrate how it was handled in the event of a complaint or legal remedy, unless a documented hold related to a dispute applies, and then delete it. The link between the request and your profile and the per-family details are erased 12 months after closure, purely technical processing data (attempts, diagnostics) 30 days after closure, and explanations written by our team in a request made to support 12 months after the closure of that request. Where personal information was actually used to make a decision about you, it is retained for at least one year following that decision, as required by law, even if the normal retention period for its category is shorter; such retention is limited to the necessary information and subject to access restrictions. A deletion request submitted to support whose identity verification or security approval has not been completed within 30 days may have its technical procedure expire, following a review of its status; this expiry does not automatically close a pending request to exercise privacy rights, which remains subject to applicable statutory deadlines, response requirements and remedies.
  • Completed administration handovers and the related decisions of our team are kept for as long as the family exists and this evidence remains necessary, because they establish who administers it and on what basis, and are reviewed periodically; offers that did not succeed (declined, expired or cancelled) are deleted 12 months after the relevant offer is closed, and the explanatory note of an archiving by our team is erased 12 months after the archiving decision. One-time verification codes expire after 10 minutes and are destroyed as soon as they are used. We retain only the verification metadata necessary to substantiate the handling of the request. For an exceptional review, the minimal record includes the categories of independent verification elements checked, the results of those checks, the approvals by two authorized persons, the notice dates and objection period, and the final decision; it contains no secret verification codes, copies of identity documents or complete payment details. It is kept for 3 years after the request is closed; when that period ends, the information that identifies the administrator we asked, the family, the type of document, the date of the video call and the payment obligation relied on is erased or dissociated (the corresponding audit log entries follow the audit log rule set out below). Accepted authentication steps are kept for 24 hours to prevent their reuse, and the fingerprint of the objection link is erased when the request is closed. To prevent the same sensitive operation from being run twice by our staff (including the entry of verification elements), we keep for 24 hours, then delete, a cryptographic fingerprint of the request content (without the information entered in clear) and the operation’s technical response.
  • Operational notifications relating to these procedures are normally deleted 180 days after they are created; notification categories are distinguished according to their function and, where a notification or evidence of its dispatch is necessary to substantiate a decision, support a legal remedy or comply with a legal obligation, only the necessary minimal evidence is retained for the applicable period. In the audit log, events that establish the family’s governance decisions are kept for as long as the family exists and this evidence remains necessary; security events relating to the sending of verification codes have the personal identifiers they contain deleted or de-identified after 12 months, to the extent technically possible and consistent with retention obligations, a technical trace being kept to preserve the integrity of the log. Residual technical references may remain personal information and continue to be protected as such. After your account is deleted, these records no longer contain your email address or phone number; they may contain a technical identifier linked to your former profile ("Removed member" where it is kept, which is not anonymization) and, in notifications already received by other members and for as long as they are kept, the name under which you appeared in the family.
  • Content when the account is deleted: the erasure covers sent messages and their attachments, personal photos and files (photos on your own record, files you did not share to any family content), supporting documents, help requests and replies, service listings. Your contributions to the family heritage stay visible to the family, attributed to “Removed member”: verified family links, memories and photos added to a relative’s record, to memorials, places or heritage, cultural content, lexicon entries and shared documents, because they also concern other members; you may request their review (see section 13). Not deleted by this operation: billing entries, acceptances of the legal texts, audit-log entries, dispute files and proofs of consent, whose retention remains subject to the purposes, legal obligations and rights described in this policy.
  • One-time codes: a few minutes; pending sign-ups: for the validity of the code.
  • Face check: nothing is kept apart from the result (accepted or refused) in the audit log; a refused photo is deleted immediately.
  • Sessions and push notification tokens: a session remains valid for up to 30 days; the technical records of an expired or revoked session are deleted in accordance with our retention policy, normally within 30 days after its expiry or revocation. The push notification token is deleted earlier when the session is revoked, the account is erased, an unregister request is received or the token is found to be invalid; for a session that has simply expired, the token is no longer used and is deleted when the session record is purged.
  • Data export files: 7 days.
  • Subscription and payments: invoices, payments, refunds and financial records are kept to comply with applicable accounting and tax obligations, for the corresponding legal periods. Proof of payment authorisation, billing notices, trial data, transaction references and the card details displayed (brand, last four digits, expiry, used only to show you the saved card) are currently kept without automatic purge. Their retention period is determined according to applicable legal obligations, dispute and limitation periods, the existence of a dispute and, for trial data, the need to apply the rule of one trial per family and per paying administrator over 12 months. The absence of automatic purge does not mean indefinite retention: once these purposes have ended and no legal obligation prevents it, the information must be deleted or, where the law allows, anonymised. You may send a request for deletion or restriction to contact@ktmasolutions.com; it is reviewed against these criteria and the legal exceptions.
  • Pricing zone: the decision record (zone and country retained, nature and country of each indication, version of the geolocation database, fingerprint) is kept according to the retention periods and criteria applicable to billing entries and payment authorisation records, as specified in this section (“Subscription and payments”); the card-issuing country is removed from that record 30 days after the card is registered, the decision itself being kept. The file of a contestation (country stated, reason, decision and its reason, person who reviewed it) is kept with the same entries. This retention remains subject to legal obligations and to your rights regarding the protection of personal information. No IP address is kept for this purpose.
  • Proof of use of a paid feature: kept with the billing data of the corresponding period, for the same duration as that data (see above); when your account is deleted, the author account is dissociated, unless retention linked to a dispute is under way.
  • Dispute file: the dispute and its decisions are kept with the billing records; the items of the evidence file (accepted texts, payment authorisation, invoice, proof of use, billing emails, refunds) are protected against erasure during the dispute and for at least 180 days after it is closed, at which date our team reviews whether to keep them longer (remedies, proceedings, accounting obligation); this is not an automatic erasure, and each review is recorded. Personal information used to make a decision concerning an individual is also retained for the minimum period required by applicable law; the review conducted 180 days after a dispute is closed does not permit destruction before the expiry of a mandatory statutory retention period. At each review, the continued need for retention is documented, and information that is no longer necessary is destroyed or anonymised in accordance with applicable requirements. The content of the family space is never kept for this purpose.
  • Moderation reports: kept with the decision record. No automatic purge is currently applied to these records: their necessity is reviewed when the case is closed by our authorised team, and information that is no longer needed is destroyed or anonymised where the law allows, subject to retention necessary to support the measure taken, answer a challenge, defend rights or comply with a legal obligation.
  • Audit log of family decisions, proof of acceptance of legal texts, consents and billing records: these records are currently retained without automatic deletion. They are retained only for as long as necessary to establish or preserve the relevant governance, consent, billing or integrity evidence and to comply with applicable legal obligations. Once retention is no longer necessary for any of those purposes and no legal obligation requires otherwise, the information must be deleted or, where permitted by law, anonymised. More specific periods or criteria will be published as the retention schedule is formalised and implemented.
  • Conversations with the help assistant (account holders): kept encrypted for 30 days after the last exchange (a period KTMA Solutions Inc. may adjust; any change respects the stated purposes and data minimisation; the period in force is shown in your list of conversations), then deleted; you can delete a conversation at any time; they are deleted with your account and included in the export of your data. No visitor exchange is kept.
  • Human support requests: an unused confirmation link expires after 30 minutes and the unconfirmed request immediately undergoes the erasure and generalisation process described below; the text of your question is erased as soon as the request is closed, you withdraw your agreement or you cancel; an inactive request is closed after 90 days; a closed request goes through the anonymisation process at the end of the period counted from closure and stated in the information notice displayed before sending (180 days by default; a later reduction of this setting also applies, never an extension). When you delete your account, your support requests are closed and their personal information goes through the same process, except where continued retention is necessary to comply with an applicable legal obligation or for the establishment, exercise or defence of legal claims. In this exceptional situation, destruction is deferred by a reasoned, dated and logged decision, for no longer than strictly necessary, with a maximum expiry of three years for each decision; the deferral is reviewed and the request is processed during the next automated cycle after the hold is lifted or expires. After this process, the statistical information retained is limited to the type of request (call back or appointment), its topic and a generalised creation period (quarter or year); rare combinations undergo additional grouping measures and a re-identification risk assessment. Datasets that do not meet the applicable anonymisation criteria continue to be protected as personal information.
  • Erasure register: when you delete your account or a conversation with the assistant, or withdraw your agreement to pass on your question or cancel a support request, and when a file is erased from our storage, a minimal technical record (technical identifier of the account, conversation, request or file, nature of the operation and date; no name, email, phone number or content) is written, outside the main database, to our backup storage in Canada. It is used only to verify and re-apply these erasures if an earlier backup ever had to be restored; these technical identifiers remain protected as personal information for as long as indirect identification remains reasonably possible. It is kept for 60 days, then deleted automatically.
  • Security logs and support exchanges by email: these are retained only for as long as necessary to detect and investigate incidents, protect the platform, handle the relevant support request, defend legal rights or comply with a legal obligation. No automatic deletion is currently applied to these categories. Once those purposes have ended and no legal obligation justifies further retention, the information must be deleted or, where permitted by law, anonymised. More specific periods will be published once the corresponding retention schedule is formalised and implemented.
  • Backups: encrypted database backups are subject to an expiry rule after 35 days; versions that become non-current are also deleted automatically. These operations are carried out asynchronously by the hosting provider and may take additional time; KTMA Solutions Inc. periodically checks the configuration and execution of these cycles and takes corrective action if any overrun is detected. Files have a separate backup copy; when a file is erased, the erasure is recorded in a log and then applied to the copy, within a window of up to 45 days, the execution of which is also checked. Older database backups are not rewritten to remove a record: they expire at the end of their cycle. If a backup ever had to be restored, the service remains blocked from being brought back online until the erasures, deferred deletion requests, their cancellations and the related governance decisions made after that backup have been reconciled: erasures are reapplied, so that erased information does not become accessible again, and deferred deletion requests that are still valid are restored and can only be executed after a review by our team.
  • Referral: information relating to referral relationships, complimentary months, decisions and their reasons, and supporting calculation records is retained with the relevant billing records under the same retention rules described in “Subscription and payments”. This information may be used to document the application of benefits, handle disputes, prevent abuse and comply with applicable legal obligations. The referral code is retained while the family exists; when renewed, the previous code is deactivated. Retained relationships use technical identifiers. When an account is deleted, information relating to the account that established the referral is dissociated in accordance with the applicable rules described in this section. The system does not currently perform automatic deletion of these records; their retention remains subject to applicable legal requirements concerning retention limits and deletion or anonymization once the purposes have been fulfilled, subject to legally required retention periods.

Pseudonymisation or replacing a person’s displayed name does not necessarily constitute anonymisation. Where the law requires the destruction of personal information once the purposes for which it was collected or used have been fulfilled, that information must be destroyed or, solely under the conditions permitted by law, anonymised in accordance with the applicable regulatory criteria so that it is no longer possible to identify the person concerned, directly or indirectly, in an irreversible manner.

12. Security

  • encrypted connections (TLS) and several categories of sensitive data encrypted at rest (notably messages, supporting documents and technical secrets); database backups encrypted;
  • passwords hashed with Argon2id, limited attempts, progressive lockout, messages that do not reveal whether an account exists;
  • two-step verification required for the roles and actions for which the platform imposes it;
  • email alert when signing in from a new device and on every password change;
  • antivirus scanning of uploaded files and removal of photo metadata;
  • staff access limited to what is strictly necessary and traced.

No system is infallible. In the event of a confidentiality incident or data breach, we take the necessary measures to limit its consequences and comply with the notification obligations that apply in each country: depending on the applicable law and the level of risk, we notify the competent authority and the people concerned within the time limits and according to the thresholds set by that law.

13. Your rights

Depending on the law that protects you, you have the following rights:

  • access to your information and a copy of it;
  • rectification of inaccurate information;
  • erasure or de-indexing, subject to legal retention obligations and exceptions (see section 11);
  • portability: where this right applies, receiving the information covered by law in a structured, commonly used format; some data concerning third parties, or subject to a legal exception, may not be included; transmission to another authorised organisation may be requested where the law requires it and it is technically possible;
  • objection and restriction of processing;
  • in respect of a decision based exclusively on automated processing (notably the pricing zone, section 8): to be informed, to know the information used and the reasons and principal factors of the decision, to submit your observations and to obtain review by a person;
  • withdrawal of your consent at any time, where processing depends on it;
  • directions about what happens to your data after your death, and exercise of certain rights by your relatives or successors where the law provides for it.

Right to object (GDPR): If the GDPR applies to you, you also have the right to object, on grounds relating to your particular situation, to the processing of your personal data based on our legitimate interests (Article 21 GDPR). You can exercise this right by turning off “Show notification details” or by contacting our privacy officer using the contact details provided in this policy. We will assess any objection in accordance with the GDPR and stop the relevant processing unless we demonstrate compelling legitimate grounds overriding your interests, rights and freedoms, or the processing is necessary for the establishment, exercise or defence of legal claims.

You can exercise some of these rights directly in Settings › Privacy: request an export of your data, manage your consents, delete your account. For other requests (further access, rectification, objection, restriction, a request about a relative or a deceased person), write to contact@ktmasolutions.com. We reply within the time limits of the applicable law after verifying your identity (for example one month under the GDPR and, in Quebec, in principle 30 days for access or rectification requests); any refusal is reasoned and states the remedies available. If you are the paying administrator, deleting your account cancels the family’s subscription: no new charge is initiated for future periods, access already covered stays open to the family until the end of the corresponding period and a written confirmation is sent to you. A payment initiated before the deletion (card charge in progress, Mobile Money payment awaiting validation) may nevertheless be completed afterwards by the provider: the deletion is neither refused nor delayed; if that payment goes through, the period it was paying for is excluded from coverage and its full amount is returned to you (card: refund of the original payment; Mobile Money: transfer to the wallet); if it fails, nothing is owed on that account. If you delete your account within 14 days after a settled payment, the deletion is recorded as a request under the 14-day commercial guarantee: our team checks whether a paid feature has been used during the period covered by that payment, before the request was received (any later use does not retroactively remove the guarantee); if none has, the full refund is made by the same payment method; otherwise the guarantee gives no right to a refund, without prejudice to your statutory rights. As your address is erased with the account, the decision is not sent to you by email; you may ask for the outcome at contact@ktmasolutions.com. When you request deletion of your account while you are the only administrator of an active family, your request may be recorded for deferred processing after verification by code. Administration offers require express acceptance by eligible members. Adult family members concerned may be informed of the handover process and the identities of members offered the role, without disclosure of the private reason related to your account deletion request. If no successor accepts, our team may intervene under the applicable security and governance procedures, including by making another administration offer or, as a last resort, archiving the family. Starting on day 27, if no one has accepted and the situation has not been resolved, we normally place the family in read-only mode (without its data being erased solely because of that restriction) and your account deletion may then be executed; this mechanism may be suspended for security reasons, technical incidents or to preserve an existing administrative restriction, in which case the request remains pending and is followed up by our team. Our team may reactivate the family through an administration offer accepted by a member. If you can no longer access your account, the same process applies to a deletion request made to our team, subject to verification using a code sent to the contact details registered to your account and to applicable security checks, and whose execution must be approved by a second authorized team member.

If you no longer have access to either your registered email address or your registered phone number, you may ask our person in charge of the protection of personal information for an exceptional review, described in section 19 of the terms of use: it serves only to delete the account (never to regain access to it), relies on at least two independent verification elements (including an authenticator code or an identity document checked by video call), with no copy of an identity document, a code or complete card data kept, includes a notice by email to the address still registered and an in-app notification (no SMS), a 14-day objection period and approval by a second authorized team member using multi-factor authentication, and leads to a reasoned response with the available remedies; the information processed in this context is described below. You may cancel your request until its execution begins. Once the conditions for execution are met, our system performs logical account deletion and triggers the associated mechanisms for erasure or justified retention of the relevant data. Our internal aim is to resolve deferred requests within 30 days. This target does not restrict your rights or our applicable legal obligations; requests that cannot be completed within that period remain subject to internal follow-up. Deferring account deletion does not suspend any legally applicable response deadline for requests concerning your personal information. Where full execution cannot occur immediately, we provide the information required by applicable law concerning the request’s status, relevant reasons, and available remedies. Account deactivation and anonymization are distinct from the destruction of all associated personal information. Some information may be retained temporarily where a legitimate purpose or legal obligation justifies doing so. Applicable retention periods, access restrictions, and destruction or anonymization procedures continue to apply. Deleting the account does not automatically erase invoices, accounting records, proof of payment or other information whose retention remains legally justified; such information may be the subject of a separate request for access, rectification or erasure under the conditions provided by law.

Exceptional deletion review (person who no longer has access to their email or phone): information processed. We process the categories of verification elements presented and their result (verified or failed); for the video call, the type of identity document presented, the date of the verification and the identifier of the authorized agent; for an attestation, the account of the administrator whose confirmation we request, the family concerned, the channel through which you designated that administrator and their answer; for a payment verified successfully, the internal reference of the payment obligation relied on; the log of notices (type, result and time at which our email-sending service accepted them, without the address or the link); any objection (from the account or through the link); the reason for a report received outside the application; the decisions and the authorized persons who made them; and the corresponding audit log entries. We never keep a copy, screenshot, photograph or video of an identity document, nor its number, nor the authentication codes you read out (a backup code presented is only marked as used, and the accepted authentication step is kept for 24 hours to prevent its reuse); the one-time codes sent to the administrator we ask are handled by our authentication mechanism (section 11) and are not entered in the review file, nor the date, amount or last four digits of the card number given to verify a payment. To verify a payment, our team queries Stripe using technical payment identifiers we have already recorded: Stripe confirms the amount, the currency, the customer and the last four digits of the card to us, which we compare with what you tell us, and what you tell us is not entered in the review file. Stripe may process this information outside Quebec (section 10). The administrator we ask receives an in-app notification giving your name and stating that they are asked to confirm your identity for a step related to your account; they do not receive the elements verified, the reason for the step or its timetable, and they may confirm or answer that they cannot confirm, without giving a reason. To be asked, they must have an email address registered on their account; they sign in again before answering (recent multi-factor authentication, or a code sent by email to their own address). The 14-day objection period runs from the moment our email-sending service accepts the last required notice: that acceptance establishes neither receipt nor reading of the message. We send no SMS in this procedure. Retention periods are set out in section 11.

You may also lodge a complaint with the supervisory authority: in Cameroon, the personal data protection authority established by law no. 2024/017; in Canada, the Office of the Privacy Commissioner; in Quebec, the Commission d’accès à l’information; in the European Union, the competent supervisory authority, including that of your habitual place of residence or, in France, the CNIL.

14. Cookies and local storage

Case Familiale uses no advertising cookies, no third-party trackers and no audience-measurement tools. We only use cookies and local storage needed for operation: keeping your session (secure cookie not accessible to scripts), a random device identifier to flag unusual sign-ins, chosen language, drafts and display preferences. In the mobile app (version published on Google Play: no advertising, no audience analytics tools, no telemetry transmitted, and no app updates delivered outside Google Play; Google Play may nevertheless collect crash reports independently under its own terms), the device also keeps: your session tokens in the system’s secure storage, an encrypted local cache of data already viewed, and the offline map packs you downloaded; when you sign out or switch accounts, the app deletes this cache and these packs; changes made offline and not yet transmitted may nevertheless remain stored in encrypted form, including after sign-out, pending transmission or deletion; uninstalling the app deletes all local data (the app is not backed up by the Android system); fingerprint or face unlock is handled by the device’s operating system and no biometric template is sent to us. You can manage the privacy settings available from the Privacy page; cookies strictly necessary for the service to work cannot be switched off from that page.

15. Applicable laws

  • Cameroon: law no. 2024/017 on the protection of personal data.
  • Quebec: Act respecting the protection of personal information in the private sector, as modernised notably by Law 25.
  • Canada: where it applies, the Personal Information Protection and Electronic Documents Act (PIPEDA).
  • Members residing in the European Union: Regulation (EU) 2016/679 (GDPR).
  • Any other mandatory personal-data protection law applicable to the processing concerned under its material or territorial scope.

Where the applicable law makes a processing operation or transfer subject to a formality, declaration or prior authorisation by an authority, we complete the required formalities before the processing concerned.

16. Changes to this policy

Each version is dated and numbered. When a new version is published, it may be presented to you at your next sign-in, and the acknowledgement or acceptance requested by the service is recorded with the version number. This general acceptance does not replace the specific consents required for certain processing. Previous versions remain available and can be provided on request.

A question about this text? Write to us at contact@ktmasolutions.com

Back to top