Frequently asked questions

Breedmap is a breeding and strain tracking app, for plants and mushrooms first. Growers and strain trackers use it to record lineages (parents, children and generations), keep photos, care logs and QR labels for each item, and publish strains to a public registry.

It is one app for Android, iPhone, Linux and the browser.

Breedmap is in development. According to the draft Terms of Service, the service is first offered as a free beta, and access to the beta and to publishing during the beta is by invitation only. Data in the beta may be reset, migrated or deleted.

To ask about taking part, see the contact page.

Source: Terms of Service draft, section 5

Anyone who breeds or grows plants and mushrooms and wants to keep a clear record of lines and generations: individual growers with a Personal account, and groups or organizations with an Organization account.

A project holds a set of items, for example one species or line, together with the fields you want to record for them (numbers, dates, text and so on). An item is one plant, culture or other individual. Each item gets a short visible code such as K7M2QX, made from an alphabet without 0/O and 1/I so it is easy to read from a label.

You link items as parents and children. The lineage view draws the pedigree: parents and earlier generations above, the item in the middle and children below, with generation badges (G1, G2…) and status dots. Tap a relative to put it in the middle. A parent you are not allowed to see is shown as “?”.

• Gallery: photos, videos and documents (photos up to 10 MB, videos up to 30 MB, documents up to 20 MB, 50 files per item).
• Care log: watering, feeding, pruning, repotting and treatment entries, plus your own log types. Entries are not edited: a mistake is removed and logged again.
• QR label: a large QR code with the item’s short code. Scanning it on a phone opens the item, or its public page for people outside your account.

Yes. In the browser and the desktop app, on screens at least 900 px wide, a project’s items are shown as a grid of cards and an item opens in a side panel or a pop-up next to the grid. On a phone an item opens full screen.

Yes. Breedmap is offline first: your data is stored in a local SQLite database on your device and the screens read from there. You can add items, edit values, add gallery files and care log entries offline; they wait on the device until the next sync.

Some actions need a connection, for example publishing, changing photo captions and covers, and adding or removing the demo project.

When you sync, the app first sends your queued changes and uploads, then downloads what changed on the server since the last sync. The first sync downloads everything. Sync can be automatic or manual.

If someone changed the same field in the meantime, you get a compare screen with your value and the server’s value and choose which to keep. An item can also be checked out: while someone has it checked out on one device, it is read-only elsewhere and shows which device has it.

In the browser the local database lives in the browser’s storage (IndexedDB). Photos and files waiting to be uploaded are kept in memory and are lost if the page is closed before syncing. The QR scanner is phone-only.

Publishing works online. A released item can be published by a person with the publish permission. Publishing always opens a preview first: name, project, generation, revision, strain, modification flag, parents (hidden ones as “?”), the values, how many photos go public and a note from the server. A modified item needs a compliance checkbox.

The result is either Published or Sent for approval: a publish request from an editor waits for an owner or admin to approve it.

Yes. Retract hides the public page after a confirmation.

Note from the draft Terms: other users may link their items to your published content as parents, offspring or relatives, and if you unpublish or delete it, Breedmap may keep the lineage relationship as a placeholder record.

Source: Terms of Service draft, section 9.6

According to the draft Terms, content is private by default and publishing is your choice. Published content is visible to anyone, including people without an account, and may be indexed by search engines.

According to the draft Privacy Policy, what a public page shows follows the sharing ticks of each field, which you can change at any time, and locations shown outside your own workspace are rounded to about 1 km.

Source: Terms 9.4 · Privacy Policy section 3

There is no separate sign-up form: an emailed 6-digit code signs you in and also creates your login the first time. A new login asks for your name. You can also sign in with a password, which always has a second step (an authenticator app or an emailed code).

Every account is Personal (the default) or Organization, chosen when the account is created. Settings › Account lists your accounts with their type and your role. Only the account’s creator can change its type; changing an Organization to Personal warns that the creator’s name becomes public.

While you work in an account, the header shows its name and type, so you always know where you are.

Yes. After signing in you pick an account or create one. A device holds one account at a time: switching syncs first and then downloads the other account, so one account’s data never shows under another.

