Good Ole Days: Privacy Policy (DRAFT)
Draft for review. Not legal advice. Written against the Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs). Items marked [TOM] need a decision or a detail before publishing. Publish the final version at
goodoledaysapp.com/privacy. Apple needs this URL for App Store review.
Last updated: [TOM: date]
Good Ole Days ("we", "us") helps groups of friends make plans. This policy explains what personal information we collect, why, who we share it with, and your choices. We've kept it as short and plain as we can.
Who we are: [TOM: legal entity name and ABN, e.g. "Tom Conroy trading as Good Ole Days, ABN …"]. Contact: [TOM: support@goodoledaysapp.com].
1. What we collect
| What | When | Why |
|---|---|---|
| Email address | When you sign in | To sign you in with a one-time code and to contact you about your account |
| First name | When you sign in | So your friends know who invited them and who's in |
| Crews and plans: crews you're in, plans you send, and your answers (in / maybe / can't) | As you use the app | This is the service itself. Your crewmates see it |
| Interests you pick | Onboarding | To suggest ideas you'll like. Stored on your device [TOM: and in your profile once crew-aware dealing ships] |
| Age | Onboarding | To confirm you're 18+ and to suggest things you're likely to enjoy. Your exact age stays on your device. Only an age range (e.g. 35–44) is saved to your profile, so your crew's suggestions suit the group |
| Approximate location | Only if you allow it | To suggest ideas within the distance you choose. Used on your device. [TOM: confirm it's never sent to our servers, or update this line once local events ship] |
| Push notification token | Only if you allow notifications | To send invites and "It's on" alerts |
| Usage and crash data: screens viewed, taps on key buttons, device model, OS version, crash reports | Automatically | To fix bugs and understand which features help people actually meet up |
What we don't collect: your contacts, your photos, or the contents of your calendar. When you say yes to a plan, we add an event to your calendar. On iOS 17 and later we ask for "add events only" access, so we can't read your calendar at all.
We don't collect sensitive information (as defined in the Privacy Act), and we ask you not to put any in plan names or crew names.
2. How we use it
- To run the app: sign-in, crews, plans, answers, notifications and calendar events.
- To improve the app: aggregated usage data and crash reports.
- To contact you about your account and important changes to the service.
- Marketing emails go out only if you've opted in (for example on our waitlist), and every one has an unsubscribe link (Spam Act 2003).
We don't sell your personal information, and we don't use it for advertising.
3. Who can see it
- Your crewmates can see your first name, the crews you share, and your answers on plans in those crews.
- Service providers that host or process data for us, under contract:
| Provider | What for | Where data is stored |
|---|---|---|
| Appwrite Cloud | Accounts, crews, plans, answers | [TOM: region chosen, e.g. Sydney, Australia] |
| PostHog | Product analytics | [TOM: US or EU region] |
| Sentry | Crash reports | United States |
| Apple Push Notification service / Firebase Cloud Messaging | Delivering notifications | United States |
| [TOM: email provider, e.g. Resend] | Sign-in codes and account emails | [TOM] |
Some of these providers store data outside Australia (APP 8). We take reasonable steps to make sure they handle it consistently with the APPs, including choosing providers with strong security practices and contractual privacy commitments.
- When required by law, for example a valid request from an Australian enforcement body.
4. Keeping it safe
Data is encrypted in transit (HTTPS). Access is limited by the app's permissions: only your crew can read crew data, and only our server code can write plans and answers. No system is perfectly secure. If a data breach is likely to cause you serious harm, we'll tell you and the OAIC as required by the Notifiable Data Breaches scheme.
5. How long we keep it
We keep your account data while your account is active. If you delete your account, we delete your profile and your answers within 30 days, and remove you from your crews. Plans you hosted are deleted along with the answers on them, and you're removed from other people's invite lists. [TOM: confirm that deleting hosted plans (rather than anonymising them) is what you want, because crewmates lose those plans too.] Backups roll off within [TOM: e.g. 35] days. Analytics and crash data are kept for up to [TOM: e.g. 12] months.
6. Your choices and rights
- Access and correction: you can see and edit your name in the app, or email us for a copy of your information.
- Delete your account: in the app, go to Crew → Delete account, or email us.
- Notifications, location and calendar can be turned off at any time in your phone's settings.
- Complaints: email us first and we'll respond within 30 days. If you're not happy with our response, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au).
7. Age
Good Ole Days is for people aged 18 and over. We don't knowingly collect information from anyone younger. If you think someone under 18 has signed up, contact us and we'll delete the account.
8. Changes
If we make a significant change, we'll tell you in the app or by email before it takes effect.