Privacy policy

The controller of your personal data is RONORDICA DEVELOPMENT AGENCY SRL (tax ID 36061653, Trade Register J40/6724/2016), registered at Str. Glodeni nr. 12, C3, Sector 2, București, România. For anything about your data, write to [email protected].

Your account

Email address and name. With a password, we keep only a hash of it; with Google, we get your name, email, profile picture and Google account ID. We also keep the site's language when you signed up and your account's tier. Needed to run your account (contract). To keep one account per inbox, we also keep your address in its plain form (for Gmail, without dots and anything after “+”), and we check that its domain can receive email and isn't a throwaway inbox service (our legitimate interest in preventing abuse). When an account is made, we also keep, for 30 days, a scrambled (keyed hash) form of the connection's address and of the browser's fmm-device ID, never the values themselves, to notice many accounts made from one place.

Signed-in sessions

While you're signed in, a session with your IP address and browser (user agent), so you stay signed in and we can spot misuse. A session ends when you sign out or after 7 days without use (contract, and our legitimate interest in security).

Your watches

The routes, dates or months, passengers, cabin and target price you save, the prices we check for them, and a record of the alert emails we send you (date, kind, price). This is the service itself (contract).

Invite requests

If you ask for a seat among the invited watchers, your email address, to answer you (your request).

Emails

Account emails (verifying your address, resetting a password, confirming a deletion) and the price alerts you set up (contract). Only if you ask for them, at sign-up or on your Account page: deals, travel ideas and reminders about your searches, each with a link to stop them (your consent).

Your search history

While you're signed in, the searches you run (route, dates or month, passengers, when), so you can run them again from “Your recent searches” and see your own stats and routes on your account page; if you asked for our emails, also to remind you about them (contract; your consent for the reminders). You can remove one, or clear them all, from your account page.

Signing in safely

When you sign in by password from a browser we haven't seen, we email you a 6-digit code; a browser you confirm is remembered for 30 days by a cookie (better-auth.trust_device). If you add an authenticator app, we keep its secret key and your backup codes, encrypted, until you remove it. Needed to keep your account yours (contract and our legitimate interest in security).

Your phone number

When we ask for it: a free account confirms a mobile number with a code by SMS before its first alert (one number, one free alert), and so does an account made where many others were. We keep the number (in international format, with its country) to stop it confirming other accounts, and, for 30 days, a scrambled (keyed hash) record of each code sent, with the number's country and first digits, to stop SMS fraud. Our legitimate interest in preventing abuse. We never use it for marketing without asking you separately. The SMS goes through Twilio Inc. (United States; transfers under the EU–US Data Privacy Framework and the EU Standard Contractual Clauses).

Your preferences

The language, currency and home you choose while signed in (the town you type, and the nearest city with fares), so every device you sign in on uses them (contract). The town is looked up as you type through Photon (komoot GmbH, Germany), asked by our server: it gets the letters, never who you are.

What you agreed to

When you made your account: that you accepted the Terms and said you're 16 or older, how (the sign-up form, or the notice under “Continue with Google”) and when; and whether you want our emails, and when you last said so (legal obligation, to show it).

Your nearest city

To start the route finder on a city near you, your IP address is sent to our travel-data partner to look up a city, once per visit. Neither the address nor that city is stored, not even in your browser; only a city you pick yourself is remembered (legitimate interest).

Abuse limits

Your IP address, briefly, to limit how often forms and searches can be sent from one connection (legitimate interest in keeping the service up).

Cookie choices

Each answer to the cookie question: a random ID kept in your browser, what you allowed and when, and your account if you were signed in, so we can show what you agreed to (legal obligation).

Where you came from

Only if you allow analytics or marketing cookies: the campaign tags, the site that linked to us and the page you landed on, first and last time; with marketing, also the ad click IDs from Google, Meta or Pinterest. Kept in your browser and, once you sign in, on your account, so we can tell which campaigns bring people who sign up (your consent).