The two drafts currently differ. The draft Privacy Policy (v2.0, 17 October 2026) says you must be at least 15 to have your own account, and younger children can have a child account created by a guardian aged 18 or over. The draft Terms of Service (v2.0, 14 October 2026) says 13. The final documents will settle this.

Account permissions decide who may change a project’s structure (create projects, add or edit fields), create items, check out, release, publish, break locks and purge old versions. Tools you may not use are hidden; the server always makes the final decision. Within a shared account the administrator controls membership, roles and access.

Source: Terms 4.5

Yes. When you open an item online, the server tells the app which fields you may write; the others are read-only. If you may write none, editing tools are hidden for that item.

From the draft Terms of Service:

• You keep ownership of your content.
• You grant Breedmap a broad licence to use your content (worldwide, non-exclusive, royalty-free, perpetual, irrevocable, transferable and sublicensable), including for operating, developing, improving and promoting the service. This licence survives deletion of content and of your account.
• For published content, unless you choose a different licence offered in the service, other people get a non-exclusive licence to view it within the service, and no other rights.
• Plans: the service has a Free plan and Premium plans (Single User licences, Multi User licences and Token pools), all with limits shown in the service.

Source: Terms sections 6 and 9

The Terms of Service are the agreement between you and Breedmap. According to the draft, you accept them by creating an account or using the service. They are provided in English only, and the English version is the binding one. The Privacy Policy and the price list form part of the Terms.

Current draft: version 2.0 (draft), last updated 14 October 2026. Full draft text: terms-of-service.md (not yet publicly accessible).

The draft Terms say Breedmap may process data for operating and developing the service, research, statistics, publication and commercial purposes, including by automated means and artificial intelligence, and that this is a condition of using the service.

On a request to delete your account, Breedmap deletes personal data that relates strictly to you as a person (such as your name, email address and login data). Other data, including content, lineage data, item records and photos, is kept.

Source: Terms 10

Yes. The draft says data loss may occur, you are responsible for keeping your own backups of your content, and Breedmap has no obligation to store or back up content. Export functions, where offered, come without guarantees.

Source: Terms 9.8 and 11

In short, from the draft acceptable use rules: breaking the law (including rules on controlled substances, protected species, plant health, biosecurity and CITES), unlawful or abusive content, other people’s personal data without a lawful basis, revealing locations of protected or valuable organisms in a harmful way, offering or trading organisms or products (Breedmap has no marketplace), impersonation, malware, scraping or bulk downloading outside permitted interfaces, and getting around limits or security. Items about regulated species or substances get the tag “Regulated”.

Source: Terms 12.2 and 13

Report content you consider illegal or infringing by email to [email protected]; this is also the single point of contact under the EU Digital Services Act. A notice should include the exact location (URL) of the content, why it is illegal or infringing, your name and email address, and a good-faith statement.

If Breedmap removes or restricts your content or account, you can object by email within six months of the decision, giving your reasons.

Source: Terms 14 and 15

According to the draft, Premium plans will be sold through a third-party reseller (“Merchant of Record”) once paid plans are available. Monthly licences renew until cancelled; licences and Tokens are generally non-refundable once supply has begun, and Tokens expire 365 days after purchase. Refund requests go to [email protected]. During the beta, Premium switches and price lists are previews, not offers.

Source: Terms 5.4, 7 and 8

Except where applicable law provides otherwise, the laws of Finland and applicable EU law, and the courts of Finland.

Source: Terms 25

The controller is Breedmap, email [email protected]. At the time of the draft, Breedmap has not yet been registered as a company and has no Business ID; the details will be added once it is registered. No data protection officer has been appointed, as the GDPR conditions for one are not met.

Current draft: version 2.0 (draft), 17 October 2026. Full draft text: privacy-policy.en.md (not yet publicly accessible).

• Account data (username, sign-in data; passwords are stored only as hashes) and your email address.
• Your name, required at registration and shown to others only if you choose to share it.
• Your full birth date, never shown to other users (for child accounts, also the guardian declaration).
• Profile photo and address, only if you add them.
• Your breeding and cultivation data, and gallery photos with their metadata (time, location, device), where you choose which metadata fields are kept.
• Technical data: IP address, browser and device data, and a country code derived from Cloudflare headers.

