Bachlette

Privacy Policy

Last updated: 30 September 2026

1. Introduction

This Privacy Policy explains how Bachlette ("we", "us", "our") collects, uses, discloses and protects personal information when you use the Bachlette mobile application for iOS and Android (the "App" or "Service").

Bachlette is operated by a sole trader in Queensland, Australia, ABN 30 517 427 873. You can reach us at [email protected].

This policy also covers this website, which collects nothing at all: it has no analytics, sets no cookies, and does not track visitors.

By using the Service you agree to this Policy. If you do not agree, please do not use the Service.

2. Who this Policy applies to

Bachlette is sold on the App Store and Google Play in every market except the European Economic Area and the United Kingdom, where it is not offered for sale. This Policy applies to everyone who uses the Service, and includes additional rights for users in the United States (Section 13) and Australia (Section 14).

3. Age requirement

The Service is intended for users aged 18 and over. We do not knowingly collect personal information from anyone below this age. If we learn that we have done so, we will delete it promptly. If you believe a child has provided us with personal information, contact us at [email protected].

4. Information we collect

4.1 Account information

If you create an account with an email address, we collect your email address and a password. Passwords are stored only as a cryptographic hash by our authentication provider and are never visible to us in readable form.

If you sign in with Apple, we receive your email address and full name. Apple provides your name only on first sign-in, and allows you to hide your real email address using Apple's private relay service.

If you sign in with Google, we receive your email address, name, and profile photo URL.

4.2 Profile information

Your display name, which is free text you choose and which is visible to other people in any party you join.

4.3 Party and game content

Information created through normal use of the App:

  • Party names, access codes, and party settings
  • Party membership, including host and bride designations
  • Prompts, including any text a host writes or edits
  • Your in-game activity: votes, prompt claims, and bingo card progress

4.4 Push notification tokens

If you allow notifications, we store a push notification token identifying your device installation. That token is the only thing we store for this purpose. We do not store your device model, your operating system version, or any other characteristic of your device alongside it.

We are not sending push notifications yet. The token is stored so that we can send them about your parties when that feature is released. On Android, delivery will be handled through Google Firebase Cloud Messaging.

4.5 Technical information

  • IP address. Our backend and app-update servers log your IP address when your device connects. An IP address can indicate approximate location, generally at city level. We use this for security and fraud prevention, not to determine where you are.
  • App update metadata. The App checks for over-the-air updates, and these checks send device and runtime information (such as app version, platform and runtime version) to our update provider.

4.6 Purchase information

Bachlette is unlocked by a one-time in-app purchase. The purchase is processed by Apple In-App Purchase or Google Play Billing, under their own terms and privacy policies, and charged to the store account you bought it with.

We do not collect, receive, process or store your credit card number, bank details, billing address, or any other financial information. None of it reaches us. The store takes the payment and tells us only that it happened.

What is recorded on your account. Your profile carries a single true/false flag saying whether the App is unlocked. The App cannot write that flag. It is written by our server, when RevenueCat, the service that sits between the stores and us, notifies the server that your store account holds the unlock, and by nothing else.

What we keep about the purchase itself. Each notification is recorded, and each record holds:

  • the store it came from, and whether it was a test purchase or a real one;
  • the product bought and the unlock it granted;
  • the store's transaction identifiers for it;
  • the price, currency and storefront country the store reported;
  • when the purchase was made, what kind of event it was (a purchase, a refund, a transfer), and the notification itself as RevenueCat sent it.

The identifier tying that record to you is your Bachlette account id. We do not receive your name, your email address, or your payment details from the store.

Why we keep it. A true/false flag cannot answer any of the questions a payment arrives as: which transaction was this, has it already been refunded, did this account pay or was the unlock transferred to it from another one. Those are the questions a refund, a dispute or a support request is made of, and the person asking usually has a transaction number and nothing else. Section 9 says how long these records are kept, and Section 10 says what deleting your account does to them.

4.7 Content reports

If you report a prompt to us, we collect the reason you chose, any note you wrote, and a copy of the prompt's text as it was worded at the moment you reported it. Stored with it are the party's name, the game it was in, your display name, and the host's display name and email address.

That copy is the whole point of the record. Party content deletes itself seven days after the party ends, and a host can rewrite a prompt at any time, so a report that merely pointed at the original would be empty before anyone could read it. A report is therefore kept on a clock of its own, for twelve months, and it outlives the party it is about and the accounts of the people named in it. Section 9 sets that out in full, and Section 10 says what account deletion does and does not do to it.

Reports go to us by email and nowhere else. We do not show a report, or the fact that one was filed, to the host or to anyone else in the party, and nobody can read a report back through the App.

4.8 What we do not collect

We want to be specific about this, because the list is unusually short:

  • No camera or microphone access. The App does not take photos, record video, or record audio.
  • No photo or media library access. We do not read, upload or store your photos.
  • No location data. The App does not request or use device location services, in the foreground or the background. We do not track your location.
  • No contacts access. The App never reads your address book. Guests join a party using an access code, not by us looking through your contacts.
  • No phone numbers.
  • No analytics or behavioural tracking of any kind. Bachlette contains no analytics, crash-reporting, advertising, or attribution software. We do not build advertising profiles, we do not track you across other apps or websites, and we do not use third-party trackers.
  • No sensitive information such as government identifiers, health data, biometrics, racial or ethnic origin, religious beliefs, sexual orientation, or political opinions. Please do not submit this to us.

