Larkabout
Privacy Policy
Last updated: 23 October 2026 · Version 1.6
This policy explains what Larkabout does with your information. It describes the app as it actually works — every statement here was checked against the code that ships, not against a plan.
Larkabout is an app for parents. It is not for children, it is not directed at children, and it holds no profile of any child. See Children below, which is the part most people want first.
1. Who is responsible for your data
The controller of your personal data is SEICHE LAB, MCHJ, a company registered in the Republic of Uzbekistan. SEICHE LAB publishes Larkabout on the App Store.
- Address: 65-j, Pichoqchi MFY, Xiyobon Str., Margilan, Fergana Region, 151100, Uzbekistan
- Your data: privacy@parentapp.net · Everything else: support@parentapp.net · Phone: +998 50 796 17 53
- EU representative: not yet appointed. Until we name one, write to privacy@parentapp.net — we answer every request ourselves.
- UK representative: not yet appointed. Until we name one, write to privacy@parentapp.net.
If you tested Larkabout before its release. Test versions on TestFlight come from the personal developer account of SEICHE LAB’s founder, and earlier versions of this policy named him as the controller. From the date of this version, SEICHE LAB is responsible for the data of every version of Larkabout, test versions included.
2. What Larkabout does without knowing anything about you
The map, the list, the filters, search, the place cards, “Meet in the middle” and the AI assistant’s free questions all work without an account. If you never create one, we hold no name and no email address for you.
You are asked to create an account only to save a place.
To count your free AI questions, the first time you ask one we give this installation a random identifier on our servers. It holds no name, no email and no identifier from your phone. The same identifier records whether you have already seen our one-time yearly offer, so that it is shown only once. If you later create an account, this identifier becomes your account.
Our sign-in system keeps, for each signed-in session — with an account or with this identifier — the IP address and the type of device it came from, to keep sessions secure.
Legal basis: performance of the service you asked for (Article 6(1)(b) GDPR); for the session details, our legitimate interest in keeping accounts secure (Article 6(1)(f) GDPR).
3. Your choices, and where they live
The second screen you see in Larkabout asks three separate questions, all switched off until you turn them on:
- Usage analytics — section 5.5
- Install attribution — section 5.6
- Advertising measurement — section 5.7
Nothing is pre-ticked, “Reject all” is as easy as “Accept all”, and you can change any of it later in Settings → Privacy & consent. Turning something off stops it — it is wired to each provider’s own off switch, not merely to a note on your phone.
Crash reporting (section 5.4) is not one of the three. It runs on our legitimate interest in keeping the app working, and it is described in full below so you can see exactly what it carries.
4. Children
Larkabout collects no information about any individual child. There is no child profile, no name, no date of birth, no exact age, no photograph, no voice recording, and no field anywhere in our systems that could hold one.
During setup we ask two questions about your household so the app can be useful: how many children you have, and which age ranges they fall into — you tap 0–1, 1–3 or 3–4. You cannot type a birthday or an exact age, because the screen has no keyboard on it.
Those answers stay on your phone. They are used to shape what the app shows you, and they leave your device in only two situations:
- If you allow usage analytics, one event recording the answers you gave — the number of children, the age ranges, your city, and your activity and transport preferences — is sent to our analytics provider once, when you finish setup. See section 5.5.
- If you use the AI assistant, the number of children and the age ranges travel with your question so the answer fits your family. See section 5.9.
Nothing about your children is ever sent to Meta or to any advertising system, under any setting.
Larkabout is intended for adults. If you are under 18, please do not use it.
5. What we hold, why, and who else sees it
5.1 Where you are
When you allow it, Larkabout reads your device’s location to sort places by how long it actually takes to get there and to find the nearest changing station.
Your location is never stored on our servers. It is used on your phone and in the query that produces the answer, and then it is gone. There is no location history, and there is no table anywhere in our database that could hold one.
If you refuse location, the app still works: it opens on the city you chose during setup.
Legal basis: performance of the service you asked for (Article 6(1)(b) GDPR).
5.2 “Meet in the middle”
This feature takes two or three starting points — yours and your friends’ — and finds places between them.
We store none of it, and we cannot: the whole calculation runs on your phone. The starting points never reach our servers, so there is nothing for us to keep, hand over, or lose. That includes the address you enter for someone else, which is the reason it works this way.
One thing does leave your phone. If you type a place name or an address instead of dropping a pin, your phone sends what you typed to Google as you type, to turn it into a point on the map and to suggest places while you are still typing — the same Google that draws the map itself. It goes straight from your phone to Google, never through us, and we never see it. If you would rather not involve Google at all, press and hold the map to drop the pin yourself.
The search screen asks Google too — but only when our base comes up empty. When no place we have checked matches the name you typed, your phone sends what you typed to Google, to see whether such a place exists at all — straight from your phone, never through us, and we never see it. What comes back is shown under the Google Maps mark, kept nowhere, and never mixed in with the places a parent has checked. If our base has the place, Google is never asked.
5.3 Your account and your saved places
If you save a place, Larkabout asks you to create an account. You can do that with Apple, with Google, or with a sign-in link sent to your email address.
What we hold for an account is short: your email address (or the private relay address Apple gives us if you chose to hide yours), the list of places you saved, and the session details in section 2. Your setup answers are not part of your account — they stay on your phone.
Your account data is stored in the European Union (Frankfurt), with our hosting provider Supabase.
Legal basis: performance of the service you asked for (Article 6(1)(b) GDPR).
5.4 Crash and error reports
Larkabout sends crash and error reports to Sentry so we can find and fix what breaks.
A report carries the device model, the operating system version, and the technical trace of what went wrong. It carries no name, no account, and nothing you type — we never attach your identity to a report, and the AI question screen is excluded from the diagnostic trail entirely. Sentry infers an IP address from the connection that delivers the report; that is the one piece of personal data in this channel.
Legal basis: our legitimate interest in a working, secure app (Article 6(1)(f) GDPR).
5.5 Usage analytics — only if you allow it
If you allow it, we record which screens you open and which buttons you tap, so we can see which parts of the app work and which do not. These events are stored by our analytics provider, Amplitude, under a random identifier generated on your device — not your name, your email or any identifier issued by your phone. We link that same identifier to your subscription status held by Apphud, so we can tell whether the features people use are the ones they find worth paying for.
One of these events carries your setup answers: when you finish setup, we send the city you chose, how many children you have, their age ranges as bands, and your activity and transport preferences, as a single event. Nothing about your children is attached to any other event, and no exact age, birthday or name exists for us to send.
We never attach your name, your email address, or anything you search for to these events, and no event ever carries your location.
You can withdraw this at any time in Settings → Privacy & consent; we then stop recording and remove the link. If you want the history deleted as well, ask us and we will have both providers erase it.
Legal basis: your consent (Article 6(1)(a) GDPR).
5.6 Install attribution — only if you allow it
If you allow it, Branch records which advertisement or link brought you to Larkabout, so we can tell which of our campaigns worked. This uses identifiers from your device. Until you allow it, Branch is switched off before it can make a single network request.
Separately from attribution: links you share from Larkabout live on Branch's domain, so opening one is resolved by Branch's servers — even if neither you nor the person you sent it to has allowed anything. A shared link carries the place it points to — its identifier, its public name and its district — and nothing about you or your family. Chat apps also fetch such a link once to draw a preview card.
You can withdraw it at any time in Settings → Privacy & consent.
Legal basis: your consent (Article 6(1)(a) GDPR).
5.7 Advertising measurement — only if you allow it
If you allow it, we share limited events about your use of the app — creating an account, opening the subscription screen, and starting a trial, together with the amount and currency — with Meta Platforms Ireland Limited, so that we can measure whether our advertising reaches parents who need this app.
Who is responsible. For collecting these events in the app and sending them to Meta, we and Meta Platforms Ireland Limited are joint controllers under Article 26 GDPR. Under Meta’s Controller Addendum, we are responsible for collecting and sending the events lawfully and for telling you about it; Meta Platforms Ireland is responsible for your rights over the data once it holds it. When Meta measures our ads, it processes the events on our behalf. For its own purposes, Meta is an independent controller under Meta’s Privacy Policy.
We never send your email address, your name, your searches, your location, or anything about your children.
You can withdraw this permission at any time in Settings → Privacy & consent, and it stops both the app and our subscription provider from sending further events. The app stops immediately; our subscription provider is told within seconds and stops from then on.
To exercise your data rights against Meta, you may contact us and we will forward your request to Meta within seven calendar days, or contact Meta directly.
Legal basis: your consent (Article 6(1)(a) GDPR).
5.8 Subscriptions
We use Apphud to manage subscriptions and to check whether this device already has one. Because anyone may be returning to restore a purchase they made before, a subscription record is created for every installation as soon as you have made your privacy choices, whether or not you ever open the subscription screen. That record holds a random identifier generated on your device and your subscription status — no name, no contact details, and nothing about how you use the app unless you allowed usage analytics. Once you create an account, we also attach the account identifier we issued — an identifier of ours, not one your phone or Apple gave us — so that your subscription follows your account rather than only this handset.
Payment is handled by Apple. We never see your card details, and we cannot charge you — Apple does, under your App Store account.
Legal basis: performance of the service you asked for (Article 6(1)(b) GDPR).
5.9 The AI assistant
AI questions are answered using Anthropic (USA) as our processor: your query and quiz preferences are sent to generate the reply, are not used to train AI models, and Anthropic deletes them from its systems within 30 days — longer only where the law or its own misuse checks require it. We store only the structured interpretation of your query, never its text.
Concretely, what travels with your question is: the number of children, their age ranges as bands, your activity and transport preferences, and — when the assistant works it out from your question — the district you are asking about. Never a street address, never a coordinate, never your email address or any account identifier.
We keep a record of each question you ask for metering and cost control — under your account, or under the random identifier in section 2: the date, the structured interpretation, the size of the request, and — if we could not understand it — a one-word label saying why. There is no column in our database that can hold the text of your question. These records are deleted after 12 months. If you delete your account sooner, they are unlinked from you at once; what remains has no link to you and is deleted when its 12 months run out.
Before your first question, Larkabout asks you separately for permission and names Anthropic. The place where you ask is marked “Ask AI”.
Legal basis: your consent for the transfer to Anthropic; performance of the service you asked for, for the answer itself.
5.10 Maps and directions
The map inside Larkabout is provided by Google Maps. When the map is on screen, your device talks to Google directly, which means Google receives your device’s IP address and the area you are looking at, under Google’s own terms.
When you tap Directions, Larkabout hands the destination to Google Maps or Apple Maps on your phone. From that moment you are in their app, under their privacy policy, not ours.
Photos, and whether a place is still open. When you open a place’s full card, Larkabout asks Google for up to two photos of that place and for whether Google shows it as temporarily or permanently closed — so that nobody drives across the city to a place that has shut. That request goes from your phone to Google and carries your device’s IP address, exactly as the map does. It happens only on the full card, never on the map and never in the list. What comes back is shown and then gone: we do not store Google’s photos or Google’s opening status, and nothing Google says is written into our own record of a place. Where Google supplies a photo credit, we show it next to the photo.
Place information in Larkabout comes from OpenStreetMap plus our own checks. Some venue listings include a telephone number published on OpenStreetMap, which for a small business is sometimes the owner’s personal number. If that number is yours and you want it gone, email privacy@parentapp.net and we will remove it.
5.11 The sign-in email
If you sign in with your email address, the sign-in link is delivered by our email provider, Resend (Plus Five Five, Inc., USA), which processes your email address and the sign-in message on our behalf and for no other purpose. Because Resend operates in the United States, this transfer is protected by the EU Standard Contractual Clauses incorporated into our agreement with Resend. Each link works once and expires shortly after it is sent.
5.12 If you write to us
If you email us a suggestion, a correction to a place, or a question, we keep your message and your address for as long as it takes to deal with it and to keep a record of what we changed and why.
Legal basis: performance of the service, and our legitimate interest in maintaining accurate place information (Article 6(1)(b) and (f) GDPR).
5.13 Speaking instead of typing
In the search field and in the AI question field you can speak instead of typing. Larkabout asks your phone to do the recognition on the device itself, and it offers the microphone only when your phone reports that it can recognise your language without a network. What you say is turned into text on your phone. The recording is not sent to us, and we never receive it.
About the notice Apple shows you. The first time you use the microphone, iOS displays its own permission sheet, and that sheet says speech data will be sent to Apple. That sentence is Apple’s, it is identical in every app that asks for this permission, and no app can change or remove it. It describes what the permission allows in general. What Larkabout asks for is on-device recognition — which is also why the microphone button is simply absent, rather than quietly falling back to a network service, on a phone that cannot do it.
Legal basis: performance of the service you asked for (Article 6(1)(b) GDPR) — for the text your words become, which is the same text you would have typed. The recording itself we never receive, so there is nothing for us to hold a basis for.
5.14 Places you suggest to us
If you tell us about a place we are missing — from the search screen, or from the card of a place we found on Google but have never checked — we keep what you send: the place (either the Google reference for the one you were looking at, or nothing at all if you were describing one from scratch) and your note, if you wrote one. It is attached to your account so that we can remove it if you ask us to.
We keep it for 12 months and then it is deleted automatically. Nothing you send is published, shown to other people, or added to the app by itself — a person reads it when we get to it, which is why we do not promise a reply. Please leave other people’s personal details out of the note; the field asks for the place, and that is all we want.
Legal basis: our legitimate interest in improving the base of places we have checked (Article 6(1)(f) GDPR) — you send it deliberately and you choose what to write.
6. Who else receives your data
| Who | What they get | Where | Role |
|---|---|---|---|
| Supabase | Your email address, saved places, AI usage records, and the random identifier and session details from section 2 | European Union (Frankfurt) | Our processor |
| Apple | Sign-in (if you use Apple), all payments and subscriptions | Apple’s own infrastructure | Independent controller for the purchase |
| Sign-in (if you use Google); map tiles and your IP while the map is on screen; a place name or address you type into “Meet in the middle” (section 5.2); a place name you type into search, when no place we have checked matches it (section 5.2); your IP when a place card asks for photos and opening status (section 5.10) | Google’s own infrastructure | Independent controller | |
| Resend | Your email address and the sign-in message | USA | Our processor |
| Sentry | Crash and error reports, and the IP that delivered them | USA | Our processor |
| Anthropic | Your AI question and your setup preferences | USA | Our processor |
| Amplitude | Usage events under a random identifier — only with your consent | USA | Our processor |
| Apphud | Subscription status under a random identifier and, once you have an account, the account identifier we issued | USA | Our processor |
| Branch | Device identifiers for install attribution — only with your consent; and, when you or a friend opens a link shared from Larkabout, the contents of that link (a place identifier and its public name — section 5.6) | USA | Our processor |
| Meta Platforms Ireland | Subscription and registration events — only with your consent | Ireland / Meta’s infrastructure | Joint controller for collecting and sending the events; independent controller for its own purposes (section 5.7) |
We do not sell your data, and we do not share it with anyone not on this list.
7. Sending data outside your country
SEICHE LAB is based in Uzbekistan, outside the EU and the UK. There is no EU or UK adequacy decision for Uzbekistan. When you use Larkabout, you give your data to us directly, and the EU and UK data protection rules apply to us as they would to a company based there.
Your account data is stored in the European Union (Frankfurt). Some of the providers in section 6 are based, or process data, outside Europe — most of them in the United States. This is how that data stays protected:
- Amplitude, Branch and Sentry are certified under the EU-U.S. Data Privacy Framework and its UK Extension, which the European Commission and the UK recognise as giving adequate protection.
- Anthropic, Apphud, Resend and Supabase: the European Commission’s Standard Contractual Clauses and the UK Addendum, which are part of each provider’s data processing terms.
- Meta Platforms Ireland is in the EU.
Email privacy@parentapp.net for a copy of these safeguards.
8. How long we keep things
| What | How long |
|---|---|
| Your account and saved places | Until you delete your account. Deletion is immediate: your account, your saved places and the places you suggested are erased, and your AI usage records are unlinked from you |
| Your AI usage records (never the text) | 12 months, then deleted |
| Places you suggested to us (the place and your note) | 12 months |
| The random identifier that counts free AI questions (section 2) | No fixed period yet. It holds nothing that names or reaches you; the AI usage records linked to it are deleted after 12 months, and if you create an account it becomes your account |
| Session details (IP address, type of device) | Until you sign out or delete your account; for the random identifier, for as long as it exists |
| Your setup answers | On your phone only. They disappear when you delete the app |
| Your record of privacy choices | Kept for as long as we rely on it, as proof of the permission you gave |
| Crash reports | Under our provider’s standard retention period |
| Analytics and attribution events | For as long as we need them to understand and improve the app, then deleted; Amplitude and Branch keep them under their own retention settings. Withdrawing your permission stops new events — ask us and we have the history erased |
9. Your rights
You have the right to ask us for a copy of your data, to correct it, to delete it, to restrict or object to what we do with it, and to receive it in a portable form. Where we rely on your consent, you can withdraw it at any time, and withdrawing does not make what we did before unlawful.
You have the right to object. Where we rely on our legitimate interests — crash reports (section 5.4), session details (section 2), messages you send us (section 5.12) and places you suggest (section 5.14) — you can object at any time, and we will stop unless we have compelling grounds that override yours.
Here is where each of those actually happens:
- Delete your account — in the app: Settings → Account → Delete my account. It erases your account and your saved places at once and unlinks your AI usage records from you, and it cannot be undone. You can carry on using Larkabout without an account.
- Withdraw a permission — in the app: Settings → Privacy & consent. It takes effect when you save.
- Get a copy of your data — email support@parentapp.net. We will send it within one month. It is short: your email address, your list of saved places, and any places you suggested to us.
- Anything else, including a correction or an objection — email privacy@parentapp.net.
- A request that concerns Meta — write to us and we will pass it to Meta within seven calendar days, or write to Meta directly.
If you think we have handled your data wrongly, tell us first — most problems are fixed by one email. You can also complain to a data protection authority:
- Poland: Urząd Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa — uodo.gov.pl
- United Kingdom: Information Commissioner’s Office (ICO) — ico.org.uk/make-a-complaint
- Or the authority in the country where you live.
10. Decisions made about you
None. The AI assistant suggests places; it decides nothing about you, and nothing in Larkabout makes an automated decision that has a legal or similarly significant effect on you.
11. Is any of this required?
Only what a feature needs. You can use the map, the filters, search and “Meet in the middle” without giving us anything at all, and the AI assistant’s free questions with nothing but the random identifier in section 2. An account is required only to save a place, because a saved place needs somewhere to stay. The three permissions on the consent screen are genuinely optional — refusing all three costs you nothing inside the app.
12. Changes to this policy
This page carries a version number and a date. If we change anything that matters — a new provider, a new purpose, a change of controller — we will update the date, and where the change affects a permission you have already given, we will ask you again inside the app rather than rely on you re-reading this page.
Version 1.6 — 23 October 2026. What changed since 1.5:
- A new controller. SEICHE LAB, MCHJ — the company that publishes Larkabout on the App Store — is now responsible for your data, in place of its founder as an individual developer (section 1). SEICHE LAB is based in Uzbekistan, so section 7 now explains how your data stays protected outside Europe and names the safeguard for each provider. Representatives in the EU and the UK are not yet appointed; section 1 says how to reach us meanwhile. Larkabout from SEICHE LAB is a new app on the App Store, so it asks for your permissions afresh when you install it.
- The app is called Larkabout. Earlier versions of this page called it PA.
- Catching up with the app. The AI assistant’s free questions work without an account; section 2 now describes the random identifier that counts them and the session details our sign-in system keeps. Deleting your account unlinks your AI usage records from you rather than erasing them at once (sections 5.9 and 8). These were already part of the app and are described here for the first time.
- Section 5.7 names all of Meta’s roles; section 9 says how to object and adds the UK authority; section 8 gives the analytics period in place of “deleted on request”.
Version 1.5 — 21 September 2026. What changed since 1.4: section 5.9 now gives the real deletion period at Anthropic. It said your question was deleted from Anthropic’s systems “within days”. Anthropic’s own published figure is 30 days, and deletion is not unconditional — material is kept longer where the law or Anthropic’s own misuse checks require it. Nothing about what we send, why, or to whom has changed; only the description of how long it sits there was wrong, and it was wrong in our favour.
Version 1.4 — 21 August 2026. What changed since 1.3: section 5.6 gains a paragraph about shared links, and the Branch row in section 6 now names their contents. Links you share from PA have always lived on Branch’s domain, and opening one is resolved by Branch’s servers before any consent — on your device or the recipient’s. The link carries the place it points to (its identifier and public name) and nothing about you. Nothing in the app changed; the policy previously described Branch’s SDK on your device and was silent about the links themselves. This version closes that gap.
Version 1.3 — 21 August 2026. What changed since 1.2: section 5.2’s search paragraph — PA no longer shows you a button to press before it asks Google. When no place we have checked matches the name you typed, your phone asks Google straight away. The recipient has not changed, the data has not changed, and the purpose has not changed — the same words go to the same place for the same reason. What changed is when: before, only if you pressed a button; now, whenever our own base has nothing. This is still narrower than “Meet in the middle”, which has sent what you type to Google as you type since August 2026. Nothing new is kept, and results now carry the Google Maps mark.
Version 1.2 — 21 August 2026. What changed since 1.1: section 5.2 now covers the search screen’s Google button as well as “Meet in the middle” — the same recipient and the same purpose, reached by a second, explicit action; section 5.14 is new and describes the places you suggest to us, including the 12-month period and the fact that nothing is published; section 5.8 and the recipient table say that Apphud also holds the account identifier we issue once you have an account; section 8 gains the suggestions row; and the “copy of your data” line now names suggestions too.
Version 1.1 — 14 August 2026. What changed since 1.0: section 5.2 now names Google as the recipient of what you type (a place name or an address); section 5.10 describes the photos and the opening status a place card asks Google for; section 5.13 is new and covers speaking instead of typing.