Source: Privacy Policy section 3

On your own device, and on Breedmap’s own server in the EU. Cloudflare relays the service’s traffic, Google receives data if you sign in with Google, and an email service provider sends the service emails. Breedmap does not use advertising or third-party analytics and does not sell your data.

Cloudflare and Google are US companies, so data may be transferred outside the EU/EEA in their processing, with safeguards such as the EU-U.S. Data Privacy Framework or standard contractual clauses.

Source: Privacy Policy sections 7–9

The exact location of a photo stays private in your own workspace. Anything shown to others uses a rounded location of about 1 km. Metadata is removed from the stored image file; profile photos are re-encoded and their metadata is not stored. Uploaded photos may be scanned automatically, including with artificial intelligence, for the purposes of the service (for example species identification and content checks).

Source: Privacy Policy sections 3, 5 and 10

According to the draft, the service itself sets no cookies. It uses only storage that is needed: sessionStorage or the system keychain to keep you signed in, and localStorage for interface preferences such as the theme. Cloudflare sets security cookies (for example __cf_bm and cf_clearance) to protect the service.

This website stores only your theme choice in your browser’s localStorage.

Source: Privacy Policy section 7

There is a separate Finnish privacy notice draft, tietosuojaseloste (updated 16 October 2026). It is an earlier draft with placeholder details and differs from the English v2.0 in places (for example retention periods). The answers on this page follow the English v2.0 draft.

Under the GDPR you have the right to:

• access your data and get a copy of it,
• have inaccurate data corrected,
• have your data erased,
• restrict processing,
• receive your data in a machine-readable format and transfer it (data portability),
• object to processing based on legitimate interest, including the aggregated breeding analytics,
• withdraw consent at any time, where processing is based on consent,
• lodge a complaint with a supervisory authority; in Finland, the Office of the Data Protection Ombudsman (tietosuoja.fi).

Source: Privacy Policy section 11

Email [email protected]. Breedmap may confirm your identity using the service’s own sign-in methods, and answers without undue delay and within one month at the latest. For complex or numerous requests this can be extended by up to two more months, and you will be told why.

Source: Privacy Policy section 11

Your personal data is deleted: name, email address, birth date, address, profile photo, login data, sessions and follows. Your items, their lineage and their photos stay in a workspace without an owner, shown as “owner no longer present”, so that other users’ links do not break; the account name is replaced with a random one. You can ask for specific photos or text to be removed or sanitised; photos showing people are removed on request. Before deleting, you can name a successor who answers link requests to the workspace.

Source: Privacy Policy section 10

If an account is not used for 12 months, the personal data is deleted in the same way. You get an email 30 days, 14 days and one day before, and signing in stops the deletion.

Source: Privacy Policy section 10

• Database logs (sign-ins, access and purge logs): 30 days.
• Application and server logs: one month.
• Email sending logs at the email service provider: 30 days.
• Backups: encrypted, every night. During the beta they are kept for the whole beta and deleted 30 days after the public launch; after the launch, backups are kept for 30 days. Deleted data remains in older backups until they expire.

Source: Privacy Policy section 10

Once enough data has accumulated, Breedmap intends to analyse breeding lines and breeding efficiency from all users’ data in anonymised or aggregated form, so that no individual user can be identified from the results. You can object to this. There is no automated decision-making or profiling with legal or similarly significant effects.

Source: Privacy Policy sections 5 and 12

Under the draft Privacy Policy, a person under 15 can only have a child account created by a guardian (aged 18 or over) from the guardian’s own account. The guardian can read the child account and decides about publishing, and exercises the child’s data protection rights until the child turns 15. At 15 the account becomes a normal account after a notice 30 days before. (The draft Terms currently say 13; see minimum age.)

Source: Privacy Policy section 13

The draft lists encrypted server disks and database volume, encrypted backups, HTTPS with an encrypted tunnel to the server, Argon2 password hashes, two-factor sign-in, short-lived access tokens, a separate database schema per account and role-based access. The local database on your device is not encrypted by the app; it is protected by your device’s own security settings.

Source: Privacy Policy section 14