Privacy notice
This page describes what Meaningful actually does with your data, in plain terms. It hasn’t had a legal review yet. Treat it as an accurate description of practice, not a substitute for one. See also the Terms of service.
What we collect
Account & profile: email address, password (stored as a salted hash, never in plain text), display name, pronouns, gender and bio if you add them, timezone, and your interests. Gender is optional and is used for one thing only: if you say you are a woman you can choose to be paired only with other women. It is never shown to anyone you are paired with. Profiles here are deliberately thin: there’s no photo gallery and no free-text feed.
Activity: bookings, call attendance, reputation and streak counters, comfort settings (like camera preference), survey responses after calls, and any strengths or reflections exchanged with a call partner.
Calls: calls run over LiveKit for live video and audio between the two matched participants. Meaningful does not record calls, has no transcription feature, and does not store anything from the audio or video itself in our own systems. That includes a window shared on screen, where an organisation has turned screen sharing on for its group: it is carried the same way, live between the two people, and not kept by Meaningful. LiveKit carries the call for us, and like any video infrastructure provider, its own systems may briefly keep short diagnostic data (logs, connection metrics, and, under LiveKit’s data processing terms, potentially brief audio, video, or text snippets) for infrastructure monitoring, for up to 30 days by default, separately from anything Meaningful controls moment to moment. This isn’t something Meaningful can see or access: it’s covered by LiveKit’s own privacy policy and data processing addendum, which govern what LiveKit does with data while acting on our behalf.
Contact exchange: after a call, either side can offer contact details (an email, a handle, whatever they choose to type). That text is only shown to the other person if they accept the exchange.
Safety reports: if you report someone, we keep the reason, any details you add, and which call it relates to, so it can be reviewed.
Organisations: if you join through a university or employer, that organisation’s admins can see your membership and attendance within their own cohort, not your activity elsewhere on the platform. If your organisation has defined skills, a tag you receive on one is shown to you as coming from “a colleague” (or “a certified mentor” for an endorsement from someone the organisation authorised) rather than by name, and the organisation sees only anonymous totals, including how many members of a staff group it has chosen to include are taking part, each hidden when fewer than five people are behind a figure. If you propose a skill, the organisation’s admins can see that you proposed it. If you offer to teach or learn a skill, only the matcher reads that. A colleague you are paired with sees the skill, and your level if you offered to teach it and have that switched on, and your name only after you both accept.
Security: if you enable two-factor authentication, the underlying secret is encrypted at rest (not just hashed, since checking a code requires it). Backup codes and password-reset links are stored only as one-way hashes. We keep a short-lived record of failed sign-in attempts to slow down password-guessing.
Who it’s shared with
Nothing here is sold, and nothing is used for advertising. Data is shared in exactly these cases:
- Your matched call partner sees your profile as normal, and anything you explicitly send them through contact exchange.
- If you belong to an organisation, its admins can see your standing within that organisation.
- A small set of infrastructure providers process data on our behalf to run the service: Supabase (database hosting), Vercel (application hosting), LiveKit (video/audio transport for calls), Resend (delivering emails like reminders and password resets), Sentry (technical crash reports: stack traces and request metadata, not conversation content), and PostHog (product analytics, see below).
Cookies & analytics
Meaningful sets one cookie: a signed session cookie that keeps you signed in.
We also use PostHog for product analytics: which pages get visited, which buttons get clicked, that kind of thing, so we can tell whether a change actually helps. It runs from your browser, not a cookie (its own visitor id lives in local storage instead), and honours your browser’s Do Not Track setting if it’s on. It never sees the content of a call, a message, or anything you type into a form. Screen/session recording is switched off in code, not just left at whatever PostHog’s own default is. This stays consistent with the same “not a feature” stance the calls themselves take on recording (see above). Nothing here is used for advertising, and nothing is sold.
Your choices
You can turn off reminder emails from your profile at any time. Transactional mail like password resets still goes through, since that’s how account recovery works.
Deleting your account
You can delete your own account at any time, without contacting us: on the web, go to your profile and use “Delete account” under Danger zone; in the mobile app, it’s under Settings. This removes your profile details (display name, pronouns, bio, interests) and group and organisation memberships, and turns off two-factor authentication and push notifications, immediately and permanently — it can’t be undone. Your call history and any reports involving you stay on record for safety and integrity purposes, but are no longer linked to anything identifying you. If you’d rather we do it for you, or have questions about exactly what’s kept, email privacy@getmeaningful.io.
Questions
Reach us at privacy@getmeaningful.io for anything about this notice or your data.