Privacy Policy

Version 3.9  ·  Effective 27 October 2026  ·  Operated by Conesworth Limited (New Zealand)

This Privacy Policy explains what information JoyR1der collects, how we use and share it, how long we keep it, and — importantly — the technical measures we take to verify age and keep minors off the Service (JoyR1der's 18+ account requirement). Please read it alongside our Terms & Conditions.

Who we are. JoyR1der is owned and operated by Conesworth Limited, a company incorporated in New Zealand (company number 1862936), registered office 16 Rautawhiri Road, Helensville 0800, New Zealand, trading as “JoyR1der” (“JoyR1der”, “we”, “us”, “our”). We are the “agency” responsible for your personal information under the New Zealand Privacy Act 2020, and the data controller for users in the EU/UK. Our Privacy Officer is Tim Schliebs, whom you can reach at legal@joyr1der.com (section 14).
Test environment (test.joyr1der.com). While the Service runs at test.joyr1der.com it is a test / preview environment. Data you enter there (your test account, content, activity and complimentary “test” Clicks) is used only to operate and evaluate the test Service and will not be carried over to the live (production) Service — you will register again on the live site. Test data may be reset or deleted at any time as part of testing. If we offer testers Bonus Clicks on the live Service, we may retain a minimal record needed to identify eligible testers and apply that offer. All other handling described in this Policy applies equally to the test environment.

Contents

★ Test environment (test.joyr1der.com)
1. Information we collect
2. How we use your information
3. Our lawful bases
4. How we share information
5. We do not sell your data
6. Where your data is held
7. Age assurance — the 18+ account requirement
8. Safety & our moderation model
9. How we protect your information
10. How long we keep information
11. Your rights & choices
12. Cookies & local storage
13. Changes to this policy
14. How to contact us

1. Information we collect

We collect only what we need to run the Service, keep it safe, and meet our legal obligations. The main categories are:

CategoryExamplesSource
Account & profileDisplay name, username, avatar and gallery images, date of birth (stored encrypted), derived age band, gender (optional), your chosen privacy, notification and marketing-email preferences, and a record of each version of our Terms you have accepted and when.You, at sign-up and in Profile settings
Contact detailsEmail address and (if provided) phone number. These are held in a restricted, access-controlled store separate from your public profile.You
Content you createLive video/audio streams, event recordings, chat and direct messages, posts, comments, images you upload, tips and reactions.You, as you use the Service
Financial & transactionYour Click balances and a double-entry ledger of purchases, earnings, payouts, refunds and gifts. We do not collect or store your card number. Card entry and identity checks are handled by Stripe, and App Store and Google Play purchases by Apple and Google. Host payout details (payouts are currently made by PayPal) and tax details are handled directly by Trolley, our payout provider; we keep the Trolley recipient ID that links your account to it.You (via Stripe, Apple, Google and Trolley); the Service’s ledger
Age & identity verificationA “liveness” selfie — three photos taken while you follow on-screen prompts — analysed automatically to estimate your age and confirm you are a live person; camera frames checked for age (see “Age checks on camera” in section 7); and/or a government-ID check handled by Stripe. The photos and frames are not kept. We keep the result: pass or refer, the age band, its certainty, the method and the date; your consent record; and, where a check leads to a further step (a government-ID check, or a staff or moderator review), the estimated age range. For an ID check we keep the outcome, your age in years where it was needed to settle your age, and a one-way hash of the name and date of birth on the ID, used only to recognise a banned person who returns.You, and our verification providers
Device & technicalA push-notification token, IP address, device/browser type, and anti-abuse signals (e.g. from Google App Check / reCAPTCHA). We do not embed third-party advertising or analytics trackers.Your device
Approximate locationOnly if you turn location sharing on. It is deliberately imprecise: your device moves it by up to a distance you choose (500 metres unless you change it) before it is sent.Your device (opt-in)
InterestsInterests you pick, and interests we infer from the events you join and from what you browse, watch, save, search for and dismiss (see “Personalisation and ads” in section 2).You, and your activity on the Service
Safety & moderationReports you make or that are made about you, moderation decisions, appeals, and evidence attached to a report.You and other users; our moderators

We do not knowingly collect more sensitive categories of data except where you provide it for age/identity verification. This includes facial images (biometric data) from the selfie, from camera frames and — once that check is switched on — from images and videos hosts upload as content, used to estimate age; they are not kept — except a frame flagged as possibly showing a child, which is kept privately as safety evidence (section 7) — and are never used for advertising, profiling or identification. The selfie is optional — you can always choose a government-ID check instead, anywhere; the camera checks apply to whoever is on camera while broadcasting.

2. How we use your information

Personalisation and ads

We build an interest profile for you: content categories you pick, plus categories we infer from the events you join and from what you browse, how long you watch, what you save or search for, and what you dismiss, with older activity counting for less over time. We use it to choose what is recommended to you and the order of people and posts, to match you with ads and research studies, and to count interest audiences for advertisers and researchers (who see only totals, never for fewer than 25 people). Ads can also be aimed at age group, at gender if you gave one, and at an area of at least 3 km around a point, using your approximate location only if you share it. We never use your identity documents, biometric data or messages for ads. You can turn all of this off with the “Personalise what I see” switch in your Profile settings: we then stop using anything we have inferred about your interests, and you only get ads and research invites that are not aimed at an interest.

3. Our lawful bases

Under the New Zealand Privacy Act 2020 we collect, use and disclose personal information in accordance with the Information Privacy Principles. If you are in the EU/UK, we rely on: performance of our contract with you (to provide the Service); your consent (e.g. optional location sharing, marketing); our legitimate interests (safety, fraud prevention, running our business); and legal obligation (financial records, child-safety reporting). Where we rely on consent you may withdraw it at any time.

4. How we share information

We share personal information only with the service providers (“sub-processors”) that help us run JoyR1der, and only as needed. Our current sub-processors are:

ProviderPurposeWhat is shared
StripePayments (web card purchases) and age/identity verification (Stripe Identity)Your user ID, purchase amounts, and — direct to Stripe — your card and identity details (we never receive your card number)
TrolleyHost/creator payouts (currently paid by PayPal) and payout tax forms (W-8/W-9)Your name, email and country, and — direct to Trolley — your payout and tax details (we never receive your PayPal or bank details)
Google / Firebase (Google Cloud)Sign-in, database, file storage, push notifications, bot/abuse protection, hosting, and translating text you ask the app to translate (Cloud Translation)Account data, content, device push token and what each notification says (for an incoming call or ride request: the caller’s or requester’s name, username, profile picture link and the event title), abuse-protection signals, and the text sent for translation (not the username or name shown beside it; an @mention or name inside the text is sent as written)
LiveKitReal-time video/audio streaming transport, and producing event recordings when a host, co-host or moderator records (or our staff record) a streamYour user ID and the live media of streams you take part in; a recording is written straight to our own private storage
SendGrid (Twilio)Sending transactional and notification emailYour email address and the message content
AppleiOS call notifications (APNs) and App Store in-app purchases (Apple takes the payment)A device push token and, for an incoming call or ride request, the caller’s or requester’s name, username, profile picture link and the event title shown on the alert; purchase receipts (validated offline; no data is sent to Apple)
Google PlayGoogle Play in-app purchases (Google takes the payment) and checking themThe purchase token for an Android purchase
Amazon Web Services (Amazon Rekognition)Age and liveness from selfies and camera frames; explicit-content detection on live preview images; staff age checks on recordingsThe image or frame, sent for analysis. JoyR1der does not store it, and Amazon does not keep these images or use them to improve its services
TypeSafe (typesafe.ai)Automated text checks on posts, comments and chat messages (and on descriptions of uploaded content) that flag possibly harmful ones for review and can hide or blur them (section 8), and search / recommendation matchingThe text being checked
AnthropicSummarising app error reports, the feedback you send us and screen-usage totals, so we can prioritise fixesError reports grouped by type (no user IDs; email addresses and long numbers removed from the error text), the text of feedback with the screen, app version and platform it came from (not your name, username or screenshot), and how often each screen was viewed
OpenStreetMap / NominatimDisplaying maps and looking up place names, from your deviceThe map area you view, a place name you search for, or the location you type on your profile or event form and look up on the map (sent when you press search or the find-on-map button), and, to name your town, your position rounded to about 1 km

We may also disclose information: (a) to law enforcement, regulators or child-safety bodies (how we handle their requests is set out in our Law Enforcement Guide) (including New Zealand’s Department of Internal Affairs and, where a report has a US nexus, the US National Center for Missing & Exploited Children) where we are required to or where it is necessary to protect a child or prevent serious harm; (b) to professional advisors; and (c) as part of a business sale or reorganisation, subject to this policy. We require our sub-processors to protect your information and use it only for the purposes above.

Advertisers

Advertisers on JoyR1der never see who viewed or tapped their ads. Audience sizes they see are totals, and never for groups of fewer than 25 people. Two things are shared with an advertiser only when you choose to:

When you delete your account, we remove your name, email and note from every lead you sent and remove your account from every offer code you hold; the advertiser keeps only the fact that a lead or code existed and what it was charged. Copies an advertiser already saved outside JoyR1der are theirs to manage — ask them directly.

Some kinds of ad, such as alcohol or political ads, are allowed in some countries and not others. To decide which ads may be shown to you, we work out which countries you are likely to be in from the country in your profile, your shared location if you share it, your time zone, and your IP address. The IP address is looked up in DB-IP’s country database, which runs on our own servers, so your IP address is not sent to DB-IP (IP geolocation by DB-IP, licensed under CC BY 4.0). We work this out each time an ad is chosen and don’t keep the result. An ad of that kind is shown to you only if it is allowed in every one of those countries; if we can’t tell where you are, you see only general ads.

5. We do not sell your data

We do not sell your personal information, and we do not share it with data brokers or third-party advertising networks for their own use. JoyR1der contains no third-party analytics, telemetry or ad-tracking SDKs. We earn money from Click purchases, platform fees and advertisers who buy space on our own system — not from selling your data.

6. Where your data is held

JoyR1der runs on Google Cloud infrastructure located in the United States, and several of our providers (Stripe, LiveKit, SendGrid, Apple, Amazon Web Services, TypeSafe, Anthropic) are US-based. By using the Service you understand that your information is transferred to and processed in the United States and other countries, which may have different data-protection laws than your own. We take reasonable steps, and use providers with recognised safeguards, to protect information that is transferred internationally.

7. Age assurance — the 18+ account requirement

Our promise. You must be 18 or older to hold a JoyR1der account. We do not knowingly allow anyone under 18 on the Service, there are no child or guardian-managed accounts, and we verify age with technical checks that are enforced in our server code and “fail closed” — if we cannot confirm you are an adult, interactive features stay locked.

Minimum age

You must be at least 18 years old to create an account or use the Service. Our sign-up screens will not accept a date of birth under 18, and there is no mechanism for anyone under 18 to hold or be given an account.

How we verify age

Age is not taken on trust. Verification is layered:

Age checks on camera

Because a different person can sit in front of a verified account’s camera, we also check the age of whoever is on camera:

Frames go to Amazon Rekognition and are not kept. We keep what a check led to: after an under-18 read, the required government-ID check; for a staff or moderator check, its outcome and the estimated age range, which only our staff can see and which we delete 30 days after the event ends (or when the account is deleted, if sooner). An under-18 read can stop the broadcast or the camera and require a government-ID check. Someone who has already passed a government-ID check is not scanned when they turn a camera on in someone else’s event; on their own stream — at go-live, or at their first camera-on if they went live without one — an under-18 read blocks the stream or turns the camera back off and goes to our staff for review instead (and if that check can’t run on a camera frame, the go-live waits, or the camera stays off, and you can try again). The selfie and the checks on you rely on your consent to the biometric release below (how and when it is required is explained there). The age part of the live safety check looks at every face in the preview image of a live stream — whoever is on camera. Once we enforce the release, nobody can go live or turn a camera on in an event without having accepted it, so everyone it looks at has. Private calls with friends and research sessions are not broadcasts: they don’t ask for the release and are never age-scanned; its explicit-content part is not a face scan and runs on every stream. A staff age check on an event recording looks at everyone in the sampled frames and, once we enforce the release, runs only when everyone who could appear on camera in that event — the host, co-hosts, the event’s moderators and every rider allowed on camera or in a private call — has accepted it. The one exception to “not kept”: a frame flagged as possibly showing a child is kept privately as safety evidence (up to 6 per stream; for a suspected child-abuse incident, the frame that triggered it) until staff close the review.

How we handle your face data — Biometric Data Policy

This is our published policy for the biometric identifier our face scans collect — the geometry of a face, from the liveness selfie and from the camera checks above. It is sensitive data and we handle it strictly:

Reports that someone is under 18

Any user can report another user who appears to be under 18. When several independent, established accounts report the same person within 30 days, that person is automatically asked for a fresh selfie, which leads to a government-ID check if needed (for someone already ID-verified, the reports go to our staff instead). Staff may also require a government-ID check (which is free to them). A user who is confirmed to be under 18, or who refuses or fails the required check within the time we specify, is removed from the Service. Verification checks you start for yourself carry a fee, described in our Terms; a fee owed for an ID check can be paid either by buying Clicks or as a one-time card payment through Stripe, and Stripe (not JoyR1der) handles the card details.

Minors depicted in content

Even though every account holder is an adult, a real child could appear on camera (for example, a bystander). Child sexual abuse material and any sexualisation of a minor are strictly prohibited and are removed. Our staff can run an age estimate on a few frames of an event recording; only staff can see those estimates, and they are deleted when the recording is (an estimate that leads to a child-protection review is kept with that review). Once that check is switched on, images and videos hosts upload as content are automatically checked by our own systems — not sent to a third party — for nudity and the apparent age of any face (once we enforce the biometric release, the apparent age is read only for an uploader who has accepted it); the apparent age is never shown to other users. An image that may show a child in explicit content is logged for our staff to review — and, once that step is switched on, also preserved as evidence and escalated. That log entry, which includes the apparent-age reading, is visible only to our staff and is kept as a safety record. Where we become aware of child sexual abuse material we preserve the relevant evidence and escalate to the appropriate authorities, including New Zealand’s Department of Internal Affairs and, for reports with a US nexus, the US National Center for Missing & Exploited Children (NCMEC).

8. Safety & our moderation model

Keeping the community safe is central to how the Service works:

9. How we protect your information

No system is perfectly secure, but we work continuously to protect your information and to fix issues we find.

10. How long we keep information

InformationRetention
Event recordingsA host’s recording of their own event becomes a content item in their catalogue and is kept until the host deletes it (like any uploaded content), subject to the storage terms in our Terms & Conditions. Administrator safety recordings are kept privately only as long as needed for safety, moderation or legal-compliance purposes, and are preserved under a legal hold for a serious safety case.
Live event chatDeleted when the event ends — unless it is subject to an open safety report, in which case it is kept until that report is resolved.
Chat / direct-message imagesAutomatically deleted approximately 24 hours after they are sent; you can also delete them immediately.
Chats, messages, call history & event history you deleteRemoved from your view straight away (after a few seconds in which you can undo). Deleting is personal: the other people in a chat, call or event keep their own copies. Payment, refund and safety records connected to them are kept as described below.
Age-verification selfie and camera frames (biometric)Not kept — analysed and discarded, with no face template. Exception: a frame flagged as possibly showing a child is kept privately as safety evidence until staff close the review (deleted if benign; kept as the law requires if reported).
Age-check resultsThe result (pass or refer, age band, certainty, method, date), your biometric consent record and, where a check led to a further step, the estimated age range — kept while your account is open (an estimated age range from a staff or moderator on-camera check is deleted 30 days after the event ends, or sooner if the account is deleted). An audit record of each check (method, band, certainty, date) is kept after deletion, to show the 18+ rule is enforced. Where a check led to a child-protection review, that review — which can include the estimated age range — is kept as a safety record, also after deletion.
Government-ID checkHandled by Stripe under Stripe’s own retention. JoyR1der keeps the outcome (verified / not verified), your age in years where it was needed to settle your age, and a one-way hash of the name and date of birth on the ID, used only to recognise a banned person who returns. If you ask our staff to verify you (for example as a public figure or brand) and upload proof documents, we keep those documents and the name you gave only while your account is open, for that review. When you delete your account they are deleted, any ID check still in progress is cancelled, and staff notes about your checks are deleted; we keep only the outcome and the date. The hash is deleted too — unless the account was banned, in which case it is kept with the ban record while the ban stands, to help prevent banned people from returning, and deleted if the ban is lifted.
Your @username after you delete your accountHeld for 30 days so that only you can reclaim it — for this we keep your former user ID and a one-way hash of your sign-in email with the hold — and then released for anyone to take. A username you switch away from is held for 30 days the same way.
Bonus ClicksBonus Clicks we grant you expire (currently) 30 days after they are granted; Bonus Clicks a host receives as payment expire (currently) 90 days after they are received (see our Terms).
Account & profile dataKept while your account is open; removed or de-identified when you delete your account, except where we must retain it (below). If you earn on JoyR1der, deletion completes after a hold of at least 24 hours so refunds can be settled (see “Delete your account” below): during the hold the account is closed and hidden but its data and funds are kept, and you can cancel by signing back in and tapping “Cancel the deletion”.
Lead forms you send and offer codes you holdKept while the advertiser’s campaign records are kept. When you delete your account your name, email and note are removed from every lead, and your account is removed from every offer code (the code and what it was charged stay, without you). An unused offer code expires on the date shown with it.
Your Trolley recipient ID after you delete your accountIf money we owe you is still being held when your account is deleted (for example earnings you did not agree to forfeit), we keep your Trolley recipient ID with that record so our staff can pay you after your profile is gone. It is a payment-processor reference, not contact data, and is deleted when that record is settled. Payout entries in our ledger are kept as transaction records (below).
Your Terms acceptancesA record of each version of the Terms you accepted and when, kept as evidence of what you agreed to.
Transaction, tax & moderation recordsRetained as long as we are legally required to, and to resolve disputes and prevent fraud, even after account closure.

11. Your rights & choices

You can, at any time:

If you are in the EU/UK you also have rights to portability, restriction and objection, and to lodge a complaint with your data-protection authority. If you are in California you have rights under the CCPA/CPRA, including to know and to delete — and note that we do not sell or “share” your data as those terms are defined. Sensitive data (US state laws). Where US state privacy laws treat information as sensitive and require your opt-in consent, we use it only with that consent: biometric data (the face scans in section 7) only after you accept our written biometric release, and your location only if you turn location sharing on (you can turn it off at any time, which deletes the stored location). We do not use sensitive data to infer characteristics about you, and we never use biometric data for ads. If you are in New Zealand and are not satisfied with our response, you can contact the Office of the Privacy Commissioner (privacy.org.nz).

12. Cookies & local storage

Our web app uses only the local storage and cookies needed to keep you signed in, remember your preferences, and run our bot-abuse protection (Firebase App Check with Google reCAPTCHA, which Google provides and which sets its own cookies to tell people from bots). Stripe’s script (Stripe.js) also loads on the web app so that Stripe can take payments and help prevent fraud; Stripe may set its own cookies or storage for that, under its own policy. We do not use advertising, analytics or cross-site tracking cookies. The first time you visit, a notice tells you about this storage; you can dismiss it.

13. Changes to this policy

We may update this policy from time to time. If we make a material change we will update the “Effective” date above and, tell you in the app or by email. A material change comes with an updated version of the Terms, which we ask you to accept before you continue using the Service, as the Terms explain; where the law requires your consent to a new use of your information, we ask for it separately. If you do not accept a change, you can delete your account instead.

14. How to contact us

Conesworth Limited (trading as JoyR1der)
Privacy Officer: Tim Schliebs
16 Rautawhiri Road, Helensville 0800, New Zealand
NZ company number 1862936
Email: legal@joyr1der.com