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
- Your pairs are private. Your pair records are shown to you and the other person in that pair. Only people we've authorised, when they need to, can open the limited information needed for the reasons in section 7. Our providers and any other recipients are described in sections 8 and 16.
- We collect what Oopsta needs to work: how you sign in, the name you choose and an optional @handle, your birth date to check you're 18 or over (and we keep the month and year), your country, and the thank-yous, oops chits and notes you and your people create.
- The Oopsta app doesn't ask for your phone's GPS or location, or read your contacts. We never sell your information, and we don't use what you write to train AI. We don't show ads.
- Our optional PostHog usage data and Sentry crash reports are off unless you switch them on. Separately, each time Oopsta starts it checks with Expo for an app update, and that switch doesn't control the check (section 4.5). On an iPhone, the check can include a short error message if Oopsta didn't start properly the time before. If you're testing through TestFlight or Google Play, those platforms collect their own information (section 4.10).
- You're in charge: get a free copy of your records, fix your details, or delete your account. Settings covers most of it; for the rest, or for a fuller copy, write to us (section 13).
- Our main database is in Sydney, Australia. Some of our providers are in other countries. Section 8 lists them and section 9 explains where information is handled.
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.
- Privacy questions and requests: privacy@oopsta.com. Our privacy officer for New Zealand and our privacy contact for Australia is our director. You can use this address even if you can't sign in or don't have an account.
- Anything else, including problems with the app: support@oopsta.com
- Safety worries: safety@oopsta.com, or report it in the app.
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.
- How you sign in. Your email address if you sign in with a code, or your Apple or Google account. Apple or Google gives us an account identifier and your email address (Apple may give us a private relay address instead). The app asks Apple only for your email address, not your name. Google sends your name and a link to your profile picture; our sign-in provider stores them, but we don't show them or copy them anywhere else.
- Your name and @handle. The name you choose (it doesn't have to be your legal name), and an @handle if you add one (it's optional).
- Your birth date and country. Right after you sign in, we ask for your birth date to check you're 18 or over. We receive the whole date when you send it, and use it only to check your age. We then keep just the month and year, and if you answer again we compare your answer with them. We also keep the country you live in, the result of the check and the age rule that applied. We fill the country in from your phone's region setting, and you can change it.
- What you've seen and agreed to. Which version of our collection notice you saw, and when you agreed to the Terms and Community Rules: the versions, the time, your app version, and which screen and wording you were shown.
- Guest use. Guest use is switched off during the closed test. If it's on, a guest gets a temporary account with no email address, and a quick "are you a person" check runs through Cloudflare first.
4.2 What you and your people create
- Thank-yous, oops chits and settling up. Who gave what to whom, how many chits, when, and the state of each one (for example, a favour settled). Promises, asks and treat ideas are switched off during the closed test.
- Notes. Short notes (up to 140 characters) on a thank-you, an oops or a settlement.
- Your pairs. Who you're paired with, when the pair started, and the pair's time zone, which is set from the inviting person's phone. If you invite someone, we keep the invite and a scrambled form of its link.
4.3 Information other people give us about you
- The person you pair with. P Square Pty Ltd collects notes and activity records about you from the person you choose to pair with, to provide your shared record and handle the safety and privacy matters explained here. For example, "For the dishes. Legend." on a thank-you they give you. Those notes are part of both people's record. Sections 2, 7 and 8 identify our contacts and recipients; section 13 explains access and correction.
- People who don't use Oopsta. A note might mention someone who isn't on Oopsta, such as a friend at a dinner. We don't ask for this, and we ask everyone to keep notes about what happened, not about other people. If you're mentioned and want to ask us about it, write to privacy@oopsta.com, even without an account.
- Reports. If someone reports something you wrote, we keep the report, its reason and any short note they add.
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
- Notification details. Your phone's push token and your notification choices, including whether your lock screen shows names or a generic line.
- Time zone. We read your phone's time zone so reminders and summaries arrive at a sensible local time.
- Sign-in sessions. For each device you're signed in on: when the session started and was last used, and a short device label (Oopsta's version and iPhone, iPad or Android). You can see your sessions in the app. Our sign-in provider also keeps the IP address for each session.
- IP address. Our servers see your IP address to stop abuse. For that check we keep a scrambled form of it for two days (scrambled doesn't mean anonymous). The separate raw copies are kept by our sign-in provider in its sign-in and security records, and our hosting providers may keep them in their own logs. Section 10 gives the periods.
- If you sign in with Apple. When Apple gives our server a sign-in token, we keep it encrypted and use it to ask Apple to disconnect Oopsta from your Apple ID when your account is deleted. We never use it to sign you in or to read anything from Apple. If Apple gives us no token, or capturing it fails, there is no token to keep.
- Technical safety records. Short-lived records that stop the same tap being counted twice, rate-limit counters, and the state of sign-in codes.
- App updates. Each time Oopsta starts, it asks Expo, our update provider, whether there's an update to the app, so fixes can reach you without waiting for the store. To do that it sends a random number made for this install of Oopsta, whether your phone is an iPhone or Android, the app's version, which update it has and any update that didn't work, and your IP address. The number isn't your account, name or email and isn't linked to them. It stays on your phone until you remove Oopsta. It's still about your phone, so we treat it as personal information. Expo counts installs with it, and shows us totals for each update, such as how many phones got it and how many had trouble. There's no switch for this check, and "Share usage and crash data" doesn't control it. On an iPhone, if Oopsta closed with an error while it was starting, the next check also sends Expo a short technical message about that error (up to about 1,000 characters), whether or not "Share usage and crash data" is on. On Android, a message is sent only if the update system itself failed to start.
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
- The Oopsta app does not request GPS or device-location access or read your contacts. We receive the country, time-zone and technical information described in section 4.
- There is no photo or voice-note sharing feature in the app; support or test feedback may include an image you choose to send.
- We don't show ads, and we don't sell or rent your information to anyone. If we ever add ads, we'll update this policy and tell you in the app before any ad appears. Ads would never give or cost chits and would never appear on the screens you share with the person you're paired with.
- We don't track you across other companies' apps or websites, and there's no advertising identifier in Oopsta.
- We don't use what you write to train AI models. Oopsta's automatic actions are described in section 15, and none of them uses AI. Some providers use their own automated tools to spot spam or abuse (section 8).
- We don't send marketing notifications.
6. Why we use your information
| What we do | What we use |
|---|---|
| Run the private record between you and each person you pair with: thank-yous, oops chits, settling up and your monthly summary | Your account, your pairs, what you and your people create, your time zone |
| Sign you in and keep your account safe | Sign-in details, sessions, IP address, technical safety records |
| Check you're 18 or over, and handle a review if you think we got it wrong | Birth 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 friend | Push token, notification choices, time zone |
| Keep Oopsta kind and safe: screen words that break the Community Rules, handle reports, blocks and appeals | What you write, reports, safety records |
| Answer your questions and requests, including access, correction and deletion | Your account, what you send us |
| Meet legal duties and answer lawful requests | Only what the duty or request needs (section 16) |
| Fix crashes and improve sign-up, only if you switch it on | Usage and crash data (section 4.8) |
| Keep the app up to date and working, and undo an update that goes wrong | The update-check details (section 4.5) |
| Assess and improve the beta app | The 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
- The other person in each pair can see the shared activity and profile information described here: your name, your @handle and what's between the two of you: thank-yous, oops chits, settling up and the notes on them. Oopsta does not display your sign-in email, birth information, country, your other pairs, or who you've blocked, muted or reported to that person through the ordinary pair screen. If you leave a pair, they see that it ended, but nothing says who ended it or when.
- Your @handle. Oopsta has no "find a friend by @handle" search: people pair with you through an invite. Someone filling in a report can name a user by @handle.
- People we've authorised (during the closed test, our director, and one other trusted person we've authorised to give a decision a second look or to help in an incident) can access the limited information needed to handle a report or request, address an actual safety or security issue, or meet a lawful obligation, under restricted procedures.
- Reports. Where Australian online-safety rules protect a reporter's identity, we do not let another user or account holder access it, directly or indirectly, unless the reporter clearly tells us we may. In a pair of two, someone may still infer who reported from what they already know.
- Our service providers store and process information for us (section 8).
- Authorities may receive information only where the applicable law requires or permits disclosure, as section 16 explains.
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.
| Provider | What it does for us | Where it is |
|---|---|---|
| Supabase | Our database, sign-in and server functions | US company. Main database and sign-in records in Sydney, Australia. Server functions and logs may be handled outside Australia |
| Resend | Sends 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 phishing | US company. Emails are sent from Japan; message content and delivery logs are stored in the United States |
| Expo | Passes notifications to Apple and Google, and delivers updates to the app (section 4.5) | United States |
| Apple | Delivers 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 itself | Worldwide |
| Delivers 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 itself | Worldwide | |
| Cloudflare | Hosts 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 check | Worldwide (US company) |
| Hostinger | Our domain names and the oopsta.com website, including visitor logs | Cyprus (EU) |
| Titan (through Hostinger) | Our support, safety and privacy mailboxes | Company in the Cayman Islands; mailbox storage country being confirmed with the provider |
| PostHog | Usage data, only if you switch it on | European Union (Frankfurt, Germany) |
| Sentry | Crash reports, only if you switch it on | US 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:
- with someone you ask us to share it with;
- when the law requires or permits it, or to protect someone from serious harm (section 16);
- if Oopsta moves to another company (section 20).
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:
- United States: Supabase (the company, and server functions that may run there), Expo, Cloudflare, Apple, Google, Sentry's account and settings data, and Resend (message content and delivery logs).
- Japan: Resend's sending region.
- European Union: Hostinger (Cyprus), PostHog (Germany) and Sentry (Germany), the last two only if you switch on usage and crash data.
- Cayman Islands: Titan, the company behind our mailboxes.
- Worldwide: Apple and Google (notifications, sign-in and, if you test through them, TestFlight or Google Play) and Cloudflare (the person check and our web pages).
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.
| Information | How 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 year | While you have an account, so we don't ask again; removed when your deletion completes |
| Notes on thank-yous and oops chits | 12 months after the chit was given, then removed |
| Words on settlements | 12 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 account | The same 12-month periods above. You can ask us to review, hide or remove a note about you, even without an account |
| Your records download | The 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 done | 2 years after it completes or is cancelled |
| Report notes and appeal text | 90 days after the report or appeal is decided |
| Ordinary report and case records | 24 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 Standard | Kept until two years after the end of the calendar year in which the action occurred |
| Requests from authorities and legal holds | The 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 checks | 2 days |
| Notifications waiting to be sent | 14 days after they're created |
| App update checks at Expo | The 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 app | 90 days after they're sent |
| Technical records that stop the same tap being counted twice | The saved reply 7 days; the bare record 12 months |
| Your sign-in sessions | Until 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' logs | Set by the provider. We're confirming the period. |
| Backups | A limited period after information is deleted from our live systems. |
| Apple sign-in token | If we hold one: until your deletion completes, then gone within 20 hours |
| Emails you send us | 2 years after your request is closed, unless we no longer need a particular attachment or ID document, which we remove sooner |
| Financial records | Financial 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 on | Nothing 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 see | We 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 account | 30 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 email | Use 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.
- You can cancel your deletion request during the 29-day waiting period. We complete deletion of your live account by day 30. The limited records in section 10 may remain for their stated lawful purposes and periods, and restricted backups follow their separate schedule.
- What goes: your name (shown as "Deleted user"), your @handle, your sign-in details from your active account, your age-check result, your birth month and year, your country, and the words you wrote: your notes, favour descriptions and invite drafts. Your open items close quietly and no chits move.
- What stays, no longer linked to your account: the amounts, dates and states of what happened between you and each person you paired with, because that's their record too. Remaining shared history may still identify you from context, so we say "no longer linked", not "anonymous". The records listed in section 10 stay for the periods shown there.
- Copies you've shared. Deleting your account doesn't reach copies you or anyone else saved or shared outside Oopsta.
- Sign in with Apple: if we hold a token, we ask Apple to disconnect Oopsta from your Apple ID when your deletion completes, and the token is gone within 20 hours of that.
- Backups clear on the schedule in section 10.
- Before you go, you can download your records (section 13).
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.
- See and download your information. Settings, then Get my records. It's free, once a day. We build a file within about an hour, email you when it's ready, and you download it inside the app (it's a technical file, JSON Lines, which you can save or share with another app; if you'd like a plain-English copy, write to us and we'll help). The download contains the records we still hold and may lawfully provide, including permitted partner notes. It does not restore text already expired or removed and may omit information protected by another person's privacy or safety. The file is normally kept for 7 days after it's built. Once you save or share a copy outside Oopsta, it is outside our deletion controls. Guests can't download a file, so please email us.
- Asking for more. The daily download limit applies only to the self-service file. You can separately request access to personal information we hold about you, including information held for us by providers and our safety records about you. We consider your requested format and the lawful limits. You can contact us even if you cannot sign in or have no account, at privacy@oopsta.com.
- Fix your details. Change your name and @handle in the app. You can undo a chit you gave, or pass one back, inside the time the app shows. We assess requests to correct information about you, including past records. To preserve history, we may retain an original entry with a clearly linked correction or statement where that meets the applicable law. If we refuse a correction, we explain the reason and complaint options and how to request a statement with the record.
- Delete your account (section 11).
- Switch off usage and crash data any time in Settings.
- Choose what shows on your lock screen.
- Ask about a note that mentions you, even if you don't use Oopsta.
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 happens | What it uses | How 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 rule | Section 14 |
| Word screening. If a note contains words the Community Rules don't allow, the app may stop it, or ask "are you sure?" first | The words you type | You 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 words | The report reason, the words reported, the time the report has been open | You 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 device | They reset on their own |
| Quiet closing. An unanswered settlement closes quietly after its time runs out, and no chits move | The state and time of the item | You can make a new one |
| Re-sign-up checks are switched off | Nothing | Not 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.
- Australia: the Office of the Australian Information Commissioner (OAIC), oaic.gov.au
- New Zealand: the Office of the Privacy Commissioner, privacy.org.nz
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.