This privacy policy has been prepared in accordance with Article 13 of Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation, hereinafter the "GDPR") and the Finnish Data Protection Act (1050/2018). This policy concerns Breedmap, a breeding and strain tracking application for living organisms such as plants, fungi and animals (hereinafter the "Service"), and the processing of the personal data of its users (hereinafter the "User").
In short #
- Who: We are Breedmap. You can reach us at [email protected].
- Age: You must be at least 15 to have your own account. Younger children can have a child account created by their guardian.
- What we collect: your account details, your email address, your name (required at registration, and shown to other users only if you choose to share it), your full birth date (never shown to other users), your profile photo and address (if you add them), your breeding and cultivation data, your photos and their metadata, and technical data (IP address, browser and country).
- Why: We use the data so that the service works and stays secure.
- Where: Your data is stored on your device and on our own server in the EU.
- Who else sees data: Cloudflare relays the service's traffic. Google receives data if you sign in with a Google account. An email service provider sends our emails. We do not use advertising or third-party analytics tracking, and we do not sell your data.
- Support requests: if you ask a person for help in the help chat, our staff read your request and the last AI answers in that chat. Replies arrive as messages from "Breedmap support".
- New sign-in alerts: If someone signs in to your account from a new device or a new country, we email you (and send a push notification if you have the app) with the approximate place, the IP address, the device and the time, and a "This wasn't me" button that locks the account down.
- Messages: Registered users can send each other text messages in the app. Messages are stored on our server, encrypted at rest. We can technically read them, but our administrators read only messages that a user reports, plus a few messages around them. Child accounts cannot send or receive messages. When you report a message you agree that the reported message and a few around it go to our administrators.
- Photos: The exact location of a photo stays private in your own workspace. Anything shown to others uses a rounded location of about 1 km. Uploaded photos may be scanned automatically, including with artificial intelligence, for the purposes of the Service.
- Shared analytics: We analyse breeding lines and breeding efficiency from all users' data in anonymised or aggregated form. You can object to this.
- When you delete your account: We delete your personal data: your name, email address, birth date, address, profile photo and login data. Your items, their lineage and their photos stay in a workspace without an owner, so that other users' links do not break. They are shown as "owner no longer present". You can ask us to remove or sanitise specific photos or text.
- Unused accounts: If you do not use your account for 12 months, we delete the personal data in the same way. We email you 30 days, 14 days and 1 day before.
- Your rights: You have the right to see, correct, delete and transfer your data and to object to its processing. You can also lodge a complaint with the Data Protection Ombudsman.
For children and guardians:
- For you, if you are under 15: You cannot create a Breedmap account yourself. Your guardian creates a child account for you from their own account and enters your email address. You then get an invite and set your own login. Your guardian can read your account and decide about publishing. If someone under 15 creates an account in some other way, we delete it. On your 15th birthday your account becomes a normal account, and we tell you 30 days before. If anything is unclear, ask your guardian.
- For guardians: A child account is created only from the guardian's own account, with a declaration that you are the child's guardian. A guardian must be at least 18. A child can have up to two guardians. You exercise the child's data protection rights until the child turns 15. Requests: [email protected]. Section 13 is binding.
This summary is provided for ease of reading. The privacy policy below is binding and prevails if the summary and the policy differ.
1. Controller #
Name: Breedmap
Business ID: Not yet granted
Email: [email protected]
At the time this policy was prepared, the Controller has not been registered as a limited liability company and does not have a Business ID. The Controller's identification details (including the official name, Business ID and postal address) will be updated in this policy without delay after the company has been registered.
2. Contact person for data protection matters #
Enquiries concerning the processing of personal data and requests to exercise data subject rights shall be sent by email to [email protected].
The Controller has not appointed a data protection officer, as the conditions for the obligation to appoint one under Article 37 of the GDPR are not met.
3. Personal data processed #
The Controller processes the following personal data concerning the User:
"Profile photos" means photos added to a User's profile. "Gallery photos" means photos added to items in the Service (for example species or other item entries). Where this policy refers to "photos" without qualification, both profile photos and gallery photos are meant.
- Account data: username, data required for authentication (the password is stored only in hashed form) and technical data on the time of account creation and use;
- Email address;
- Name: the User's name is mandatory at registration, as it is needed to identify the User. The name is shown to other users only when the User chooses to share it;
- Birth date: every User gives their full birth date at registration. A guardian gives theirs and the child's. The birth date is not shown to other users;
- Guardian declaration (child accounts only): who made the declaration, for which child, when, and which version of the text was accepted;
- Profile photo, if the User has added one;
- Address, if the User has provided one;
- Breeding and cultivation data: data stored by the User in the Service on plant and fungal strains, crosses, generations, growing conditions, observations and other similar entries, insofar as they can be linked to the User.
- Gallery photos and their metadata: photos the User adds to items. When a photo is uploaded, the Service reads its metadata (time of capture, location, device information) and shows it to the User in the upload window, where every field is ticked by default. The User can untick any field. The metadata is then stored in the database and removed from the stored image file. Profile photos are re-encoded on upload; their metadata is removed and not stored.
- Location of photos. The exact location is stored privately in the User's own workspace and cannot be edited afterwards; on request it can only be replaced by the rounded location (see section 10). Everything shown outside the User's workspace uses a rounded location of about 1 km: public pages, and a separate shared copy of photo metadata used for identification and mapping. The shared copy contains no name, workspace or item name. It contains a hidden reference to its source so that erasure and objection requests can find it. A rounded location can still point to an area where a User lives or grows plants.
- Public pages. What a public page shows follows the sharing ticks of each field, which the owner can change at any time.
- Messages and messaging data: the text of messages you send and receive, the links to items in them, the sender, the recipient, the time, whether a message was read and in which mailbox it is, your messaging settings (who may message you, push text choice), your friends, contacts and blocked users, the device token used for push notifications, and reports you make or that are made about you. Photos are not sent in messages.
- Technical data: IP address, browser and device data (User-Agent) and a country code derived from header data relayed by Cloudflare, which are stored in connection with the session.
- Sign-in notice data: for each account, a list of the devices and countries the User has already been notified about, with the time of each notice. A device is stored only as a one-way hash (SHA-256) of its device identifier, never as the identifier itself. For each notice sent, a record of what was new (device, country or both), the country code, the device label (for example browser and operating system), the time, and whether and when "This wasn't me" was used. The notice record does not contain the IP address or the city (see section 5, "New sign-in notices").
The Controller complies with the principle of data minimisation (Article 5(1)(c) of the GDPR) and processes only personal data that is adequate, relevant and limited to what is necessary in relation to the purposes of the processing.
4. Sources of personal data #
Personal data is obtained from the User themself in connection with registration and use of the Service. Technical account data is generated in connection with use of the Service. In addition, the Service's server logs automatically generated technical data, such as the browser version and device data, in connection with use of the Service. If the User signs in to the Service with their Google account, the Controller receives from Google the User's Google user identifier, email address and name. The country code is obtained automatically from request headers relayed by Cloudflare (CF-IPCountry). For new sign-in notices, the approximate city is obtained from a Cloudflare request header (CF-IPCity), which is Cloudflare's estimate based on the IP address.
5. Purposes and legal bases of processing #
| Purpose of processing | Legal basis |
|---|---|
| Creating and maintaining the user account, identifying the User | Performance of a contract (Article 6(1)(b) of the GDPR) |
| Checking age and eligibility with the birth date: the minimum age (15), guardians aged 18 or over, and conversion of a child account at 15 | Legitimate interest of the Controller (Article 6(1)(f)); for child accounts also the guardian's consent (Article 6(1)(a)) and the contract with the guardian (Article 6(1)(b)) |
| Providing the Service, including storing breeding and cultivation data and synchronising it between devices and the server | Performance of a contract (Article 6(1)(b)) |
| Necessary communications relating to the Service, such as sign-in codes, notices before account deletion, notices about child accounts and link requests, changes to the service and personal data breaches | Performance of a contract (Article 6(1)(b)) and compliance with a legal obligation (Article 6(1)(c)) insofar as the communication is based on law |
| Processing of voluntary data, such as the profile photo and address, and other processing for which the User's separate consent is requested | Consent (Article 6(1)(a)) |
| Handling and notifying personal data breaches and maintaining the record of processing activities | Compliance with a legal obligation (Article 6(1)(c)) |
| Measuring and analysing breeding lines, breeding efficiency and other similar aggregate-level observations based on Users' combined data (see further below) | Legitimate interest of the Controller (Article 6(1)(f)) |
| Delivering messages between users, keeping friends, contacts and blocks, the Other mailbox and the daily limit, and sending push notifications of new messages | Performance of a contract (Article 6(1)(b)) |
| Providing the in-app AI helper and species search by other names: the question the User types, the earlier messages of that chat and the search text are sent to Anthropic, PBC (see section 8) | Performance of a contract (Article 6(1)(b)) |
| Answering a support request: administrators and owners read the request and the last AI answers in the help chat | Performance of a contract (Article 6(1)(b)) |
| Staff support access: staff enter a workspace to help with a problem, only after a workspace owner approves, for a limited time and read-only by default (see "Staff support access" below) | Performance of a contract (Article 6(1)(b)) and legitimate interest of the Controller (Article 6(1)(f)), limited by the owner's approval for each session |
| Handling a report of a message: staff read the reported message and a few messages around it, and may block an account or contact the users involved (see below) | Legitimate interest of the Controller (Article 6(1)(f)); for the reporter, also the agreement given when reporting. Where the law requires it, compliance with a legal obligation (Article 6(1)(c)) |
| Preventing abuse of messaging, such as spam: the daily limit for messages to people who are not friends or contacts, and blocking | Legitimate interest of the Controller (Article 6(1)(f)) |
| Signing in with a Google account (OpenID Connect) | Performance of a contract (Article 6(1)(b)) |
| Processing of gallery photos and their metadata for the purposes of the Service, for example species identification, data analysis, disease detection, comparison of individual characteristics, content checks and keeping the Service lawful | Legitimate interest of the Controller (Article 6(1)(f)): processing gallery photos is a core function of the Service from which the User benefits. |
| Keeping and showing the direct lineage of an item whose owner is no longer present, to find the cause of hidden mutations and inherited diseases in living organisms (see section 10a) | Legitimate interest of the Controller (Article 6(1)(f)) |
| Relaying network traffic and ensuring the security of the Service, including processing technical data in Cloudflare's network | Legitimate interest of the Controller (Article 6(1)(f)) |
| New sign-in notices: comparing each sign-in with the account's earlier devices and countries, telling the User about a sign-in from a new device or country, and securing the account when the User answers "This wasn't me" (see "New sign-in notices" below) | Legitimate interest of the Controller and the User (Article 6(1)(f)) in keeping accounts secure, and performance of a contract (Article 6(1)(b)). The notices are also a security measure under Article 32 |
Uploaded photos may be scanned automatically, including with artificial intelligence, for the purposes of the Service, such as species identification, data analysis, content checks and keeping the Service lawful. Photos showing people can be removed on request.
Where processing is based on consent, the User has the right to withdraw their consent at any time. Withdrawal of consent does not affect the lawfulness of processing based on consent before its withdrawal.
Messages #
The Controller is the controller of the personal data in messages. Messages are stored on the Controller's server, encrypted at rest, and are not end-to-end encrypted. This means the Controller can technically read them. The Controller does not read messages in normal operation. Administrators read messages only in these cases: a user reports a message, the law or an authority requires it, or it is necessary to investigate a security incident.
Reporting a message. When you report a message, the reported message and a few messages before and after it in the same conversation are shown to the Controller's staff (owners, administrators and moderators). The app tells you this before the report is sent, and by reporting you agree to it. The staff read them to decide whether the Terms were broken, and may block an account, remove content or contact the people involved. They read nothing else in the conversation. Staff sign in to a separate administration system with their own login, never with an ordinary user account. The messages around the reported one can include messages of other people, including the person you reported. Reading them is based on the Controller's legitimate interest (Article 6(1)(f)) in keeping the Service safe and handling abuse, and on the need to protect users from harassment. The Controller has weighed this against the interests of the people in the conversation: access is limited to administrators, to the reported message and a few around it, and to the purpose of handling the report.
Who can message you. You choose whether you receive messages from known people only or from anyone. Messages from people you have not allowed go to the "Other" mailbox, without an alert or push notification. You can block a user. The blocked user cannot reach you, and is not told.
Child accounts. Child accounts cannot send or receive messages. If someone uses "send message" towards a child account, the message goes to the child account's guardian.
Push notifications. A push notification of a new message is sent through the push services of Google (Firebase Cloud Messaging) and, on Apple devices, Apple. You choose what the notification shows: a generic text (default), the sender's name only, or a preview of the message. If you choose the name or the preview, that content goes through these services. Messages in the Other mailbox never cause a push notification.
No other use. The content of messages is not used to train artificial intelligence models and is not used for analytics or research. It is processed only to deliver messages, for the safety and abuse handling described above, and where the law requires.
Support requests. If the help assistant cannot solve your problem, you can ask a person. The request you send, and the last AI answers in that help chat, are shown to the Controller's administrators and owners. The app tells you this before you send, and by sending you agree to it. They read them only to answer you. The reply comes to you as a message from "Breedmap support" and, if allowed, a push notification. The legal basis is performance of a contract, because you ask for the help (Article 6(1)(b)). A support request needs an online account.
Messages from staff. Administrators and owners may send a message to any registered user, for example about the Service, the user's account or a report.
Staff support access #
To help with a problem, the Controller's staff (owners, co-owners and administrators; not moderators) can enter your workspace only after a workspace owner allows it. The owners of a workspace are told in the app, by push notification and by email; if no owner answers within 15 minutes, the request is refused. Each access is for one staff member and one workspace. It is read-only unless the owner also ticks "Allow editing". It lasts at most the time the owner chooses (1 hour by default), and it ends when that time runs out, when the staff member ends it, or when an owner ends it, which an owner can do at any time. While access is active, the workspace shows who has access and until when. Staff can see items, projects, settings and sync state. Even with editing allowed, they cannot read messages, change sign-in details, passkeys or two-factor settings, delete the workspace or account, change licences, billing, seats or members, start a data export, or act in other workspaces. Every request, decision and staff action during the access is written to a log that cannot be changed. Owners can see this log in the workspace settings, and it is kept for 12 months. The legal basis is performance of a contract (Article 6(1)(b)) and the Controller's legitimate interest in giving support (Article 6(1)(f)). The owner's approval for each session limits the access and makes it visible.
New sign-in notices #
After every successful sign-in, the Service checks two things: whether the device has never been used on the account before, and whether the country of the sign-in is not among the countries of the account's sign-ins in the last 90 days. The country comes from our network provider (Cloudflare). The very first sign-in of an account, and a sign-in whose country is unknown, never cause a notice. The check never blocks a sign-in and makes no decision about the User; it only decides whether a notice is sent.
If the device or the country is new, the Controller sends the User an email and, if the User has the app with notifications allowed, a push notification. The email shows the country and, when available, the approximate city, the IP address of the sign-in, the device and browser, the time, and a "This wasn't me" button. The city is Cloudflare's estimate from the IP address and is often wrong, for example on a mobile network or a VPN. The push notification has a generic text only: no place, IP address or device.
The IP address and the city are taken from the sign-in request and placed only in the email. The notice itself does not store them. The Controller stores a list of the devices (as a one-way hash) and countries the User has already been told about, so that the same device or country does not cause a new notice, and a record of each notice without the IP address or city (see section 3). Separately, the sign-in log, which existed before this feature, records each sign-in with its full IP address and is kept for 90 days (see section 10).
"This wasn't me". The button works once and for 7 days. When the User confirms it, the Service signs out all devices, removes the password, cancels a pending email change and unused sign-in codes, and requires a second sign-in step at the next sign-in. It also removes passkeys, linked sign-ins (such as Google) and an authenticator app that were added in the 7 days before, because an attacker may have added them; older ones are kept and the User is asked to check them. The Service then emails the User a confirmation of what was done. The action is recorded in the sign-in log.
The notice data is included in the copy of the User's data under the right of access and data portability (section 11), and is deleted when the account is deleted (section 10).
Aggregated breeding analytics #
Once a sufficient amount of data has accumulated in the Service, the Controller intends to measure and analyse breeding lines, breeding efficiency and other similar aggregate-level observations based on the data of multiple Users. This is a purpose of processing that extends beyond the User's own use of the Service.
Whenever possible, the processing is carried out using anonymised or aggregated data. The results of the analysis are published and used only in a form from which an individual User cannot be identified.
The legal basis for the processing is the legitimate interest of the Controller (Article 6(1)(f) of the GDPR). The Controller's legitimate interest consists of developing the Service and producing knowledge about breeding. The Controller has carried out and documented a balancing test in which the Controller's legitimate interest has been weighed against the User's interests and fundamental rights and freedoms. Based on the balancing test, the impact of the processing on the User has been assessed as minor, because the processing concerns anonymised or aggregated data and individual Users cannot be identified from the results. In addition, the User can reasonably expect that a provider of a breeding and strain tracking service uses the data accumulated in the service in aggregated form to develop the service and to produce knowledge about breeding.
As this is a new purpose of processing, the Controller has, in accordance with Article 6(4) of the GDPR, assessed its compatibility with the original purposes, taking into account, among other things, the link between the purposes, the context in which the personal data was collected, the nature of the data, the possible consequences of the processing for Users and appropriate safeguards, such as anonymisation and aggregation. Based on the assessment, the processing is compatible with the original purposes.
The User has the right to object to this processing in accordance with Article 21 of the GDPR (see section 11).
Legitimate interest assessment: gallery photos #
Assessment dated 16.10.2026, updated 17.10.2026. The Controller has assessed the processing of gallery photos and their metadata (capture time, location, device information) on the basis of its legitimate interest (Article 6(1)(f) of the GDPR) as follows.
1. Purpose test: the Controller's interest. The Controller processes gallery photos uploaded by Users, and their metadata, for the purposes of the Service, for example species identification, data analysis, disease detection, comparison of individual characteristics, content checks and keeping the Service lawful. These are examples and not an exhaustive list. Processing gallery photos is part of the core function of the Service: tracking the breeding and lineage of plants and fungi. Users benefit from it directly through identification, disease insight and comparison of their own lines. The interest is lawful, clearly stated and real, not speculative.
2. Necessity test. Identification, disease detection and comparison of characteristics need the images. Time and location improve accuracy, because species, season and region are linked. Less intrusive alternatives are used: the file itself carries no metadata; the exact location stays in the owner's workspace; outside the workspace only a rounded location is used; the User chooses which fields are stored and shared; uploading is voluntary.
3. Balancing test.
- Nature of the data: photos of plants, fungi, animals and other organisms are not special category data. The privacy risk is location, which can reveal a home or growing site.
- Reasonable expectations: Users upload photos to a breeding and identification service, so analysis is expected. Keeping item photos after an account is deleted is less expected and is stated in sections 3 and 10.
- Impact: low for image content; low to moderate for location, since only a rounded location leaves the owner's workspace.
- Safeguards: exact location stays private; rounded location outside; file metadata removed; per-field choice and defaults shown at upload; storage and backups encrypted; access controls; no sale of data and no third-party analytics; objection (Article 21) and erasure (Article 17) available at any time, including before deleting the account.
4. Conclusion. The Controller's interest, which also benefits Users, is not overridden by the interests or fundamental rights and freedoms of Users, provided that the safeguards above are in place. The retention of the exact location after account deletion is reassessed regularly.
6. Requirement to provide personal data #
Providing a name, an email address and a full birth date, as the minimum data required from every User, and the other data required to create a user account is a requirement for entering into the contract and creating a user account. If the User does not provide this data, the Controller cannot offer the User the functions of the Service that require a user account.
Providing a profile photo and an address is voluntary. Not providing them does not prevent use of the Service. Uploading gallery photos to the Service is voluntary.
7. Storage and place of processing of personal data #
The Service operates primarily locally (offline-first). The User's data is stored in a local SQLite database on the User's own device and is synchronised to a server maintained by the Controller itself.
For the time being, personal data is stored and processed within the European Union on the Controller's own server.
Emails sent by the Service may contain technical means that tell the email service provider whether and when an email was opened. The Controller does not use this information for advertising or analytics.
Cookies and browser storage #
The Service itself does not set any cookies. The Service uses the following browser and device storage, all of which is strictly necessary to provide the Service requested by the User or to remember settings chosen by the User. Under section 205 of the Finnish Act on Electronic Communications Services (917/2014), such storage does not require consent.
| Storage | Purpose | Duration | Strictly necessary |
|---|---|---|---|
Browser sessionStorage, key breedmap_tab_session | Keeps the User signed in when "Keep me signed in" is not selected | Survives a page reload; cleared when the browser tab is closed | Yes |
System keychain, key breedmap_session (or the app's own database on the device if no system keychain is available) | Keeps the User signed in when "Keep me signed in" is selected | Until the User signs out or the session expires | Yes |
Browser localStorage | Stores user interface preferences, such as tree panel width and visibility, folded sections and theme | Until the User clears the browser's site data | Yes (settings chosen by the User) |
Cloudflare security cookies, for example __cf_bm and cf_clearance | Set by Cloudflare to protect the Service against malicious and automated traffic | __cf_bm expires after 30 minutes of inactivity; cf_clearance according to Cloudflare's settings | Yes |
More information on Cloudflare's cookies: Cloudflare Cookies.
8. Recipients of personal data #
The Controller does not disclose personal data to third parties, except to the service providers and independent controllers named in this section: Google as an independent controller for the sign-in option, Google (Firebase Cloud Messaging) and Apple for delivering push notifications, Cloudflare, Inc. as a processor under Article 28 of the GDPR for DNS, edge delivery and bot blocking, Anthropic, PBC as a processor under Article 28 for the in-app AI helper, and an email service provider as a processor under Article 28 for sending service emails. Personal data may be disclosed to authorities only where required by applicable law.
Cloudflare, Inc. acts as a processor under Article 28 of the GDPR on behalf of the Controller. All network traffic to the Service passes through Cloudflare's network, and Cloudflare processes IP addresses, browser data and request data in order to relay network traffic and ensure the security of the Service. The processing is subject to Cloudflare's data processing agreement (Data Processing Addendum, DPA). Processing carried out by Cloudflare is subject to Cloudflare's own privacy policy.
Anthropic, PBC acts as a processor under Article 28 of the GDPR on behalf of the Controller for the in-app AI helper and for searching species by other names. When the User asks the helper a question, the question, the earlier messages of that chat and the name of the screen the User is on are sent to Anthropic together with public help text about the Service, to produce the answer. The helper has no access to the User's workspaces, items, photos or account data; they are sent to Anthropic only if the User types them into the question or, in a future feature, starts a feature that needs them. When a species search finds nothing, the search text may be sent to Anthropic to suggest other names. The User should not put sensitive data into the helper. The processing is subject to Anthropic's data processing addendum, which includes standard contractual clauses. Processing carried out by Anthropic is subject to Anthropic's own privacy policy.
Google. The User can sign in to the Service with their Google account using the OpenID Connect protocol. Google acts as an independent controller with respect to the sign-in. The Controller receives from Google the identifier required for sign-in, the email address and the name. Processing carried out by Google is subject to Google's own privacy policy.
Push notification services. To show a notification on your device the Controller sends it through Google's Firebase Cloud Messaging and, on Apple devices, Apple's push notification service. They receive your device token and the notification text, which is generic unless you choose to show the sender's name or a preview (see section 5, Messages). New sign-in notices always use a generic text (see section 5, "New sign-in notices"). Processing carried out by them is subject to their own privacy policies.
Email service provider. The Controller uses an email service provider to send emails from the Service. These emails are: sign-in codes; warnings before an unused account is deleted (30 days, 14 days and one day before); invitations and notices for child accounts, including the notice 30 days before a child account becomes a normal account; notices about link requests between items; and new sign-in notices and the confirmation sent after "This wasn't me". A new sign-in notice contains the place, IP address, device and time of the sign-in, so the email service provider processes these as part of the email content. The email service provider acts as a processor under Article 28 of the GDPR on behalf of the Controller. It processes the User's email address and the content of these emails only for sending them. A data processing agreement under Article 28 is concluded with it.
The Service does not use third-party analytics or error reporting services.
9. Transfers of personal data outside the EU or EEA #
For the time being, personal data is stored and processed within the European Union on the Controller's own server. The service providers Cloudflare, Inc., Anthropic, PBC and Google mentioned in section 8 are US companies, and personal data may be transferred outside the EU or EEA in the course of their processing. These service providers participate in the EU-U.S. Data Privacy Framework and/or use the European Commission's standard contractual clauses as safeguards for transfers (see footnote 1). Otherwise, the Controller does not transfer personal data outside the EU or EEA. If other transfers take place in the future, the Controller will ensure that the transfer is carried out in accordance with Chapter V of the GDPR and will update this policy before the transfers begin.¹
¹ If personal data is transferred outside the EU or EEA, the Controller ensures appropriate safeguards in accordance with Chapter V of the GDPR. In that case, the transfer is based on an adequacy decision of the European Commission (Article 45), including the EU-U.S. Data Privacy Framework insofar as the recipient is in the United States and certified under the framework, or on standard contractual clauses approved by the European Commission (Article 46(2)(c)), supplemented by additional safeguards where necessary. The Controller informs Users of transfers, and the User may request a copy of the applicable safeguards by email at [email protected].
10. Retention period of personal data #
Validity of the user account. The Controller retains personal data for as long as the User's user account is valid and the data is necessary for providing the Service.
Erasure request. When the User asks to delete the account, the Controller deletes without undue delay the personal data concerning the User: name, email address, birth date, address, profile photo, login data, sessions, sign-in notice data and follows. The workspace with the User's items, lineage, item photos and their metadata is not deleted. It remains without an owner and is shown as "owner no longer present". Items are never hard-deleted because of an erasure request, so that other Users' links to them keep working. The Controller removes from the workspace the details that directly identify the User: the account name is replaced with a randomly generated name. The legal basis for keeping the workspace is the Controller's legitimate interest (Article 6(1)(f)): the lineage and links of other Users depend on it, and a breeding record has value for other breeders. The data is about plants, fungi, animals and other non-human subjects. If a note, photo or other text still contains personal data, the person concerned can ask for it to be sanitised or removed, and the Controller does so case by case. Sanitising means that everything that identifies a person is removed or changed while the item itself stays: names are replaced, identifying text is removed, parts of pictures that show people are censored (blurred or masked, also with automated tools), and exact locations are rounded. Photos showing people are removed on request. Every request to sanitise or remove items, text or photos is assessed case by case, taking into account the rights of the person concerned and the lineage and links of other Users. Before deleting the account, the User can name a successor who answers link requests to the workspace (see section 10a). Guardian declarations of child accounts are kept for 12 months after the child account ends, to prove the consent given (Article 6(1)(f)).
Unused accounts. If an account has not been used for twelve (12) consecutive months, the Controller deletes the personal data in the way described under "Erasure request". The Controller emails the User three times before the deletion: 30 days before, 14 days before and the day before. The User can stop the deletion by signing in. This is consistent with the terms of service.
Gallery photos. When a User deletes the account, the profile photo and the personal data are deleted. Item photos and their metadata remain with the items in the workspace that stays after deletion (see "Erasure request"), detached from the User, on the basis of the Controller's legitimate interest (Article 6(1)(f)): the items and lineage must stay intact for the Users who have linked to them. The exact location of such photos remains stored and is not shown to any user; the Controller may use it internally for the purposes of the Service, such as species identification and data analysis, and for no other purpose. The User can ask for the exact location of their photos to be removed before or after deleting the account, and can object to this processing, by writing to [email protected]. On such a request the exact location is replaced with the rounded location of about 1 km, which is the location used elsewhere in the Service. Copies in backups are replaced when the backups expire. Photos themselves are removed on request where they show people. Metadata of profile photos is not stored.
Messages. A message is kept until a user deletes it. The sender can choose, when deleting a message, to delete it from the recipient's mailbox as well. The recipient cannot delete it from the sender's mailbox. A message in the "Other" mailbox is deleted automatically 12 months after it was received. When an account is deleted, its personal data is deleted as described under "Erasure request", and messages it sent remain visible to their recipients with the sender shown as "Former member". Support requests and replies are kept only as long as needed to answer and follow up. The Controller keeps a reported message, and the messages around it that were read for the report, only as long as needed to handle the report. Friends, contacts, blocks, messaging settings and the device token are deleted with the account. Deleted messages remain in older backups until those backups expire (see "Backups and deletion").
Logs. Sign-in logs, which contain the IP address of each sign-in, are kept for ninety (90) days and then deleted. Other database logs (access and purge logs) are kept for thirty (30) days and then deleted. Application and server logs are kept for one month. The email service provider keeps sending logs for about one month and then deletes them. It does not store previews of sent emails.
Sign-in notice data. The list of devices and countries already notified, and the record of each notice, are kept while the account exists and are deleted with the account (see "Erasure request" and "Unused accounts"). The IP address and city shown in a notice are not stored by the notice; they remain only in the sent email, in the User's mailbox and in the email service provider's sending logs.
Backups. The Controller makes regular encrypted backups of the Service. Backups are kept in a cycle of about 30 days and then deleted.
Backups and deletion. Personal data that has been deleted, or photos removed on request, remain in older backups until those backups expire, which happens within about 30 days. The Controller does not use backups for anything other than restoring the Service after a loss. If a backup is restored, the Controller deletes again the data that was deleted before the restore.
Locally stored data. Data stored on the User's device is under the User's control, and the User can delete it by deleting the application or its data from their device.
10a. Links between users' items #
A User can link their own item as a child of another User's item. This produces the following processing.
- Published item: the link needs no permission. The owner of the published item is notified of the link.
- Private item: the User asks the owner for permission by message. The owner has 30 days to answer. The owner chooses what the other User sees (by default name or code, taxon and dates, no photos, notes or field values). If the owner declines or does not answer, the private part of the lineage appears to others as one hidden step ("?") with a count of generations. Only the count is revealed.
- Owner no longer present: if the owner has deleted the account, the named successor answers the request. If there is no successor, the link is granted automatically, and the direct lineage is shown all the way up through the parents: the linked item and its ancestors, including private ones. Siblings, other branches and everything else in the workspace stay hidden.
- Purpose and basis: the Controller keeps and shows this lineage to find the cause of hidden mutations and inherited diseases in living organisms. The legal basis is legitimate interest (Article 6(1)(f)). The data concerns non-human subjects; the owner's personal data has been deleted, and only direct lineage is shown. A User who does not want this can name a successor before deleting the account, or ask the Controller to sanitise or remove specific items; each such request is assessed case by case, taking the lineage of other Users into account.
- Objection: the right to object (Article 21) applies. Contact: [email protected].
- Child accounts: a link request to an item of a child account is answered by the guardian, and the child sees it and can say no. A child account is never shown as linked to any person.
11. Rights of the data subject #
Under the GDPR, the User has the following rights:
- Right of access (Article 15): The User has the right to obtain confirmation as to whether personal data concerning them is being processed and to obtain a copy of the data being processed. A copy of messages is given as far as it does not adversely affect the rights and freedoms of others (Article 15(4)).
- Right to rectification (Article 16): The User has the right to have inaccurate or incorrect data rectified and incomplete data completed.
- Right to erasure (Article 17): The User has the right to have personal data concerning them erased.
- Right to restriction of processing (Article 18): The User has the right to obtain restriction of processing under the conditions laid down in Article 18.
- Right to data portability (Article 20): The User has the right to receive the personal data they have provided in a structured, commonly used and machine-readable format and the right to transmit it to another controller.
- Right to object (Article 21): The User has the right to object to the processing of their personal data insofar as the processing is based on legitimate interest or public interest. The right to object also applies to the aggregated breeding analytics described in section 5. If the User objects to the processing, the Controller will no longer process the User's personal data for this purpose unless the Controller demonstrates compelling legitimate grounds for the processing which override the User's interests, rights and freedoms. The right to object can be exercised by notifying it by email to [email protected].
- Right to withdraw consent (Article 7(3)): The User has the right to withdraw their consent at any time.
- Right to lodge a complaint with a supervisory authority (Article 77): The User has the right to lodge a complaint with a supervisory authority if they consider that the processing of personal data concerning them infringes the GDPR. In Finland, the supervisory authority is the Office of the Data Protection Ombudsman (www.tietosuoja.fi).
Exercising rights. Requests shall be sent by email to [email protected]. The Controller may ask the User to confirm their identity before handling the request, and the Controller verifies the identity of the person making the request using the Service's own sign-in methods. The Controller responds to the request without undue delay and at the latest within one (1) month of receipt of the request. The deadline may be extended by a maximum of two (2) further months where necessary, taking into account the complexity and number of the requests, in which case the Controller informs the User of the extension and the reasons for it within one month of receipt of the request (Article 12(3) of the GDPR).
12. Automated decision-making and profiling #
The Controller does not make decisions based solely on automated processing referred to in Article 22 of the GDPR that would produce legal effects concerning the User or similarly significantly affect the User, and does not profile Users.
13. Minors #
Under section 5 of the Finnish Data Protection Act (1050/2018), a minor's consent to information society services is valid from the age of 13. The Controller sets a stricter minimum for its own Service: a User must be at least 15 to create an account. This is a rule of the Service, not a requirement of law.
Minimum age at sign-up. Everyone who signs up enters their full birth date. If the birth date shows that the person is under 15, the sign-up is refused. No account, session or consent record is created and the birth date is not stored. The email address is used only to send the sign-in code, which is covered by the log periods in section 10. The birth date of an account that is created is stored until the account is deleted, is never shown to other users, and is deleted with the account (see section 10).
Child accounts. A person under 15 can have a child account only through a guardian who is at least 18 and has their own account. The guardian declares that they are the child's guardian. The declaration is recorded (guardian, child, time and version of the text) and kept for as long as the child account exists and 12 months after. A child can have up to two guardians, and each can answer requests and approve publishing.
What the child account can do. A child account cannot send or receive messages, has no comments or public profile, and cannot publish without the guardian's permission. A guardian can read everything in the child account and approve publishing, but cannot change or delete the child's items without the child's permission. A published item of a child account shows the label "Child account". A child account is not shown as linked to any person, including its guardians. The only way to contact the child account's side is the message button, which delivers the message to the guardian as an ordinary message (the child account itself never receives one) without showing who the guardian is or their email address.
Legal basis. Processing for a child account is based on the guardian's consent (Article 6(1)(a)) and on the contract with the guardian (Article 6(1)(b)). Article 8 of the GDPR requires guardian consent for children under 13; for children aged 13 and 14 the Controller requires it under its own rules.
Rights. The guardian exercises the child's rights described in section 11 until the child turns 15. The child can see requests that concern their account.
At 15. The account becomes a normal account after a notice 30 days before. The child can choose to stay under the Premium Family licence. The guardian then loses access.
If the guardian's account is deleted. A child aged 15 or over gets a normal account. For a child under 15 the account is frozen. Taking over a frozen account requires contacting [email protected] and a strict identification process.
Accounts made against the rules. If the Controller finds an account of a person under 15 that was not created through a guardian, it deletes the account and the related personal data.
14. Security #
The Controller implements appropriate technical and organisational measures under Article 32 of the GDPR to protect personal data against unauthorised access, processing, alteration, disclosure and destruction. The measures include, among other things:
- Encryption at rest: the server's disk is encrypted, the database is stored on a separately encrypted volume (LUKS2), and photos are stored on the encrypted volume.
- Encrypted backups: backups are encrypted, including backups of messages.
- Messages: messages are encrypted at rest and kept in their own database schema with its own database login and table permissions. They are not end-to-end encrypted. Staff have access only to reported messages and a few messages around them, and, for administrators and owners, to support requests. Moderators cannot see support requests or other user data. Staff use a separate login with a second step, and every staff action is written to an audit log that cannot be changed.
- Encryption in transit: connections to the Service use HTTPS at Cloudflare's network edge, and traffic between Cloudflare and the server travels through an encrypted tunnel.
- Sign-in security: passwords are stored only as hashes using the Argon2 algorithm, two-factor sign-in is available, refresh tokens are stored only as hashes, and access tokens are short-lived.
- Access control: each user account's data is kept in its own database schema, access is governed by role-based permissions, and access to the server is restricted to persons authorised by the Controller only.
- No third-party analytics: the Service does not use third-party analytics or crash reporting services.
The security of the User's own device is the User's responsibility: data stored locally by the app (in a local SQLite database, which the Service does not encrypt) and the sign-in session held in the device's keychain are protected by the device's own security settings.
15. Personal data breaches #
If a personal data breach affects personal data processed by the Controller, the Controller notifies the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk to the rights and freedoms of natural persons (Article 33 of the GDPR).
If the personal data breach is likely to result in a high risk to the User's rights and freedoms, the Controller also notifies the User of the breach without undue delay (Article 34 of the GDPR).
16. Record of processing activities #
The Controller maintains a record of processing activities under its responsibility in accordance with Article 30 of the GDPR.
17. Changes to this privacy policy #
The Controller may update this privacy policy, among other things, when legislation, the Service or the Controller's identification details change. The current version is always available at https://breedmap.com/legal, a page that lists all of the Service's legal documents. The Controller notifies Users of material changes in the Service or by email.