Test pilot privacy notice
This notice explains how Rotspit handles personal data in the test pilot and on its public pages. Account and activity information can identify real people. Payments, orders and delivery are simulated.
Who handles your data
Hatch House Limited operates Rotspit and is responsible for how it handles personal data. It is licensed by the Innovation City Authority (licence 07011600) at Office A, Innovation City Business Centre, RAK BANK ROC Office, Ground Floor, Al Rifaa, Sheikh Mohammed Bin Zayed Road, Ras Al Khaimah, United Arab Emirates. Contact support@rotspit.com for privacy requests.
What we use and why
- Account and sign-in information. We use your email, authentication records, age confirmation and account preferences to create and secure your account and record your agreements. If you use Apple or Google sign-in where available, we receive information from the provider to sign you in.
- Profile and social activity. We use profile details, follows, wishlists, posts, comments, reactions and sharing choices to show content to the audience you choose. New profiles are public by default. Public profiles, wishes and activity can appear in the feed, discovery or shared links, including to people without a Rotspit account. You can change your visibility settings.
- Test delivery and payment information. Use sample names, addresses and phone numbers to test delivery, and only test card details for payments. We use test contributions, fees, payment references, status and card metadata to exercise and reconcile the sandbox. Stripe handles the card entry form. When you agree to a test payment, we record verification details such as the exact authorisation text, its version and fingerprint, time, platform, IP address and user agent. An anonymous contribution hides your identity from the public and the recipient. Rotspit and its processors still handle records needed for the test.
- Support, device and security information. We use information you send to support, app and browser information, request or account events and error logs to answer questions, secure the service, investigate issues and retain relevant evidence when needed.
Product analytics are optional where offered. With your permission, we use pseudonymous usage and device events to improve the service. You can withdraw that permission in Settings. Contact discovery also requires permission where available. It uses hashes of selected contact details for matching. Use sample contact details when testing. If you subscribe to updates, you can unsubscribe from those messages.
Service providers, sellers and locations
Supabase hosts account and gift records in Sydney, Australia. Cloudflare hosts the site and delivers network traffic. Resend provides email delivery. Sentry helps diagnose errors. PostHog processes optional analytics in the EU. Apple or Google may handle sign-in if you select it. Push, monitoring and support providers receive information needed for the functions they provide when those functions are used.
Stripe receives test card details through its form and transaction information such as your billing email, test amount and reference. Rotspit receives identifiers, limited card metadata and status. Test dispute evidence can include the recorded authorisation, IP address, user agent and timestamps. Public-product search terms and links may be sent to Bright Data or services that read seller pages. Avoid entering personal data in searches.
To simulate fulfilment, Rotspit makes the recipient’s name, delivery address and phone number recorded for an active funded test order available to the approved seller for that order. The seller can view these details in its portal or retrieve them through an integration key with permission to read delivery details. Seller access ends when the order is marked delivered or cancelled. Use only sample recipient details.
These services can process data in locations outside your country. Locations depend on the provider and feature. Ask us for information about transfers or safeguards that apply to your records.
How long we keep records
Retention depends on the record and the purpose for keeping it. We keep account and test activity records to operate the pilot. Some consent, payment, security and support records can remain after account deletion to maintain evidence, resolve issues or meet legal obligations. Account data can remain in restricted recovery copies after removal from active systems, until the backup expires or is removed. Daily Supabase backups are kept for up to seven days. Encrypted recovery copies may also be kept in restricted local storage and in Cloudflare R2 in the EU. The ordinary R2 copies expire after 14 days. Separately preserved recovery copies remain until released.
Your privacy choices
Use Settings to review visibility, correct profile data, request a data export or request account deletion. An active capture, order, return or dispute can delay deletion. The app explains the reason when that happens. Depending on applicable law, you may also request access, correction, deletion, portability or limits on processing and raise a concern with the relevant authority. Email support@rotspit.com for help with these requests. We may need to verify your identity before acting.
Age limit
The test pilot is for people aged 18 or older. Contact us if someone under 18 created an account or you believe their information was shared with us.