LarpBot Privacy Policy
Effective date: 30 July 2026 Last updated: 2 August 2026
LarpBot is operated by Abhiram Somisetty ("we", "us"), contactable at abhisurya3221@gmail.com. This policy explains what the LarpBot iOS app collects, what it does not, and what rights you have.
We have tried to write this so it is actually readable. Where a section makes a specific technical claim, that claim describes how the app is built today — not an aspiration.
1. The short version
- You can use LarpBot without an account. Nothing is gated behind signing in.
- We do not store the topics or questions you enter. They are passed through our server to Google's Gemini API to generate your briefing, and are not written to our database. See section 3.
- We keep counters, not content: how many briefings you asked for on a given day, so we can enforce a daily limit.
- We do not sell your personal information, and we do not use it for advertising.
- If you create an account, the only personal detail we hold is your email address.
2. What we collect
2.1 Account and identity data
| Data | When | Why | Where it lives |
|---|---|---|---|
| Anonymous user ID (a random UUID) | First launch | To meter your daily usage so limits survive a reinstall | Our database (Supabase) |
| Session token | While signed in | To keep you signed in | Your device's Keychain |
| Email address | Only if you choose to sign in | To identify your account across devices and restore your usage history | Our database (Supabase) |
| Apple user identifier | Only if you use Sign in with Apple | To link your Apple ID to your LarpBot account | Our database (Supabase) |
By default LarpBot signs you in anonymously. That anonymous identity is a random identifier scoped to your installation. It is not your device's advertising identifier, IDFA, IDFV, phone number, or any hardware serial.
If you use Sign in with Apple and choose Apple's "Hide My Email" option, we receive only the relay address Apple generates. We never receive your real address.
We do not collect your name, date of birth, phone number, contacts, photos, precise or coarse location, or health data. LarpBot has no advertising SDK, no analytics SDK, and no crash-reporting SDK.
2.2 Usage counters
For each account, each UTC calendar day, and each type of request, we store a single integer count. This is the entire record:
user_id | day | kind ("briefing" | "ask" | "chat") | count
There is no column for the topic, the question, or the response. We keep these counts to enforce the daily ceiling described in the Terms of Use and to show you how much of your allowance you have used.
2.3 Subscription data
If you subscribe to LarpBot Pro, we store what Apple tells us about that subscription so we know whether to give you the higher limit:
- Apple's original transaction identifier (stable across renewals and reinstalls)
- The product identifier (
com.larpbot.pro.monthly) - Expiry date, grace-period end date, auto-renew flag, and Apple's numeric status
- Whether the transaction came from Apple's production or sandbox environment
We never receive or store your payment card, billing address, or Apple Account credentials. Apple processes the payment; we only ask Apple's App Store Server API whether a given subscription is currently valid.
2.4 Content you enter (transiently)
The topic or question you type or dictate is sent to our server and on to Google in order to produce a briefing. It is processed in memory to build the request and is not written to our database. See the next section for the limits of that statement.
2.5 On-device only
The following stay on your device and are never transmitted to us:
- Your recent briefings, saved locally so the Recents list works offline
- Whether you have seen the intro
- Your session token (in the Keychain)
Deleting the app removes all of it.
2.6 Dictation
If you use the microphone button, speech is transcribed using Apple's speech recognition. Depending on your device and language, Apple may process audio on-device or on Apple's servers; that processing is governed by Apple's Privacy Policy. We receive only the resulting text, and only as the topic you then submit. We do not record, retain, or transmit raw audio.
3. What we do not store
We want to be precise here, because "we don't store your data" is a claim that is usually overstated.
We do not write your topics, questions, or the generated briefings to our database. Our schema has nowhere to put them. Usage is recorded as a count.
The honest caveats:
- Google receives your topic. It has to — Google generates the briefing. See section 4.
- Your topic exists in memory and in transit while the request is being served, and is protected by TLS end to end.
- Diagnostic logs. Our server logs errors, not requests. Log lines record failure messages (for example, that a quota check failed). We do not log topics. However, if Google's API returns an error, the body of that error is logged for debugging, and in principle such a body could echo part of a request. Our hosting provider retains function logs for a limited period on a rolling basis. We treat these logs as potentially containing personal data and restrict access to them accordingly.
4. Who else receives data
We use three processors. We do not sell data to anyone, and there are no other recipients.
4.1 Supabase — hosting, authentication, database
Our database, authentication, and server functions run on Supabase. Supabase stores your anonymous ID, email (if any), usage counters, and subscription records on our behalf. See Supabase's Privacy Policy.
4.2 Google — briefing generation and web grounding
Your topic or question is sent to Google's Gemini API
(generativelanguage.googleapis.com). LarpBot enables Google's search grounding
feature, which means Google performs web searches related to your topic in order to
answer with current information. Your topic is therefore also used as a search query by
Google.
We send the topic and, for follow-up questions, the briefing text already generated. We do not send your email address, your user ID, your IP address, or any other identifier alongside it — Google receives the topic without an identity attached to it from us.
Google's handling of API data is governed by the Google APIs Terms of Service and the Gemini API Additional Terms. Please review those terms; we cannot make commitments on Google's behalf.
4.3 Apple — distribution and payments
Apple handles app distribution, in-app purchases, Sign in with Apple, and speech recognition. We query Apple's App Store Server API to verify subscriptions. Apple's handling of your data is governed by Apple's Privacy Policy.
5. Legal bases for processing (UK/EU/EEA)
Where the UK GDPR or EU GDPR applies, we rely on:
| Purpose | Legal basis |
|---|---|
| Providing the app you asked for (generating briefings) | Article 6(1)(b) — performance of a contract |
| Metering daily usage and preventing abuse of our API costs | Article 6(1)(f) — legitimate interests |
| Maintaining your account and restoring history across devices | Article 6(1)(b) — performance of a contract |
| Verifying and honouring a paid subscription | Article 6(1)(b) — performance of a contract |
| Keeping error logs to diagnose faults and maintain security | Article 6(1)(f) — legitimate interests |
We do not rely on consent for any of the above, and we do not process special-category data. Where we rely on legitimate interests, we have considered your rights and limited what we keep to counters and identifiers.
6. International transfers
Our infrastructure and our processors operate in, and may transfer data to, countries outside the UK and EEA — including the United States. Where such a transfer occurs, it is made under the UK International Data Transfer Addendum and/or the European Commission's Standard Contractual Clauses, and/or another mechanism permitted under Article 46 GDPR, as implemented in our agreements with Supabase, Google, and Apple.
You may request a copy of the relevant safeguards by writing to abhisurya3221@gmail.com.
7. How long we keep things
| Data | Retention |
|---|---|
| Topics, questions, generated briefings | Not retained by us (see section 3) |
| Daily usage counters | Retained while your account exists; superseded each UTC day |
| Anonymous ID / email / Apple identifier | Until you ask us to delete your account |
| Subscription records | While the subscription exists, and afterwards only as long as needed for tax, accounting, and dispute-resolution obligations |
| Diagnostic logs | A limited rolling window set by our hosting provider |
| On-device briefings | Until you delete the app or clear them |
8. Your rights
Depending on where you live, you may have the right to access, correct, delete, port, or restrict processing of your personal data, to object to processing, and to withdraw consent where we rely on it.
To exercise any of these, email abhisurya3221@gmail.com. We will respond within one month (UK/EU) or 45 days (California), and we will not charge you or degrade your service for asking.
8.1 California (CCPA/CPRA)
We do not sell personal information, and we do not share it for cross-context behavioural advertising. We have no "Do Not Sell or Share My Personal Information" link because there is nothing to opt out of. California residents have the rights to know, delete, correct, and to non-discrimination, and may exercise them at the address above. In the twelve months preceding the effective date of this policy, the categories we collected were identifiers (an anonymous ID, and an email address if you provided one) and commercial information (subscription status).
8.2 UK/EU
You may lodge a complaint with your supervisory authority. In the UK that is the Information Commissioner's Office. In the EEA it is your national data protection authority.
8.3 Deleting your account
Open the app and go to Account → Delete account. Deletion happens immediately on our server: our database is configured to cascade deletions, so removing your user record removes your usage counters and subscription rows with it. If you can't use the app — lost device, can't sign in — email abhisurya3221@gmail.com and we will delete the account for you. Deleting the app from your device removes local data immediately, but does not by itself delete your server-side account.
Deleting your LarpBot account does not cancel your Apple subscription — only Apple can do that. See Cancelling in the Terms of Use.
9. Children
LarpBot is not directed to children and is not intended for anyone under 13 (or under 16 in the UK/EEA where that higher age applies). We do not knowingly collect personal information from children. If you believe a child has provided us with personal information, email abhisurya3221@gmail.com and we will delete it.
Because LarpBot generates text from live web results, its output is not age-filtered and we do not represent it as suitable for children.
10. Security
Traffic between the app, our server, and our processors is encrypted with TLS. Your session token is stored in the iOS Keychain. Our database enforces row-level security so one account cannot read another's rows, and the functions that could alter usage counts are restricted to server-side credentials that never reach your device. The Gemini API key is held as a server-side secret and is never included in the app.
No system is perfectly secure, and we do not claim otherwise. If you find a vulnerability, please report it to abhisurya3221@gmail.com.
11. Automated processing
Briefings are generated by a large language model without human review. This is content generation, not decision-making: it has no legal or similarly significant effect on you within the meaning of Article 22 GDPR. Output can be wrong, out of date, or incomplete — the app says so on every screen, and you should not rely on it as fact.
12. Changes
If we change this policy we will update the "last updated" date, and for material changes we will give notice in the app before the change takes effect. Continuing to use LarpBot after a change takes effect means you accept the updated policy.
13. Contact
Abhiram Somisetty abhisurya3221@gmail.com
For UK/EU data protection enquiries, use the same address and mark it for the attention of our data protection contact.