Privacy Policy
Draft — pending legal review
This is the version currently in force in the Plastic app. It has not yet been reviewed by a lawyer, and it will change.
Version 2026-10-05 · effective 5 October 2026
1. Who we are and what this covers
Plastic runs in-person game nights. You book a seat, we put you at a table with other people, and the app runs the event.
This policy covers the Plastic app. Joined our waitlist on the website instead? That is a separate, much shorter notice about one email address — see the Waitlist Privacy Notice. The two are kept separate on purpose: neither audience should have to read the other's document.
Plastic is operated by NORSECODE CONSULTING, LLC, doing business as Plastic. This policy covers the Plastic mobile app and the services behind it.
NORSECODE CONSULTING, LLC, doing business as Plastic 16041 N Pierce Ferry Road, PMB 185 Dolan Springs, AZ 86441
Privacy and data requests: privacy@playplastic.app General support, and ban appeals: support@playplastic.app
Age: you must be 21 or over. Plastic is not for anyone under 21. This is enforced, not merely stated — a booking is refused unless an identity check has confirmed a date of birth at least 21 years ago.
2. What we collect, and why
2.1 Your account
| What | Why |
|---|---|
| Email address | To sign you in and to contact you about a booking |
| Display name | Shown to the people at your table |
| How you signed up (email, Google or Apple) | To sign you back in |
2.2 Your profile
| What | Why |
|---|---|
| Date of birth | Age eligibility, and age-band matching |
| Pronouns, and whether to show them | Shown to your table only if you choose to show them |
| Gender and who you'd like to meet | Used to build balanced tables |
| What you're looking for from an event | Used to seat you with people wanting a similar kind of event |
| Avatar | Your public face in the app before any photo is shared |
2.3 Your photo, if you add one
A photo is optional. You can use Plastic without one, and nothing about booking, being seated or playing depends on having one.
| What | Why |
|---|---|
| The photo itself | So people you have met can recognise you afterwards. Stored privately — never on a public address |
| The result of an automated check | Every photo is screened before anyone else can see it (see section 4) |
| Whether someone has reported it, and what they said | So a person can look at it |
What we do not keep. A photo is re-saved on upload from the picture itself, which removes everything attached to it — in particular where and when it was taken. Phone photos routinely carry GPS coordinates; a profile photo is often taken at home. We do not want that, so we remove it before the photo is stored rather than promising not to look. | Home ZIP code, and the city and approximate coordinates we derive from it | To show you events near you and to match by neighbourhood |
The coordinates are the centre of the ZIP code you typed, not your address and not your device's location. We look up the ZIP code; we never ask your device where you live.
2.3 Identity verification — what we keep and what Stripe keeps
We verify identity through Stripe Identity. You upload your document to Stripe, not to us.
What Stripe holds: the photograph of your identity document, your selfie, and the extracted document details. Stripe collects these directly from you and holds them; they do not pass through us. We receive only the result and your date of birth.
This section is being finalised with our lawyer.
What we store:
| What | Why |
|---|---|
| Whether the check passed, failed, or is pending | To know whether you may book |
| The date of birth Stripe confirmed | The 21+ rule, and age-band matching |
| Stripe's verification session ID | So a problem can be traced back to Stripe |
| A one-way hash of your document number and issuing authority | So that a banned person cannot simply re-register |
| The reason a check failed, if it did | So we can tell you what to do next |
What we do not store: your legal name, your document images, your selfie, or your document number. The hash is a SHA-256 of your document number combined with a secret value we hold; it cannot be reversed back into the number, and it is used only to compare against a list of banned documents.
2.4 Payment
Payments are processed by Stripe. We never see or store your card number.
We store Stripe's customer reference and a reference to your saved payment method, plus, for each booking: the amount, whether it was paid, cancelled or refunded, and Stripe's payment and refund identifiers.
2.5 Checking in at the venue
When you check in, the app asks your device for its location and sends it to us so we can confirm you are actually at the venue.
We do not store your coordinates. We calculate the distance to the venue and store only:
- whether the check passed;
- how far away you were, in metres;
- if it did not pass, which of two things happened — your device could not provide a location, or you confirmed you were there anyway.
2.6 Notifications
We store a push notification token for each device you sign in on, so we can tell you when your table is set, when it moves, and when an event is cancelled. Signing out deletes the token for that device.
2.7 Photos
(Not yet built. This section describes the design and must be re-checked before the feature ships.)
A photo you add is private by default. It becomes visible to another person only when you choose to share it with them after an event together. Sharing is one-directional: sharing yours with someone does not give you theirs.
2.8 Ratings, blocks and reports
After an event you can rate each person you sat with — happy to sit with them again, no preference, or blocked — and rate the event itself.
- Nobody is shown how they were rated. There is no screen anywhere in the app that shows it, and we do not intend to build one. The only thing another person can ever see as a result of what you choose afterwards is your photo, and only if you chose to share it with them — they are not told what you picked, only that your photo became visible.
- Blocks are silent. The person you block is not told. You will not be seated together again.
- Reports go to our safety team. We store what you reported, the category, your description, and which event and person it concerns.
3. Who sees what
Other people at your table see: your display name, your avatar, and your pronouns if you chose to show them. That is all — unless you have shared your photo with them.
Your photo is seen by nobody until you share it, and then only by the people you shared it with. At the venue itself, everyone is avatars — a photo is something that happens after an event, not at one.
While a photo is being checked, only you can see it. If we cannot use it, it is deleted and nobody ever sees it.
To anyone you have not shared with, a photo you hold looks exactly the same as no photo at all. There is no "locked" marker, and nothing in the app tells them one exists — otherwise "they have a photo but not for me" would itself be information about you.
They do not see: your email, your date of birth or age, your ZIP code or home area, your exact location, how you rated anyone, or whether you blocked anyone.
The venue address is shown only once your table is set, and only to the people seated at it. While you are browsing events you see the area, not the venue.
Our staff can see booking and safety records when investigating a report, a payment problem, or a flagged account.
4. Who we share it with
| Who | What | Why |
|---|---|---|
| Stripe | Payment details; identity documents | To take payment and verify age |
| Supabase | Everything in our database, and your email address | It is our database and authentication provider, and it sends your sign-in code |
| Google Maps Platform | Your home ZIP code | To turn it into the approximate location we match on. Sent from our server, never from your phone |
| Google Cloud Vision | Your photo, if you add one | To check it automatically before anyone else can see it. Sent from our server, never from your phone. Google returns a score and does not keep the image |
| Google, or Apple | That you signed in to Plastic | Only if you choose to sign in with them |
| Expo | Push tokens and notification text | To deliver notifications |
| Our hosting provider | Server data in transit and in logs | To run the service |
Resend delivers email to venues — a date and a party size, to confirm a booking. It receives nothing about the people at the table.
Some photos are also looked at by a person. If the automatic check flags one, or somebody reports it, a member of our staff sees that photo in order to decide. That is the only circumstance in which a photo you have not shared is seen by anyone.
We do not sell your personal information, and we do not share it for advertising.
Law enforcement: only on a valid legal demand — a subpoena, warrant or court order — or where we believe in good faith that someone is in immediate danger.
5. How long we keep things
These are working starting points, for legal confirmation. They are not yet settled. This section is being finalised with our lawyer.
| Data | Kept |
|---|---|
| Account and profile | While your account exists. Deleted within 30 days of you deleting your account, except as below |
| Identity verification record | This section is being finalised with our lawyer. The banned-document hash is intended to outlive the account — otherwise a ban is evaded by deleting and re-registering, which is the one thing it exists to prevent |
| Bookings and payment records | About 7 years, for tax and accounting |
| Safety reports, blocks and bans | Kept as long as needed for safety. After the reporter deletes their account, their identity is minimised — the report survives, the link to a named person does not |
| Check-in records (distance and outcome) | About 12 months |
| Ratings | This section is being finalised with our lawyer. Blocks are intended to be permanent: their whole purpose is to never seat two people together again |
| Push tokens | Until the token stops working, or you sign out of that device |
| Your photo | Deleted immediately when you replace it, remove it, or delete your account — not at the end of a retention window. A photo we cannot use is deleted as soon as that is decided |
Why a photo is the one thing deleted immediately. Everything else above is kept for a reason — tax, safety, evidence. A photograph of your face serves none of those once you have taken it down, so there is nothing to weigh against removing it. The file goes, not just the link to it.
Why a safety report outlives a deleted account. If deleting your account erased reports you had made, deletion would become a way to erase evidence about someone else. The report stays; your name comes off it.
6. Your rights
You can:
- See what we hold about you;
- Correct it — most of it you can edit in the app;
- Delete your account and the personal information attached to it, subject to the retention decisions above — in particular, a safety report you made stays, with your identity minimised;
- Ask us a question about any of this.
Contact: privacy@playplastic.app.
We offer these rights to everyone, wherever you live, rather than only where a law requires them.
This section is being finalised with our lawyer.
7. Security
Access to your data is restricted at the database level: the rules are enforced by the database itself rather than only by the app, so a bug in one screen cannot expose another person's record. Those rules are covered by an automated test suite that runs on every change.
8. Changes
We will update this policy when the app changes. Material changes will be notified in the app before they take effect.
If a breach affects your personal information, we will notify you as required by applicable law.