How the site is used

Only if you allow analytics cookies: the pages you open, the searches you run (route, dates, nights), what you click, the booking links you follow, the watches you save, your browser, device and screen size, how fast pages load, and your country and city, worked out from your IP address, which isn't kept. Also recordings of the screen as you use the site, which we watch to find what's confusing or broken: what you type is never recorded, and names and email addresses are hidden. Tied to a random ID, and once you sign in to your account's ID, never to your name or email (your consent).

Visit counts (everyone, no cookies)

For each page you open, our own server notes the page, the page that sent you, your browser, device and language, and your country and city as our network provider reports them. Your IP address is used only, with your browser, to make a scrambled code that changes every day, so the pages of one visit group together; the address itself isn't kept, and nothing is stored in your browser. We also note the searches you run (route, dates, nights), the booking and partner links you follow, the watches you save, and when you sign up or sign in; while you're signed in, these carry your account's ID, never your name or email, so we can tell which pages and channels bring people who sign up. Automated visits (search engines, bots) are kept only as daily totals. If your browser sends Global Privacy Control, none of this is recorded. Kept on our own servers in the EU and shared with no one. Our legitimate interest in knowing how the site is used and what brings people to it; you can object by writing to us.

Google Analytics

Only if you allow analytics cookies; before that, Google's tag isn't loaded at all. It counts your visits and the pages you open, with the same events as above (searches, booking links, watches, sign-ups), your browser, device and approximate location and, while you're signed in, your account's ID, never your name or email (your consent).

Errors

When a page or request fails on our server: the error, the page's address without its query, and when, so we can fix it. Not who you are, and no cookies (legitimate interest in a site that works). Errors in your browser are sent only if you allow analytics cookies, with the rest of “How the site is used”.

Searches send only the route, dates, passengers and cabin to the fare providers, never who you are. We don't sell personal data, and we don't use it for advertising profiles.

None of the analytics that uses cookies runs before you answer the cookie question, or at all if you say no. Visit counts use no cookies and run for everyone.

fmm-lang (cookie, 1 year)

Remembers the language you picked. Necessary.

Session cookie (while signed in)

Keeps you signed in. Necessary.

fmm-origin (cookie and local storage, 1 year, only once you pick a city)

The city you chose for the route finder to start on. A preference you set; holds a city code, not your location.

fmm-device (cookie, 1 year, set on the sign-up page)

A random ID for this browser, used only to notice one browser making many accounts. Necessary for the security of signing up.

fmm-currency (local storage, until you clear it, only once you pick a currency)

The currency you chose for prices. A preference you set. Until you pick one, the page guesses it from your device's time zone and language each visit, in your browser, and stores nothing.

fmm-consent (cookie, 1 year)

Your answer to the cookie question and the random ID that links it to its record, so we don't ask on every page. Necessary.

fmm-attr (cookie, 90 days, only if you allow analytics or marketing cookies)

Where you came from (see above). Withdraw and it's deleted.

Google Analytics: _ga, _ga_… (cookies, up to 2 years, only if you allow analytics cookies)

A random ID that lets Google Analytics tell one visit of yours from the next. Withdraw and they're deleted.

PostHog: ph_… (cookie and local storage, 1 year, only if you allow analytics cookies)

The random ID and the current visit that tie your use of the site together (see “How the site is used”). Withdraw and they're deleted.

Travelpayouts: am_user_session (cookie, about 30 minutes, renewed while you browse; only if you allow marketing cookies)

Our affiliate partner's script and its session cookie, so we're credited when you book through one of our links. It also reads the Google Analytics ID and the Google Ads click ID our site keeps (see above) and sends them to Travelpayouts with the visit, and notes which booking links and windows the page opens. For collecting and sending these, we and Travelpayouts are joint controllers; what Travelpayouts does with them afterwards falls under its own privacy policy. Say no and nothing else changes. You can change your answer any time from “Cookie choice” in the footer.

