- Controller
- Gabriela Cipro
- Company ID
- 21134154
- Registered address
- V Jezerech 311, Braškov 273 51, Czech Republic
- E-mail
- hello@mybloomia.com
- Data protection officer
- none appointed, see article 2
- In force from
- 14 November 2026
This is a translation provided for your convenience. The legally binding
version is the Czech original at
zásady ochrany osobních údajů.
If the two differ, the Czech wording applies.
The main thing, in one sentence
Everything you write into BlooMia stays stored on your own device. It is
not sent to a server and the controller has no access to it.
You sign in to your subscription with the e-mail you gave when paying
and a password you set yourself. Signing in opens the subscription only,
and none of your records are sent anywhere when you do (article
6). The app shows no
advertising and uses no third-party measurement or advertising tools.
Statistics on which parts of the app are used are collected only if you
give your explicit consent, and only as totals without your name (article
9).
The rest of this document explains what follows from that, and describes
the situations where some data is processed after all: when you write to
us yourself, when you take out a subscription and sign in to it, when
you consent to the statistics, and when you simply open the website.
Who the controller is
The controller of personal data is Gabriela Cipro,
company ID 21134154, registered at V Jezerech 311, Braškov 273 51, Czech
Republic, e-mail
hello@mybloomia.com.
Processing is governed by Regulation (EU) 2016/679 (GDPR) and by Czech Act
No. 110/2019 Coll., on personal data processing.
No data protection officer has been appointed. The
obligation under Article 37(1) GDPR does not arise: the controller is not
a public authority, and her core activity does not consist of large-scale
regular and systematic monitoring, nor of large-scale processing of
special categories of data. The controller does not process your
treatment records at all; they stay on your device. The usage statistics
described in article 9 are collected only with consent,
only as totals and on a small scale.
What you record in the app
In the app you can record, for example, your name or a nickname, the stage
of your treatment, cycles, retrievals, embryos, transfers, medication, lab
values, mood, diary entries, costs, documents and photographs.
This data is stored using your browser's own storage,
directly on your device:
| Where | What is there |
| Browser storage (localStorage) | profile, cycles, transfers, medication, values, diary, costs and other records |
| Browser database (IndexedDB) | photographs you add to the app |
The controller does not collect, transmit or see this data. It is not
subject to processing on her side unless you send it yourself in one of
the ways described below.
Health data
Data about fertility treatment falls within the special categories of
personal data under Article 9 GDPR. That is precisely why the app is built
so that this data never leaves your device.
If you send such data to us yourself, for example in the text of your
feedback, it is processed on the basis of your explicit
consent under Article 9(2)(a) GDPR, and solely for the purpose of
dealing with your message.
Please do not write sensitive health details into the feedback form unless
they are necessary to answer your question.
The same applies to usage statistics. The screens you open in the app can
in themselves show that you are going through treatment. The statistics
are therefore collected only on the basis of your explicit consent and
only in the way described in article 9.
Feedback and contact
If you use the feedback form in the app, only the following is sent:
- the topic you chose,
- your name, if you fill it in (optional),
- your e-mail address in the text of the message, only
if you tick the box saying you would like a reply. Because you send the
message from your own e-mail program, the controller always sees the
address it came from,
- the star rating, if you give one,
- the date it was sent,
- the text you write yourself.
Diary entries, cycles, lab values and photographs are never sent through
the form.
How the message leaves. When no forwarding service is set
up, the app only opens your own e-mail program with the message
pre-filled, and you send it yourself. In that case the controller uses no
technical service at all and the message goes straight from your mailbox.
No forwarding service is set up. The message therefore
goes straight from your mailbox and the controller uses no processor for
it. Should that ever change, the name and registered address of the
processor will be added here, and this policy will be updated before the
service is switched on.
Purpose and legal basis. Dealing with your message, that
is performance of a contract or the legitimate interest in communicating
with users (Article 6(1)(b) or (f) GDPR), and for sensitive data the
explicit consent described in article 4.
Subscription and payment
If you take out a subscription, the data necessary to conclude and perform
the contract and to meet legal obligations, in particular tax and
accounting ones, is processed.
| Data | Purpose | Legal basis |
| name and e-mail | concluding the contract, order confirmation, receipt, communication | performance of a contract |
| billing details | issuing the receipt | legal obligation |
| payment data (amount, date, payment method, subscription status) | processing the payment, keeping subscription records | performance of a contract |
| phone (optional) | contact about the subscription when e-mail does not reach you | legitimate interest |
| the day you last opened the app | knowing whether the subscription is being used, customer support, protection of legal claims | legitimate interest |
| the password to your subscription, stored only as a hash | signing in to the subscription on another device | performance of the contract |
| the number of failed sign-in attempts and the time of the first one | protecting the account against password guessing | legitimate interest |
| the code for setting a password sent by e-mail, stored only as a hash, and the times codes were sent | restoring access to the subscription, protecting your inbox from being flooded | performance of the contract |
| consent to the content being made available before the withdrawal period ends, and when it was given, only for subscriptions concluded on 13 and 14 November 2026 | a record of what you confirmed when paying | legitimate interest (protection of legal claims) |
| a statement cancelling the subscription or withdrawing from the contract (name, e-mail, type and time of the statement) | handling the statement and confirming its receipt | legal obligation, performance of the contract |
You do not have to give a phone number. The app works exactly the same
without it. The name is taken from the payment: it is the name you give
with your card, or the one passed on by Apple Pay or Google Pay.
Subscription records. Data about customers and their
subscriptions is stored with the payment service provider Stripe. The
controller keeps no separate customer database alongside it. She accesses
the data through her Stripe account and through her own
password-protected administration, which only reads it from Stripe and
displays it: who has a subscription, since when, until when access lasts,
when the last payment was made and whether the subscription has been
cancelled.
The day you last opened the app. When the app opens, it
checks with the server whether your subscription is still running. On
that occasion today's date is noted against your subscription, at most
once a day. Only the date is noted: no time, no details of your device
and nothing about what you do in the app. This lets the controller see
whether a subscription is being used, get in touch if you are paying and
the app may not be working for you, and have something to rely on when
dealing with complaints and disputes. From the number of these notes a
daily figure is also kept of how many subscribers opened the app. That is
only a total with no link to any particular person.
The legal basis is the controller's legitimate interest under Article
6(1)(f) GDPR. You may object to this processing at any time (article
13). The controller will then switch the note off for
your subscription and delete the date recorded so far. This has no effect
on how the app works.
For subscriptions taken out before 14 November 2026, the day of last
opening will start being noted only from 15 December 2026.
Signing in to the subscription. Your account is your
customer record with the payment service provider, which is created by
the payment. No other database of accounts is kept. When you set a
password in the app, its hash is stored with that record, that is the
result of a one-way calculation from which the password cannot be read
back. The password itself is not stored and the controller does not
know it. When you sign in, the app sends your e-mail and password to the
server over an encrypted connection. The server compares the password
with the hash and does not write it anywhere. Setting a password is
voluntary.
The customer record also holds the number of failed sign-in attempts and
the time of the first one. After eight failed attempts sign-in is closed
for 15 minutes so that the password cannot be guessed. A successful
sign-in clears the number. During sign-in the server also briefly counts
attempts from one network address, only in its memory and without
storing them.
Signing in stores only the technical key of the subscription on the
device (article 8). Your records from the app are
neither sent nor downloaded when you do: the controller does not have
them.
If you forget your password or want to set one for the first time, the
app sends an eight-digit code to the e-mail stored with your
subscription. Only its hash, its validity (15 minutes), the number of
attempts and the times codes were sent in the last 24 hours are stored
with your customer record. This prevents your inbox from being flooded.
Only exceptionally, when e-mail does not help, can the controller set a
one-time code for you by hand at your request. It is valid for 14 days at
most and ceases to exist with the first sign-in.
E-mails from the controller. Only messages concerning
your contract are sent to the e-mail you paid with: the order
confirmation with the terms and conditions and this policy attached,
confirmation of cancellation or withdrawal, the code for setting a
password and a notice when the password changes. They are not commercial
communications. They are sent by the e-mail service provider
Mailjet SAS, Paris, France, which processes the data in
the European Union. Open and click tracking is switched off for these
e-mails.
Consent before payment. The app asked for it only on 13
and 14 November 2026. For subscriptions from those days, Stripe stores
that you gave it, the wording and the time, and it is kept for as long as
the subscription data. Today nothing is ticked before payment and the
right of withdrawal stays with you for the full 14 days.
Cancelling and withdrawing on the website. The form at
mybloomia.com/en/cancel sends the type of
statement, your e-mail and your name if you fill it in. Your subscription
is looked up by the e-mail and set not to renew. A confirmation with the
content of the statement and the time it was received goes to the e-mail
you entered, and a copy to the controller.
The controller neither processes nor stores your card details. Payment is
handled by the payment service provider Stripe Payments Europe,
Limited, registered at 1 Grand Canal Street Lower, Grand Canal
Dock, Dublin, D02 H210, Ireland, under its own policy, which you can find
at
stripe.com/privacy.
You enter your card number directly with them, on their page, and the
controller never sees it.
Running the site and hosting
Both the website and the app run with the hosting provider
Vercel Inc., registered in the United States of America.
It may briefly process technical data in its operational logs, for example
the IP address, the browser type and the time of access. This serves to
keep the service running and secure (legitimate interest under Article
6(1)(f) GDPR).
The hosting provider keeps operational logs for a short time under its own
policy, which you can read at
vercel.com/legal/privacy-policy.
This is a provider outside the European Economic Area. Vercel Inc. is
certified under the EU-U.S. Data Privacy Framework, which is covered by a
European Commission adequacy decision. In addition, the transfer is
governed by the standard contractual clauses under Article 46 GDPR that
form part of the data processing agreement.
Cookies and similar technologies
BlooMia uses no cookies for traffic measurement, profiling or
advertising. No marketing tools and no third-party measurement tools are
in place.
The app uses the browser's technical storage, that is
localStorage and IndexedDB. That is not a cookie and does not serve to
track you. Without it the app could not work, because that is exactly
where your records are kept. It stays on your device and is never sent
anywhere.
The same storage holds the technical key that unlocks the app's content
after payment or after signing in, and your decision about usage
statistics (consent or refusal), so that the app does not ask you every
time it opens. For the same reason it remembers that you put off the
offer to set a password. The password itself is not kept in the storage.
The app can be added to your phone's home screen. So that it works without
a connection, your browser caches its files. None of your records are in
that cache.
Usage statistics are described in article 9. The app
collects them itself, without third-party tools, and only with your
consent.
Usage statistics
To show which parts of the app help and which need improving, the app can
count what is used in it. It does so only if you give your
explicit consent. The app asks for it itself, and without it
nothing is counted and nothing is sent.
| What is counted | How |
| launches of the app | number per day |
| screens, articles, glossary terms and exercises opened | how many times each item was opened, as a weekly total |
| features and buttons used | how many times each feature was used, as a weekly total; only the name of the feature, never what you entered into it |
| the screen on which the app reported an error | number per week, without the text of the error |
| stage of the journey, language, type of device (phone, tablet, computer), whether the app is added to the home screen, light or dark appearance and how long you have been sending statistics | once a week per device |
Nothing you have written is ever counted or sent: no diary text, no date,
value, medication, photograph or name. No device identifier that could
link one batch to another is sent either, and the totals are not linked
to your subscription, name or e-mail.
How it works. The app keeps the totals in memory for a
while and then sends them to the server as one batch. The server adds
them to the totals of the others and does not keep the batch itself. The
batch travels over the internet like any other request, that is from your
IP address; the address is not stored with the totals. The storage
therefore holds only figures such as "this week the Diary screen was
opened 42 times".
Protection when few women use the app. When only a few
women use the app, the totals could by guesswork be attributed to a
particular one of them. The detailed totals for a week are therefore
shown to the controller only once at least five devices have sent them
that week. A week that does not reach this threshold is not shown at all
and is deleted from the storage automatically within ten days.
Why explicit consent. The screens you open and the stage
of the journey you are at can show that you are going through fertility
treatment. This is data concerning health under Article 9 GDPR. The legal
basis is therefore your explicit consent under Article 6(1)(a) and
Article 9(2)(a) GDPR. The same consent covers reading data from your
device under Section 89(3) of Czech Act No. 127/2005 Coll., on electronic
communications.
Consent is voluntary. The app works exactly the same
without it and refusing has no consequences for you. You can withdraw
your consent at any time directly in the app, in Settings under Usage
statistics, with a single tap. From that moment the app counts and sends
nothing further.
What about totals already sent. The totals are not linked
to you or to your device, so the controller cannot find, correct or
delete your share in them (Article 11 GDPR). Withdrawing consent
therefore takes effect for the future.
Who sees the totals and where they are kept. Only the
controller sees them, in her password-protected administration. They are
stored with the database service provider Upstash,
Inc., United States of America, in a data centre in the European
Union. They are not passed on to anyone else and are not used for
advertising or profiling.
How long. The totals are kept for at most 400 days and
are then deleted automatically.
Backups and moving to another device
The app can save all your data into a backup file. That file is created on
your device and is under your control.
The backup contains everything you have written, photographs included, and
it is not encrypted. Keep it somewhere safe and think about where you
share it. Folders such as Downloads are often synchronised to the cloud
automatically.
The backup also contains the technical key of the subscription, so the
app unlocks once you load it on another device. The password to your
subscription is not in the backup.
The controller has no access to backups and does not keep them.
Who the data is shared with
Data is not shared for marketing purposes and is not sold. The set of
recipients is limited to what the service could not run without:
- the hosting provider Vercel Inc., United States of
America, see article 7,
- the payment service provider Stripe Payments Europe,
Limited, Ireland: subscription and payment data including the
hash of the password to your subscription, see article
6,
- the e-mail service provider Mailjet SAS, France:
your e-mail address and the content of e-mails concerning your contract,
see article 6,
- the database service provider Upstash, Inc., United
States of America: only the totals of usage statistics and the daily
numbers of subscribers who opened the app, see article
9,
- public authorities, where the law requires it.
By contrast, data is not shared:
- with a forwarding service for the feedback form, because none is set
up and the message goes straight from your own mailbox,
- with anyone for marketing purposes.
Data may be transferred outside the European Economic Area in connection
with hosting (article 7) and with storing the
statistics totals (article 9). Both providers are based
in the United States of America. For Vercel Inc. the transfer relies on
the European Commission adequacy decision for the EU-U.S. Data Privacy
Framework and, in addition, on standard contractual clauses; for
Upstash, Inc. on standard contractual clauses under Article 46 GDPR. The
e-mail service provider processes data in the European Union. None of
your records from the app are transferred anywhere, because they are
never sent at all.
How long the data is kept
| Data | Period |
| records in the app | on your device, until you delete them yourself |
| a feedback message | until it is dealt with, and one year after that |
| contact details for the subscription (name, e-mail, phone) and the day you last opened the app | for the duration of the subscription and three years after it ends |
| the hash of the password to your subscription and the number of failed sign-in attempts | until you change the password or ask for it to be erased, at most for as long as the contact details for the subscription are kept |
| the code for setting a password sent by e-mail | until used, at most 15 minutes; times codes were sent at most 24 hours |
| a one-time code set by hand | until the first sign-in, at most 14 days |
| consent to the content being made available and statements of cancellation or withdrawal | for the duration of the subscription and three years after it ends |
| records of sent e-mails at the e-mail service provider | for a short time, according to the provider's policy |
| tax and accounting documents | for the period required by law |
| usage statistics totals | at most 400 days; a week sent by fewer than five devices at most 10 days |
| your decision about usage statistics | on your device, until you change it or delete the app's data |
| hosting operational logs | briefly, under the hosting provider's policy |
Your rights
In relation to data the controller processes, you have the right:
- of access to the data and to a copy of it,
- to rectification of inaccurate data,
- to erasure,
- to restriction of processing,
- to data portability,
- to object to processing based on legitimate interest,
- to withdraw consent at any time where processing is based on consent,
without affecting the lawfulness of processing carried out so far,
- to lodge a complaint with the Czech Office for Personal Data
Protection, Pplk. Sochora 27, 170 00 Prague 7,
www.uoou.cz,
or with the supervisory authority in your own country.
An objection to the noting of the day you last opened the app (article
6) can simply be sent by e-mail. Consent to usage
statistics is withdrawn directly in the app (article
9). You change the password to your subscription
yourself in the app, in the Subscription section. You can ask by e-mail
for its hash to be erased. The subscription then keeps working on the
devices where the app is already unlocked.
For records stored on your device you exercise these rights directly: the
data is with you, you can correct it, export it to a backup or delete it
at any time, without having to ask anyone.
Complete erasure also means clearing your browser data for this site,
because deleting content inside the app may not remove every technical
record from your device's storage.
How to exercise your rights
Write to hello@mybloomia.com.
You will get a reply without undue delay, at the latest within one month
of the request arriving.
Because records from the app are not sent anywhere, your identity cannot
be verified from them. For requests concerning data held by the
controller, you may need to show that the data really is yours, for
example by writing from the e-mail address you gave when paying.
Changes to this policy
This policy may be amended, in particular when the technical solution or
the law changes. The current wording is always available at this address.
You will be told about substantial changes by a message in the app, and if
the controller has your e-mail, by e-mail as well.
The amendment in force from 14 November 2026 added subscription records,
the day you last opened the app, signing in to the subscription with a
password including resetting it by e-mail, e-mails from the controller,
consent before payment and the form for cancelling and withdrawing
(article 6), usage statistics based on
consent (article 9) and a new recipient of data
(article 11). For subscriptions taken out before that
day, the day of last opening will start being noted only from
15 December 2026. Sign-in data is processed only for those who set a
password, and from the moment they do so. The controller will send the
previous wording on request.
In force from 14 November 2026.