Privacy policy
Ascendance is for building a family's tree among its members. We process the minimum needed for that, with no advertising and no sale of data.
Data controller: Tristan Laroubine, 1 Route des Dolines, 06560 Valbonne, France. Contact: ascendance@laroubineco.com.
This website
The website sets no cookies and loads nothing from third parties, fonts included. Visits are measured with Umami, without cookies: it counts page views, the referring page, the type of device and the country, without keeping IP addresses or any identifier that could follow you from site to site.
Your account
When you sign in with Google or Apple, we receive your name, your e-mail address (or Apple's relay address if you hide it), your Google profile photo and an account identifier. They are used to recognise you, to give you access to the families you belong to and to write to you about them (invitation, access granted). Legal basis: performance of the service you ask for.
The session is kept in a strictly necessary cookie (ascendance_session), valid for 30 days, or, in the apps, in the keychain of the iPhone, iPad and Mac or in Android's encrypted storage. No other cookie is set.
If you allow notifications in the app, the server keeps the token the iPhone, iPad, Mac or Android system gives for that device, tied to your session. It is only used to tell you of what awaits an answer (a request to join a family, access granted, a proposed correction, the team's reply) and is deleted when you sign out. You choose in the app which notifications you receive, and can turn them off in the device's settings. Legal basis: your consent, given on the device.
To learn what is used and improve the app, the server counts, per day and per account, the days of use, the platform (web, iPhone, iPad and Mac, Android), the kind of device and the size of its screen (phone, tablet or computer), the language of the app and the one the device or browser prefers and the features used (screens opened, additions, exports, opening the help…), the rating requests and suggestions to recommend the app (shown, followed or dismissed, and how the message was sent), the version of the iPhone, iPad, Mac and Android apps and the invitations to update them (shown, followed or put off), without anything from the tree's content. These counters only feed the team's overall statistics and are shared with no third party. The server also keeps, for each account, the platform used, the app version, the system version and the device model; the team may look at them. Legal basis: our legitimate interest in developing the service.
To protect the service from abuse, the server counts the requests it receives per hour and per function, without their content, and limits their number per account or, when signed out, per IP address. When a limit refuses a request, it keeps the account or IP address concerned. These records are erased after 90 days and are shared with no third party. Legal basis: our legitimate interest in protecting the service.
When an account is opened, the app also notes how you arrived: the site that sent you (its name only, never the page's full address), the campaign of the link you followed (utm_* parameters), the page of this site you left for the app, or the store (the App Store; on Android, Google Play passes on where the installation came from). This site keeps these clues in your browser for the visit, the web version until you sign up. This origin is linked to the account, is only used for our statistics and is entrusted to no one. Legal basis: our legitimate interest in knowing how people hear about Ascendance.
The tree's data
A family's members enter names, dates and places, occupations, life events, notes and photos, including about living people. These data are visible only to the accepted members of that family, according to the role given by its administrator, and are never published or indexed, with one exception the family decides on:
an editor of the family may create a public link to the resting place of a deceased person, so that others can find the grave. Anyone with that link then sees, without an account, the person's name, dates of birth and death, the cemetery, the grave's plot and position, the directions to find it and its photo, and nothing else of the tree. The server keeps only a fingerprint of the link; the page is not indexed by search engines. The link stops working as soon as an editor withdraws it or creates a new one, the resting place is deleted or the person is no longer marked as deceased.
Documents linked to a person (records, censuses, photos…) stay with the service where their owner keeps them (Google Drive, Dropbox, an archives website…): Ascendance keeps only the link and the reference, and does not read their content. The preview of a Google Drive or Google Docs file, shown when the reader asks for it, is loaded directly from Google with the reader's own Google account, under Google's rules and the sharing chosen by the file's owner.
Someone who appears in a tree can ask the family's administrator to correct or delete their entry, or write to us.
Supporting Ascendance
If you choose to support the app (optional, with nothing in return), we keep for each contribution its amount, date, frequency (one-off or monthly), the payment method (Stripe or App Store), the payment's reference with that provider and the account's e-mail address. They are used to send you a receipt, to show the “Patron” badge on your account, to stop a monthly contribution and to keep the accounts. Legal basis: performance of your request, then the legal obligation to keep accounting records.
We never see your card number: payment happens on Stripe's page or in the App Store. Your first name appears on the “They support Ascendance” page only if you enter it yourself when contributing; write to us to remove it.
If you decline to be asked to support the app, we only keep the date of that choice. The device keeps a few counters locally (days of use, people and photos added) to choose when to ask; they never leave the device. The server counts each day, without knowing who, the suggestions shown and the support pages opened.
Testing the Android app
If you sign up to test the Android app (Android page), we keep the e-mail address and first name you enter, the page's language and the dates of the sign-up and of the invitation. They are only used to send you the invitation and to write to you about the test. Legal basis: your request. To become a tester, you join a Google Groups group yourself and accept the test on Google Play: Google then sees your Google account's address, under its own rules.
Services involved
- Google and Apple, for signing in, depending on the service you choose. These companies may process data in the United States, under the Data Privacy Framework.
- Brevo (France), for invitation and notification e-mails: the recipient's name and address.
- Apple (Apple Push Notification service) and Google (Firebase Cloud Messaging), to carry notifications to your device: its token, the notification's title and text.
- Oracle (Oracle Cloud Infrastructure, Marseille data centre, France), which hosts the server: the database, the photos and the daily backups are stored there, in France.
- Backblaze (B2 storage, European data centre), for the off-site copy of the backups: each copy is encrypted on our server before it leaves, and Backblaze cannot read it.
- Google Groups and Google Play, for testing the Android app: the testers' group and the app's installation go through your Google account.
- Stripe (Stripe Payments Europe, Ireland), for paying a contribution on the web: Stripe receives your e-mail address and the payment details you enter on its page, and sends us the amount and the payment's reference. Stripe may process data in the United States, under the Data Privacy Framework.
- Apple, for a contribution in the iPhone, iPad or Mac app (in-app purchase): Apple collects the payment and sends us a signed transaction (product, date, reference), without your name or payment details.
- OpenStreetMap (Nominatim, Photon) and geo.api.gouv.fr, to place locations on the map and suggest places while typing. The server only sends them place names.
- Google Fonts, from which the web app loads its fonts: Google sees your IP address.
- The map tile provider, whose images your browser loads when showing the map: it sees your IP address, as with any website.
Retention periods
- The account, until it is deleted.
- Sessions, 30 days after their last use.
- Contributions, ten years for the accounts, including after the account is deleted (the contribution is then linked to no account; the e-mail address at the time is kept).
- The tree's data, as long as the family exists; deleting a family erases its tree and photos.
- Sign-ups to the Android test, until the test ends, or earlier on request.
- Backups: every day, a copy of the database on our server, kept 14 days, and an encrypted off-site copy, kept in tiers (14 daily, 8 weekly, 12 monthly). Deleted data may therefore remain in these copies for up to about a year; they are only opened to check that they can be read back or to restore the service after an incident.
Your rights
You can access your data, correct it, erase it, object to its processing and take it with you: the tree can be exported at any time as GEDCOM or JSON.
Deleting your account
- In the Android app, or in the iPhone, iPad or Mac app: Account tab, “Delete my account”, then confirm.
- In the web version (app.ascendance.laroubineco.com): your account menu (your picture, top right), “Delete my account”, then confirm.
- Without access to your account: write to us at ascendance@laroubineco.com from the account's address; we delete it within a few days.
Deleting erases your account (name, e-mail address, profile photo, Google and Apple sign-in identifiers), your sessions, your access to families, your help requests and the origin of your sign-up. What remains: the entries you made in a tree, which belong to the family; any contributions, detached from the account, for the accounts; a line of the administration journal (name, address, sign-up date, families) that records the deletion. Backups then lose it as they are renewed (see the retention periods).
If you believe your rights are not respected, you can complain to the French data protection authority, the CNIL, or to the authority of your country.