Privacy Policy

Version: 2026-11-19 · Applies from: 2026-11-19 · Status: interim draft, checked by an AI legal agent, not yet reviewed by a lawyer; we'll tell you when the final version is ready

Oopsta is a light, warm way to say thanks between two people who know each other. Oopsta uses chits, and chits are just for fun. This policy explains, in plain words, what information we collect, why, who can see it, how long we keep it, and what you can ask us to do. If anything here is unclear, write to us and a person will answer.

1. The short version

2. Who we are and how to reach us

Oopsta is run by P Square Pty Ltd (ABN 81 168 457 967), Victoria, Australia. In this policy, "we" and "us" mean P Square Pty Ltd.

We handle personal information under the Australian Privacy Principles and New Zealand's Privacy Act 2020, where they apply.

3. Who Oopsta is for

Oopsta accounts are for adults aged 18 or over in Australia or New Zealand. During setup we process limited information to check eligibility and, where needed, review an age decision. Section 14 explains what happens when we identify an under-age account. Kids' jars, where they're switched on, are explained in section 4.11; children never have accounts.

During our closed test, people join by personal invitation only, and the first test is in Australia only.

Oopsta isn't made for children and doesn't offer child accounts. A note or report written by an adult could still mention a child; section 4.9 explains how we handle that.

4. What we collect

4.1 When you set up your account

We save sign-in and age-check information during setup, before you agree to the Terms and Community Rules.

4.2 What you and your people create

4.3 Information other people give us about you

4.4 Safety tools you use

Reports you make (a reason and an optional short note), people you block or mute, breathers you take, and anything you send us when you ask us to look at a decision again. When we act on a report, we keep a record of what we did and why.

4.5 Your device and technical details

4.6 If you email us

Your email address, your name if you include it, whatever you write, and anything you attach, such as a screenshot. Please don't send ID documents unless we ask, and please never send card details. Section 10 says how long we keep it.

4.7 If you buy something

Purchases aren't switched on yet.

4.8 Only if you switch on "Share usage and crash data"

This switch is off until you turn it on, and you can turn it off any time in Settings. It controls our optional PostHog and Sentry collection only. When it's on, we also collect which steps you complete, your device model, operating system version, locale, time zone, app version, IP address and crash stack traces. These go to PostHog and Sentry (section 8). The steps are linked to a scrambled id, not your name, but that id is still about you, so we treat it as personal information. Turning the switch off stops new collection; section 10 says what happens to what was already sent.

4.9 Private or sensitive details

Please leave out unnecessary health, sexual, religious or other sensitive details about yourself or anyone else. If we receive them, we assess whether we may lawfully collect and keep them, and may remove or redact them. We limit access and retain information we lawfully need only for its applicable purpose and period, including necessary safety or legal handling.

4.10 If you test Oopsta through TestFlight or Google Play

During the closed test you may get Oopsta through Apple's TestFlight or a Google Play closed track. Apple and Google run these testing programs and have their own beta data collection, which the "Share usage and crash data" switch does not control. They collect testing information automatically, such as crash logs and usage data. Any feedback or screenshots you choose to send through the beta app go to them too. Anything you send us directly, such as an email, comes to us from you (section 4.6). We look at what they show us in their consoles only to assess and improve the beta, as their terms allow, and we don't copy it out of those consoles. Section 6 gives the purpose; sections 13 and 19 explain your access, correction and complaint options.

Later in the test you may instead get Oopsta from the App Store or Google Play, with an invite code. Apple and Google then handle what they collect as store operators under their own privacy policies.

4.11 Kids' jars

Kids' jars aren't switched on for testers yet.

5. What we never collect, and what we never do

6. Why we use your information

What we doWhat we use
Run the private record between you and each person you pair with: thank-yous, oops chits, settling up and your monthly summaryYour account, your pairs, what you and your people create, your time zone
Sign you in and keep your account safeSign-in details, sessions, IP address, technical safety records
Check you're 18 or over, and handle a review if you think we got it wrongBirth date (only for the check), the result of the check, country
Tell you about things that happened in your account and pairs, like a thank-you from a friendPush token, notification choices, time zone
Keep Oopsta kind and safe: screen words that break the Community Rules, handle reports, blocks and appealsWhat you write, reports, safety records
Answer your questions and requests, including access, correction and deletionYour account, what you send us
Meet legal duties and answer lawful requestsOnly what the duty or request needs (section 16)
Fix crashes and improve sign-up, only if you switch it onUsage and crash data (section 4.8)
Keep the app up to date and working, and undo an update that goes wrongThe update-check details (section 4.5)
Assess and improve the beta appThe beta-testing information and feedback made available to us through TestFlight or Google Play, used only as their terms permit (section 4.10)

