personal data

Privacy Policy

How Unlabored Labs, Inc. collects and uses personal data for Roda's waitlist, mobile app, AI-assisted matching, analytics, bookings, and events.

last updated: October 13, 2026
effective: October 13, 2026

Roda is built for adults in Portugal and the EU. We use questionnaire data to arrange human-reviewed, AI-assisted social events.

Who we are

Unlabored Labs, Inc. is the controller of personal data processed for roda.place, the Roda mobile app, waitlist, bookings, support, and Roda-arranged events.

Registered address: 131 Continental Dr Suite 305, Newark, DE 19713, United States.

EU representative: Weishang Lu, Penha Longa D, Estrada da Lagoa Azul, Linho, 2714-511 Lisboa, Portugal, wynn@unlabored.net.

You can contact us about privacy, legal, or support requests at hello@roda.place.

Scope

This policy applies to the Roda landing page, waitlist, mobile app, event booking flows, support channels, and Roda-arranged gatherings in Portugal and the EU.

Roda is for people aged 18 or older. We do not knowingly collect personal data from children or allow minors to use the service.

Data we collect

Waitlist data: email address, signup time, consent records, referral or campaign source, and basic technical information such as IP address and browser data.
Account data: identifiers, email address, name, and authentication information provided through Clerk and Apple or Google sign-in.
Adult-verification data: a mandatory self-reported date of birth, checked before account setup and retained in a restricted record to confirm continuing 18+ eligibility.
Optional table-composition data: with separate consent, identity, whole-table age-span preference, women's safety preference, and balanced-gender-mix preference.
Questionnaire data: full answers about city, neighborhoods, availability, social preferences, plan types, conversation style, budget comfort, accessibility or mobility needs, food constraints or allergies, safety concerns, and event confidence needs.
Preference data: food constraints, accessibility and mobility needs, budget range or ceiling, social intent labels, and optional no-match safety text.
Matching data: profile summaries, compatibility signals, match scores, group assignments, and human review notes used to arrange events.
Matching history: earlier versions of your questionnaire answers, the matching inputs and scores used each time you were considered for a plan and how you came to be considered, which plan ideas were shown to you, and how each of your invitations progressed, including whether you, our team, or an automatic rule made each change.
Event and booking data: event selection, invitation responses and decline reasons, attendance status, post-event feedback, venue or host details, payments, refunds, subscription status if memberships are offered, communications, and support history.
Device and app data: app logs, device type, operating system, crash or diagnostic information, and motion permission status if you grant motion access in the mobile app.
Analytics data: page views, app events, interaction metadata, device and browser information, approximate location derived from technical data, and consent choices collected through PostHog or similar tools. On roda.place, analytics runs for every visitor without cookies or browser storage unless you say okay to the cookie banner; until then, visits are counted by a hash PostHog's servers work out each day, so they can't be linked across days. The Cookie Policy lists exactly what is sent and stored.
Cookie banner answers: each time you answer the roda.place cookie banner, one consent_updated event records your answer (granted or denied) in PostHog, with the same page and browser details as other analytics events. After a no, it is sent without any stored identifier, so it is linked at most to that day's other visits from the same browser and network.

How we use data

To operate the waitlist, mobile app, accounts, bookings, payments, subscriptions, support, and Roda-arranged events.
To understand preferences and arrange compatible small-group plans, including by using human-reviewed AI-assisted matching.
To verify that people are 18 or older and, when separately consented, shape groups using age and gender-comfort preferences.
To communicate about launch status, event details, safety issues, product updates, service messages, and customer support.
To process payments, refunds, accounting records, tax records, fraud checks, and legal obligations.
To improve reliability, measure product usage, debug issues, protect the service, and prevent abuse.
To learn from what happens after invitations go out (who accepts, who attends, and how plans go) so we can improve how Roda matches people, including by building and testing matching models from matching history. Optional age and gender table-composition settings are not included in this history.
To honor consent choices for analytics, waitlist updates, marketing communications, and optional sensitive details.

Legal bases

We rely on the following GDPR legal bases depending on context.

Contract: to provide the Roda app, bookings, paid events, subscriptions, support, and account features you request.
Consent: for waitlist marketing where required, analytics cookies and browser storage (on roda.place, only after you say okay to the cookie banner), and optional information that may reveal health, accessibility, allergy, or similar sensitive details.
Legitimate interests: to improve the service (including learning from event outcomes to improve matching), keep Roda safe, prevent fraud or abuse, understand aggregate product usage, and manage business operations, where those interests are not overridden by your rights. Where matching history includes optional sensitive answers, we use those answers only within the consent you gave for them.
Legal obligation: for tax, accounting, consumer-law, payment, regulatory, and dispute records.
Vital interests or public interest: only if needed to respond to urgent safety or emergency situations.

Sensitive information

Some questionnaire or preference answers, such as accessibility needs, allergies, dietary restrictions, or safety concerns, may reveal sensitive personal data. We ask for this only where it helps us arrange safer and more suitable events. You can choose not to provide optional details, but that may limit our ability to account for those needs.