5. Guests

You can join a party as a guest without creating a full account. As a guest, we collect only the display name you enter and your in-game activity, linked to an anonymous account record and a party access token. We do not collect an email address or password from guests.

Guest display names and party activity are deleted when the party is deleted, seven days after it ends (Section 9). The anonymous account record itself is deleted too, once it belongs to no party at all (Section 9).

One exception, and it is deliberate. If you report a prompt, your display name and everything you wrote in the report are copied into that report, which is kept for twelve months and is not deleted with the party (Sections 4.7 and 9).

6. Information about other people

When you create a party and share an access code, or enter a display name for someone else, you may be providing us with another person's information. Use of the App is voluntary for them, and we use party information only to run the party you have set up.

7. How we use your information

  • Creating and authenticating your account. Account, profile.
  • Running parties and games. Party and game content, profile.
  • Holding a token so we can notify you about your party. Push token, party.
  • Unlocking paid features. Purchase flag, account.
  • Providing customer support. Account, communications.
  • Keeping the Service secure and preventing abuse. IP address, account, device.
  • Receiving, investigating and acting on reports of content. Report, party and game content, profile.
  • Delivering app updates. Update metadata.
  • Complying with legal obligations and enforcing our terms. As required.

We do not use your personal information for advertising, and we do not make decisions about you by automated means alone.

8. How we share information

We do not sell your personal information, and we do not share it for advertising purposes.

With other people in your party. Your display name and your in-game activity, meaning votes, claims and bingo progress, are visible to other members of parties you join, as that is how the game works. Your email address is never shown to other users. A report you file is not: it goes to us, and nobody else in the party is shown it or told it exists.

With service providers. These providers process information on our behalf, under contract, and may not use it for their own purposes:

  • Supabase. Backend: authentication, database, realtime. Involves account, profile, party and game content, push tokens, and IP address. supabase.com/privacy
  • Expo (Expo Application Services). Push notification delivery and over-the-air app updates. Involves push token, device and runtime metadata, and IP address. expo.dev/privacy
  • Google Firebase Cloud Messaging. Push notification delivery on Android, once notifications are switched on. Involves the push token. firebase.google.com/support/privacy
  • Resend. Delivering the email that tells us a content report has been filed. Involves the contents of the report: the copied prompt text, the party and game name, the reporter's and host's display names, the host's email address, and any note. resend.com/legal/privacy-policy
  • RevenueCat. Confirming purchases: telling the App whether your store account holds the unlock, and telling our server when a purchase, refund or transfer happens. Involves your Bachlette account id, the store's transaction identifiers, the product bought and the unlock granted, the price, currency and storefront country the store reported, and device and platform metadata. revenuecat.com/privacy
  • Google Sign-In. Optional sign-in method. Involves email address, name, and profile photo URL. policies.google.com/privacy
  • Apple Sign-In. Optional sign-in method. Involves email address and name. apple.com/legal/privacy

Apple and Google. As operators of the App Store and Google Play, they distribute the App and process the purchase. They take the payment and hold the payment details, and they confirm the purchase to us through RevenueCat. What reaches us is the confirmation and the transaction identifiers, never your card, bank or billing details.

For legal reasons. We may disclose information where we believe in good faith it is necessary to comply with a law, regulation or lawful request; to enforce our Terms of Service; to detect or address fraud, security or technical issues; or to protect the rights, property or safety of our users, ourselves, or the public.

Business transfers. If we are involved in a merger, acquisition, financing or sale of assets, your information may transfer as part of that transaction. We will notify you before your information becomes subject to a materially different privacy policy.

9. Data retention

Party data deletes itself. All party content, meaning the party, its members, prompts, votes, claims and bingo cards, is automatically and permanently deleted seven days after the party ends. This happens without you doing anything.

Parties that are never ended. A party that is created and never ended has no end date for those seven days to run from. If it was started, a daily job deletes it sixty days after it started, together with everything in it. If it has not started yet, it is kept until its host ends it, which starts the seven days above, or deletes their account, because hosts create parties months before the event.

Guest account records. The anonymous account record created when someone joins as a guest is deleted by that same daily job once it is more than a day old and belongs to no party. Their display name and game activity have already gone with the party itself, so nothing of a guest is left behind, unless they filed a content report, which is kept as described below.

Content reports keep their own clock, and it is longer. A report is deleted twelve months after it was filed, by a separate daily job. It is deliberately not deleted with the party it is about: the party goes seven days after it ends, a host can rewrite a prompt before then, and a report tied to either would be gone before it could be acted on, asked about, or shown to a regulator or app store that asked how we handled it. A report holds a copy of the reported prompt's text, the party and game name, the display names of the reporter and the host, the host's email address, and any note the reporter wrote (Section 4.7).

Account data is retained while your account is active, and deleted when you delete your account (Section 10).