We use your information only for these purposes, for purposes directly related to them that you'd reasonably expect, or where the law requires or allows it. If we ever want to use it for something new, we'll tell you first and, where the law requires, ask you. A change to this policy does not itself authorise a new use. We assess any proposed change under applicable privacy law and obtain any specific permission that is required before that use.

7. Who can see what

8. Who we share it with

We use the providers below to operate Oopsta. Some process information on our behalf; others also handle specified information for their own purposes. Our list describes the actual service, information involved and known processing locations. We also disclose information in the circumstances explained below.

ProviderWhat it does for usWhere it is
SupabaseOur database, sign-in and server functionsUS company. Main database and sign-in records in Sydney, Australia. Server functions and logs may be handled outside Australia
ResendSends sign-in codes and emails with links that open your records screen in Oopsta. A sample of emails is checked by automated tools to detect spam and phishingUS company. Emails are sent from Japan; message content and delivery logs are stored in the United States
ExpoPasses notifications to Apple and Google, and delivers updates to the app (section 4.5)United States
AppleDelivers notifications to your phone; Apple sign-in if you use it; TestFlight if you test there. For sign-in, TestFlight and the store, Apple acts under its own privacy policy for what it holds itselfWorldwide
GoogleDelivers notifications to your phone; Google sign-in if you use it; Google Play testing if you test there. For sign-in and Play, Google acts under its own privacy policy for what it holds itselfWorldwide
CloudflareHosts our oopsta.app web pages; the "are you a person" check when guest use is on, including IP address and technical signals. Cloudflare also uses the person-check signals to improve that checkWorldwide (US company)
HostingerOur domain names and the oopsta.com website, including visitor logsCyprus (EU)
Titan (through Hostinger)Our support, safety and privacy mailboxesCompany in the Cayman Islands; mailbox storage country being confirmed with the provider
PostHogUsage data, only if you switch it onEuropean Union (Frankfurt, Germany)
SentryCrash reports, only if you switch it onUS company. Crash data stored in the European Union (Frankfurt, Germany); some account, usage and settings data stays in the United States

Some providers also use limited information for their own purposes, for example Cloudflare uses the person-check signals to improve that check.

We may also share information:

9. Where information is handled

Our verified core database location and the other places where information is handled are listed below. Processing location can differ from a provider's corporate address. We identify known countries where practicable and keep the provider information current. Your account and your pairs' records are kept in our main database in Sydney, Australia. Parts of the service, such as sign-in, emails, notifications, records exports and support, may be handled outside Australia. The places are:

We assess overseas handling under the privacy laws that apply to us. We use appropriate contractual, technical and organisational protections for providers acting for us. Where Australian cross-border disclosure rules apply, we take the required reasonable steps or rely on an applicable legal exception. Where New Zealand's overseas-disclosure rules apply, we use an applicable safeguard or other lawful ground. Acknowledging this policy does not waive those protections.

10. How long we keep it

We use the periods below for their stated purposes. Some are operating choices and some apply only to particular legal records. We review whether information is still needed and delete it when its lawful purpose and any specific retention duty end. A preservation requirement affects only the information and period it covers. Age-check information has the separate limits described in section 14.