Identity and age/gender table-composition matching are optional and use a separate consent. You can decline without losing normal access, or withdraw in Preferences as easily as you opt in. Withdrawal clears the active identity and composition settings; we retain date of birth only for adult eligibility while the account remains active.

Date of birth and active demographic choices are kept in a restricted record with limited internal access. They are excluded from product analytics, attendee views, general operations views, AI prompts, profile summaries, and embeddings. Matching workers receive only a derived age reference and consented composition settings, never full date of birth.

We do not ask users to upload photos, public bios, or user-generated media at launch.

AI-assisted matching

Roda may send full questionnaire answers and related preference data to OpenAI API models and internal matching systems to generate summaries, compatibility signals, event suggestions, and group-placement recommendations.

Age and gender group shaping uses deterministic internal rules and aggregate diagnostics. Full date of birth, identity, demographic consent, and composition settings are not sent to OpenAI prompts or embeddings.

AI output assists our team. A human reviews matches and event placements before users receive event arrangements. Roda does not use AI as the sole basis for decisions that produce legal or similarly significant effects.

We minimize prompts and outputs where practical, restrict processor access by contract, and avoid using AI output as a substitute for safety review or user consent.

International transfers

Unlabored Labs, Inc. is a US company operating Roda for Portugal and the EU. Some providers may process data in the United States or other countries outside the EEA.

Where personal data is transferred outside the EEA, we use appropriate safeguards such as EU Standard Contractual Clauses, transfer impact assessments, data processing agreements, and provider security controls where required.

Retention

Waitlist data: until launch plus up to 12 months, unless you ask us to delete it earlier or consent to remain on a mailing list.
Account, questionnaire, preference, matching, and event profile data: while your account is active, then generally deleted or anonymized within 30 days after deletion unless we need it for legal, safety, fraud, accounting, or dispute reasons.
Matching history: while your account is active, then your own history is deleted with the account. Records of a group decision that also concern other members are kept with your identity replaced by a placeholder.
Matching run logs (separate from the matching history above): the technical records of each matching run, meaning the scores and candidates it considered and the logs of syncing your answers to the matching service, are deleted after 30 days. The record of who was shown to whom is kept for about 180 days so we can keep invitations fair, then deleted. If you delete your account, your id in these logs is replaced with an anonymous placeholder straight away, and the logs are then deleted on this schedule.
Date of birth: while your account is active for adult eligibility, then deleted with the account under the same timetable unless a limited legal or dispute exception applies. Optional identity and composition settings are cleared when you withdraw demographic matching consent.
Backups: retained for up to 90 days before rotation or deletion. If we ever restore one, account deletions made since that backup are applied again before Roda reopens. So that a restore can't bring a deleted account back, we keep a minimal record of each deletion for 120 days: the account and profile identifiers, and nothing of what was in the account; if we restore our database from a backup, we re-apply the deletion and keep this record for up to 120 days from then.
Analytics data: retained for up to 12 months unless a shorter period is configured or required.
Payment, booking, tax, accounting, and dispute records: kept for 10 years, as Portuguese accounting law requires, or longer if needed to resolve a claim. After you delete your account, these records keep only a random record number in place of you: no name, email address, or sign-in id.
Safety and moderation records (reports, restrictions, and their review history): kept for 3 years after the matter is resolved, and a suspension or restriction for as long as it is in place and for 3 years after it ends. If you delete your account, they stay linked to that same random record number instead of your identity, so a safety decision isn't undone by deleting an account. A report you filed keeps what it says but no longer names you.
Suspension evasion: if you delete your account while a suspension or restriction is in force, we also keep a coded fingerprint of each email address, sign-in account (such as Google) and phone number on that account. It is made with a secret key and works one way only, so it can't be turned back into the address or number. We use it only to apply the same suspension or restriction if you sign up again, and delete it when that suspension or restriction ends; any copies in our deletion records (see Backups) are gone within 120 days. We do this for no other account deletion. Legal basis: our legitimate interest in keeping Roda safe.
Records of your export and deletion requests: kept for 3 years so we can show how we handled them, without your email address once the deletion is complete.

Your rights

If you are in the EU, you may have the right to access, correct, delete, restrict, or object to processing of your personal data, to receive a portable copy, to withdraw consent, and to object to direct marketing.

You can withdraw demographic matching consent directly in Preferences. To correct a verified date of birth, contact hello@roda.place; corrections are restricted to authorized support staff and audited.

You may also have rights related to automated decision-making. Roda uses human-reviewed AI-assisted matching and does not make solely automated legally significant event-placement decisions.

You can export your data or delete your account yourself, in the app under preferences → your data, or at roda.place/account/delete by signing in with the same Apple or Google login.

To exercise rights, contact hello@roda.place. You may also contact our EU representative at wynn@unlabored.net. You can complain to Portugal's Comissão Nacional de Proteção de Dados or another competent EU data protection authority.

Security

We use technical and organizational safeguards designed to protect personal data, including access controls, processor due diligence, encrypted transport where available, and limited internal access. No service can guarantee perfect security, but we work to reduce risk and respond to incidents promptly.

Changes

We may update this policy as Roda changes. If changes are material, we will take reasonable steps to notify users, such as by email, in-app notice, or an updated notice on roda.place.