Fly Me Maybe doesn't sell tickets. “Book” opens our travel partner's site, where you book under its own terms and privacy policy. The links for the rest of a trip (an eSIM, a ride from the airport, a rental car, tickets for things to do, a claim for a delayed flight) work the same way, each to its own partner's site, through our affiliate network. We don't send it your account or your email. Our links carry a short label, the page you were on and, if you allowed analytics or marketing cookies, where you came from (a campaign's name, say), so our partner's reports show which pages and campaigns lead to bookings. When you book through our links we may earn a commission; it doesn't change your price.

Only providers we need to run the service, each for its own part and under a data processing agreement. We don't name them here; if you'd like the full list, write to us and we'll send it.

Hosting

The site and the database, on servers in the EU.

Email delivery

Account emails and alerts, sent from the EU. The provider's parent company is in the United States, so any transfer there relies on the EU Standard Contractual Clauses.

Sign in with Google

Only if you choose it: Google confirms who you are and sends us your name, email and picture.

Travel data and affiliate partner

Cached fares, the nearest-city lookup and, with your consent, affiliate cookies.

Live flight prices

Prices from flight search providers in the United States. They receive the search, never who made it.

Bot protection: Cloudflare Turnstile

Named because it runs in your browser. On the sign-up, sign-in and password-reset forms, it checks that a person is using them, from signals about your browser and connection, without tracking you across sites and without cookies for advertising. Our legitimate interest in keeping accounts from being made or broken into by scripts. Cloudflare, Inc. is in the United States; transfers rely on the EU–US Data Privacy Framework and the EU Standard Contractual Clauses.

Usage analytics: Google Analytics

Named because it sets cookies. How the site is used, as described above, by Google Ireland Ltd. Google LLC in the United States can access it, under the EU-US Data Privacy Framework.

Usage analytics: PostHog

Named because it sets cookies. With your consent, how the site is used; without it, the server errors above. Stored in PostHog's EU cloud, in Frankfurt. PostHog Inc. is in the United States, so any access from there relies on the EU Standard Contractual Clauses.

• Your account and everything tied to it (watches, target prices, price history of your watches, the record of your alert emails) until you delete the account.
• Deleting your account removes all of that at once, together with your sessions and sign-in methods. A watch other people follow stays for them, without you.
• Sessions: until you sign out, or 7 days without use.
• Invite requests: until we've answered, or you ask us to remove them.
• Abuse-limit counters: minutes to an hour. Server logs, which can include IP addresses: a few days.
• Cookie choices: while that answer applies (a year at most), and 3 years after, the general limitation period in Romania, so we can show what you agreed to. Deleting your account unlinks them from it.
• Search history: the latest 50 searches of the last year. What you agreed to: as long as your account exists. Both go when you delete it.
• Where you came from: in your browser, 90 days; on your account, until you delete it or withdraw that consent.
• How the site is used: screen recordings, 30 days; the rest, up to 7 years, so we can compare over time. Deleting your account deletes what's tied to it.
• Errors: up to 7 years, tied to no one.
• Google Analytics: 14 months.
• Visit counts: 13 months, then only daily totals that say nothing about anyone. Deleting your account unlinks them from it.

Under the GDPR you can ask to see your data, correct it, delete it, restrict or object to how we use it, take it with you, and withdraw a consent you gave, at any time.

• Download your data or delete your account yourself, from the Account page.
• For anything else, write to [email protected]. We answer within a month.
• If you think we got it wrong, you can complain to the Romanian data protection authority, ANSPDCP (dataprotection.ro), or to the authority where you live.

Everything travels over HTTPS, passwords are stored only as hashes, API keys stay on the server, and access to the database is limited to what runs the service. Deleting an account asks for a confirmation sent to your email first.

Accounts are for people aged 16 and over. If you think a child has made one, write to us and we'll delete it.

The date at the top says when this page last changed. If a change affects how your data is used, we'll email account holders before it applies.