InformationHow long
Your account details (name, @handle, sign-in email, country)While you have an account. Removed from your active account when your deletion completes (section 11)
Age-check result (that you passed, when, the country and the age rule), and your birth month and yearWhile you have an account, so we don't ask again; removed when your deletion completes
Notes on thank-yous and oops chits12 months after the chit was given, then removed
Words on settlements12 months after the item closes, then replaced with "[text expired]". Items under a legal hold wait until the hold ends
Chit history (who, how many, when, what state)Part of each pair's shared record. If you delete your account, it stays with the other person, no longer linked to you. When both people's accounts have been fully deleted (not just when a pair ends), the whole pair's history is deleted 30 days later
Notes the other person wrote about things between you, after you delete your accountThe same 12-month periods above. You can ask us to review, hide or remove a note about you, even without an account
Your records downloadThe file: normally 7 days after it's built. A fingerprint of it, so we can confirm a file came from us: 2 years. Once you save or share a copy outside Oopsta, it is outside our deletion controls
Record of what you agreed to (Terms, Community Rules, notice versions)6 years after your account is deleted
Record that you asked for deletion and that it was done2 years after it completes or is cancelled
Report notes and appeal text90 days after the report or appeal is decided
Ordinary report and case records24 months after the report is resolved. Records behind a current suspension stay while it lasts
Records of actions to comply with the applicable Australian RES StandardKept until two years after the end of the calendar year in which the action occurred
Requests from authorities and legal holdsThe record of the request: 2 years after it closes or the hold is lifted, unless an order or law sets a longer period. Anything preserved under a real order or law stays only for the fields and time that order or law covers
Word-screening flags (no copy of your words)13 months after the note
Scrambled IP addresses, rate-limit counters, sign-in code checks2 days
Notifications waiting to be sent14 days after they're created
App update checks at ExpoThe random number stays on your phone until you remove Oopsta. Deleting your account doesn't change it, because it isn't linked to your account. Expo's own records of the checks: set by Expo. We're confirming the period.
Messages to you about your account inside the app90 days after they're sent
Technical records that stop the same tap being counted twiceThe saved reply 7 days; the bare record 12 months
Your sign-in sessionsUntil you sign out of that device, the session expires, or your account is deleted
Our sign-in provider's security log (includes IP addresses)Set by the provider. We're confirming the period.
Our hosting providers' logsSet by the provider. We're confirming the period.
BackupsA limited period after information is deleted from our live systems.
Apple sign-in tokenIf we hold one: until your deletion completes, then gone within 20 hours
Emails you send us2 years after your request is closed, unless we no longer need a particular attachment or ID document, which we remove sooner
Financial recordsFinancial records required under Australian company law are kept for seven years after the transactions they cover are completed. Other tax records are kept for the period required by the tax rules applying to that record. We do not retain unrelated profile or message content as a tax record
Usage and crash data, if you switched it onNothing is sent in this test yet, even with the switch on: the collection behind it isn't connected. Once it is, this row will give the periods. Turning the switch off doesn't by itself delete what was already sent
TestFlight and Google Play testing information we can seeWe look at it in the consoles only and keep no copies. Apple and Google hold their own copies under their own policies
A locked under-age account30 days after it's locked; within 24 hours if the birth date shows someone under 13. A review pauses only that account's automatic deletion, and it doesn't stop other clean-up (section 14)
A guest account that never adds an emailUse ends after 7 days; the account is removed after another 30 days. Guest use is off in the closed test.
An account where setup was never finished (no agreement, no name, no pair)If setup is not completed, we retain only information still needed for the specified setup, security or other lawful purpose and delete it when that purpose ends

Sometimes we must keep information longer. If the law requires us to keep some information, for example under a court order, we may delay deleting it until that duty ends. We'll keep only what the duty covers.

11. Deleting your account

You can delete your account any time: Settings, then Delete my account. It's also on the screen you see if your account is locked.

12. When a pair ends

Either of you can leave a pair without asking the other person. Leaving a pair does not itself delete its history. The retention, account-deletion and privacy-rights rules in sections 10, 11 and 13 still apply. You can request your information, subject to the lawful access limits explained there. Some in-app reporting options close after a pair ends. You can still report a person where that option is available, or contact safety@oopsta.com about a concern, including one you couldn't safely report earlier. We can assess only information available to us. The other person sees that the pair has ended, but gets no notification, and nothing says who ended it or when.

13. Your choices and rights

You can do most things yourself in the app, and it's free.

How we answer emailed requests. We'll confirm we've received it, check it's really you in the lightest way that works (usually by replying to the email on your account, or asking you to do it in the app), and never ask for ID documents or a selfie unless we truly need them. If you use Apple's Hide My Email, you don't need to write from your Apple address: ask for a review in the app while you're signed in. For Australian access and correction requests, we respond within a reasonable period, and we aim for 30 days. For requests governed by New Zealand's Privacy Act, we respond as soon as reasonably practicable within the applicable statutory limit (for access and correction decisions, 20 working days). If that Act permits an extension, we notify you within 20 working days with the reason, revised period and how to complain. We provide information or make an agreed correction without undue delay. Requests are free.

When we might hold something back. We withhold information only on a lawful ground. We consider partial access, redaction or another safe form of access where the law permits. For access governed by New Zealand law, we must not give access if we have reasonable grounds to believe the request is made under threat of physical or mental harm. We verify identity and authority and use appropriate procedures to deliver information only to the proper recipient. We give a written decision with reasons and complaint options, subject to legal limits on what may be explained.

14. Age

Oopsta is for people 18 and over. Right after you sign in, we ask for your birth date. If it shows you're under 18, we lock the account, so it can't be used to create or join a pair. We clear the birth month straight away and keep your sign-in details, the country you chose, the fact that the account is locked, the age rule that applied and a short technical record of the check (and, for a birth date showing someone under 13, a marker that sets the 24-hour deletion). We delete the account automatically 30 days later, or within 24 hours if the birth date shows someone under 13. You can still email us for your information or delete the account from the locked screen.