Display names in other people's parties. If you were a member of someone else's party and then delete your account, your membership of that party is removed along with the display name you entered and your votes, claims and bingo progress in it. Nothing you entered is left behind for the remaining members to see. Results other members have already seen on their own screens are not recalled.

Backups. We do not run scheduled database backups, so there is no backup copy of your data to outlive a deletion. Party data is short-lived by design, and holding fewer copies in fewer places is part of how that works. Copies may persist briefly in our hosting provider's systems while a deletion propagates through them.

Purchase records outlive the account, and that is deliberate. A record of a purchase, a refund or a transfer (Section 4.6) is kept indefinitely, for tax, accounting and dispute purposes. Deleting your account does not delete these records (Section 10). The link from the record to your profile is removed, but the store's transaction identifiers, the amount, and the account id the purchase was made under all stay, because a record of money that the payer can erase on request is not a record.

10. Deleting your account

You can permanently delete your account at any time from within the App: on the home screen, tap the menu button (the three lines) in the header, then tap Delete account at the bottom of the menu. If you are inside a party, open the party's menu and tap Home first. You can also email [email protected].

Guests do not have an account to delete. A guest joins with an anonymous session, not an account, so Delete account applies to hosts, who create accounts. A guest can leave a party at any time: tap the menu button (the three lines) in the party screen's header, then Leave party. A guest's display name and activity are deleted with the party, and the anonymous session record is deleted automatically once every party it joined has been deleted (Sections 5 and 9).

Deleting your account permanently removes your account record, email address, display name, profile, push tokens, any parties you hosted along with all content in them, and your membership of any party you joined along with everything you entered in it. This is a hard deletion, not deactivation, and it cannot be undone.

If you are hosting a party when you delete your account, that party ends immediately for everyone in it and its content is deleted with it. The App warns you and names the party before you confirm.

Purchase records are not deleted with your account. If you bought the App, the record of that purchase and of any refund or transfer that followed it is kept indefinitely, for tax, accounting and dispute purposes (Section 9). Deleting your account removes the link between the record and your profile, and leaves the record itself. It holds no payment details, because we never had any.

Content reports are not deleted with your account. Two kinds may name you. A report you filed holds your display name and whatever you wrote in it. A report somebody filed about a prompt in a party you hosted holds your display name and your email address. Both are kept for twelve months from the day they were filed (Section 9), and deleting your account removes neither, because a record that the person it concerns can erase on demand is no use for the thing it exists for. If you want a report reviewed, email [email protected].

11. Security

We use measures appropriate to the risk:

  • Encryption in transit. All connections use TLS. App Transport Security is enforced on iOS.
  • Encryption at rest. Data stored in our database is encrypted at rest by our hosting provider.
  • Row-level security. Access rules are enforced at the database level on every table, so users can only read and write the party data they are entitled to.
  • Password hashing. Passwords are stored only as cryptographic hashes.

No method of transmission or storage is completely secure, and we cannot guarantee absolute security. Keep your password confidential and tell us at [email protected] if you believe your account has been compromised.

12. International data transfers

We operate globally and your information may be transferred to, stored in, and processed in countries other than your own, including Australia and the United States, where our update, sign-in and notification providers operate. These countries may have different data protection laws.

For Australian users, we take reasonable steps to ensure overseas recipients handle your personal information in accordance with Australian Privacy Principle 8.

13. Your rights: United States

California residents (CCPA/CPRA). We collect the categories of personal information described in Section 4, for the purposes in Section 7, and disclose them to the recipients in Section 8.

We do not sell your personal information and we do not share it for cross-context behavioural advertising, as those terms are defined under California law. We do not collect sensitive personal information as defined by the CPRA.

You have the right to know what we collect and how we use and disclose it; to request deletion; to request correction; and not to be discriminated against for exercising these rights. Email [email protected]. We verify requests against our records, and accept authorised agents with written proof of authorisation.

Other states. Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana and other states with comprehensive privacy laws have similar rights of access, correction, deletion and portability, and may appeal a refused request by replying to our response.

14. Your rights: Australia

We handle personal information in accordance with the Privacy Act 1988 (Cth) and the Australian Privacy Principles. You may request access to your personal information and ask us to correct it if it is inaccurate, out of date, incomplete, irrelevant or misleading, by emailing [email protected]. We respond within a reasonable period, generally 30 days.

Complaints may be made to us at [email protected]. If you are not satisfied with our response, you may complain to the Office of the Australian Information Commissioner at oaic.gov.au. We will notify affected individuals and the OAIC of any eligible data breach as required by the Notifiable Data Breaches scheme.

15. Notifications

The App may ask your permission to send push notifications, and stores a token for your device if you allow it (Section 4.4). We are not sending any push notifications yet. When we start, they will be about your parties and game activity, and you can turn them off at any time in your device settings.

We send emails about your account, security and material changes to this Policy. These are necessary to provide the Service. We do not send marketing email.

16. Changes to this Policy

We may update this Policy. When we make material changes we will notify you by email or in-app notice before they take effect, and update the date above. Continued use after the effective date constitutes acceptance.

17. Contact us

Bachlette
Email: [email protected]