We don't keep the day of your birth date after the check. If you're 18 or over, we keep the month and year while you have an account, so we can compare them if you answer again (section 10). Apart from that, we keep only the limited decision or current-review records needed for the separately stated purpose and period. A review does not stop unrelated deletion.

If you think we got it wrong, contact us before that date and a person will look at it. A review pauses only your account's automatic deletion. We reply within 30 days. If your request also asks for access to or correction of your information, the time limits in the privacy law that applies to you apply.

If we learn in another way that someone using Oopsta is under 18, we'll lock the account and follow the same steps.

15. Automatic actions

No AI makes decisions about you. Some actions happen automatically, using the information described below. Automated screening, temporary visibility restrictions, account eligibility and expiry have different triggers and effects. We explain the available review route for each.

What happensWhat it usesHow to ask for a person to look
Age check. A birth date under 18 locks the account (section 14)The birth date you give, your country and the age ruleSection 14
Word screening. If a note contains words the Community Rules don't allow, the app may stop it, or ask "are you sure?" firstThe words you typeYou can rewrite it. Write to us to ask about a decision
Hiding reported words. If you report a threat or self-harm in eligible words the other person wrote in your pair (such as a note on a chit, or the words on a favour), those words are automatically hidden from your view. Reports of untrue things about you, or pressure or control, automatically hide eligible words if the report is still open after 72 hours. This does not mean a person has reviewed the report. Reports about a person, an invite or a pair rule do not automatically hide words; other report reasons do not use these automatic hides. The author can still see their wordsThe report reason, the words reported, the time the report has been openYou can ask us to look at a decision about your words or report
Limits. Daily limits on how many chits you can give, the time you have to undo or pass back a chit, and short waits after too many tries (for example, wrong sign-in codes)Counts and times for your account or deviceThey reset on their own
Quiet closing. An unanswered settlement closes quietly after its time runs out, and no chits moveThe state and time of the itemYou can make a new one
Re-sign-up checks are switched offNothingNot applicable

16. Requests from authorities

We assess each request and disclose only information supported by an applicable legal basis. A request from an authority does not by itself entitle it to your information. Where a binding preservation requirement applies, we restrict it to the information and period it covers. We tell you about requests concerning you unless law, an order or a properly assessed safety risk prevents that notice.

Applicable laws can require specific notifications about child sexual exploitation or pro-terror material. We assess the relevant conditions and disclose only to the appropriate recipient on a lawful basis.

17. Keeping it safe, and if something goes wrong

We use appropriate technical and organisational safeguards and limit access to people who need it. They include encryption in transit, strict rules in our database so each person can only reach their own pairs, encrypted storage of the Apple sign-in token, short lifetimes for codes and links. Your notes are encrypted in transit but not end-to-end, so our systems can read them. No system is perfectly secure, so we also watch for problems and have a plan to respond.

We assess suspected privacy breaches promptly. If notification is required, we notify the relevant privacy regulator or regulators and affected people as soon as practicable, using public notice where the law permits or requires it. We explain what happened, the information involved, our response and steps people can take, subject to applicable legal exceptions.

18. Notifications and emails we send

We send factual service messages about your account and activity in your pairs, such as sign-in codes, requested record links and a thank-you notification. By default, your lock screen shows a generic line, not names or notes. We do not send marketing emails or marketing push notifications. You can manage optional notifications in Settings.

19. Complaints

If you are unhappy with how we handle personal information, contact our privacy contact at privacy@oopsta.com, even if you have no account. We acknowledge your complaint, investigate it and aim to respond within 30 days.

If you are dissatisfied with our response or cannot resolve the matter with us, you may contact the relevant privacy regulator. This does not limit your rights to complain.

Reports about something said or done in the app follow the Community Rules; they're handled separately from privacy complaints.

20. If Oopsta moves to another company

If the business is reorganised or sold, we assess any proposed disclosure or transfer under the privacy laws that apply. We limit information to what is necessary and use appropriate confidentiality and security safeguards. If another company will become responsible for your information, we explain the change and its contact details and provide any notice or consent process required by law. Any new use must have a lawful basis.

21. Changes to this policy

When we change this policy, we'll update the version date at the top. Before a change that matters takes effect, we'll tell you in the app and explain it in plain words; if you can't sign in or have left, we post the change on oopsta.app and email the address we hold where we practicably can. We'll never treat simply using Oopsta as agreement to a new use of your information; where the law needs your agreement, we'll ask for it. A policy update does not itself authorise a new use or disclosure of information. We assess changes under the privacy laws that apply and obtain any specific permission required before the changed handling. A new version doesn't restart an existing deletion clock.