YuKon3t
Sign in

Privacy Policy

Last updated: October 26, 2026

YuKon3t is operated by Motiff Core Holdings, a Delaware company, which is the data controller for the personal information described below ("Motiff Core Holdings," "we," "us"). This Privacy Policy explains what information we collect when you use YuKon3t, why we collect it, and the rights you have over it. We collect the minimum needed to run a global, trust-based social platform, and we never sell your personal data.

1. Information we collect

We collect:

  • Account information: email address, optionally a username and password (stored as a salted hash, never in plain text), date of birth (used only to confirm you meet our minimum age requirement — not shown on your profile), display name, bio, country, languages, interests, and profile picture.
  • Content you create: Circle and Channel posts, Collab Board listings, direct messages, 24-hour Stories (including reactions and replies to them), reports you file, and any photos or short videos you upload.
  • Connection & activity data: Circles and Channels you join, connection requests, intent tags you select, streaks, event replies (whether you answered Going or Maybe, and when), trust score signals (account age, verification status, report history).
  • Poll votes: if you vote in a poll in a Circle or on a Collab Board, we store which option(s) you picked, so you can change or withdraw your vote. Everyone else, including the poll's creator and the Circle's or collaboration's admins, sees only how many people picked each option, never who voted for what. Your vote is deleted when you withdraw it, when that option or the poll is deleted, or when your account is deleted; polls you created are deleted along with your account.
  • Circle events: if you claim an item on a Circle event's “who's bringing what” list, we store that you claimed it, and everyone who can see the event sees your name next to that item. The claim is removed when you let the item go, when the event's organizer unassigns or removes it, when the event is deleted, or when your account is deleted. If you make a Circle event repeat, we keep its text, place and schedule so the next dates can be posted under your name automatically, until the repeat ends or is stopped, or you leave the Circle; it is deleted with the Circle or your account. When an organizer sends a reminder to people who haven't replied, we record when it was sent so it can be sent at most once every 12 hours. When an organizer cancels or reschedules an event, we store when, the optional reason they give (shown on the event to everyone who can see it) and, for a new time, the time it was moved from; these are deleted with the event.
  • Event organizer tools: when an organizer posts an update about a Circle event, we store its text, who posted it, when, when it was last edited, and how many people were notified; it is shown on the event to everyone who can see it and sent as a notification to the people who answered Going or Maybe. Its author can edit it and any organizer of the event can delete it: a deleted update's text is erased at once and we keep only that an update was sent and when (so the daily limit still holds), until the event or the organizer's account is deleted. If an organizer marks you as having attended an event (attendance check-in), we store that you attended, whether you had replied beforehand, which organizer marked you and when; only the event's organizers can see it, and it is deleted when they untick you, when the event is deleted, or when your account is deleted. Organizers can export a spreadsheet (CSV) of an event they organize containing, for each person who answered Going or Maybe, attended or claimed a “who's bringing what” item, only their display name, username, their answer and when they gave it, whether they attended and the items they claimed (never an email address, phone number or other account details, and nobody blocked either way with the organizer). Once an organizer saves an export, that copy is outside YuKon3t and under the organizer's control. Your own event replies, attendance records, claimed items and the organizer updates you wrote are included in “Export my data”.
  • Secret chat keys and messages: if you set up secret chats, we store your public encryption key and a copy of your private key that is encrypted with your recovery passphrase, which we cannot read or reset. The text of messages in a secret chat is encrypted on your device before it is sent; we store only the encrypted form and cannot read it. Photos, videos, and voice notes sent in a secret chat are not encrypted. When you report a message from a secret chat, the text of that message is shared with our moderators.
  • Notification data: if you enable push notifications, a device push token (a web push subscription, or, on the Android and iOS apps, a Firebase Cloud Messaging token) used only to deliver notifications like calls, messages, and event reminders to your device. In the mobile apps, the app's version and build number and your device's platform (Android or iOS) are stored with that token, used only to tell people on an older version that an app update is available or required.
  • Call & live session data: metadata needed to connect a 1:1 call or a Collab live session (who's in the room, timing). If a live session's host turns on cloud recording, the recording itself is stored as described in Section 4.
  • Product usage events: a small number of key lifecycle events tied to your account — for example sign-up, sign-in, a post created, a connection requested or accepted, a message sent, a call started, or a circle joined or created — used to keep the service reliable and to understand how features are used.
  • Technical data: IP address and basic request metadata (used for rate limiting and abuse prevention), session cookies, and your theme preference cookie. Our product analytics are configured not to use your IP address to determine your location. If enabled, our product analytics provider (see PostHog in Section 4) also receives usage data and screen recordings of how you use YuKon3t.
  • Guest preview: if you use “Explore YuKon3t as a guest” (yukon3t.com/try) without an account, we create no profile for you and ask for no email, password or other details. Your browser gets a temporary session cookie that ends on its own after at most 2 hours (or sooner, if we switch guest preview off). Every guest uses the same shared, read-only guest identity, so nothing a guest does is tied to them personally, and a guest can't post, message, react or change anything. To stop abuse, your IP address is used for rate limiting exactly as described under Technical data (counters that expire on their own; the guest start counter after 1 hour), and the Cloudflare Turnstile check may run. We record that a guest visit started, with the short tag in the link you followed (for example “reddit”) but not your IP address; these counts are kept like our other usage counts. Guest visits are never screen-recorded by our product analytics provider and are not identified to it; it may still receive the pages a guest opens, as it does for signed-out visitors.
  • Communications: if you contact us for support or to appeal a moderation decision.
  • Advertiser information: if you book a paid ad placement, we collect the company name, contact name, and contact email you submit, along with the ad creative (headline, body text, image or video, and destination link).
  • Device contacts: only if you use the "Invite from contacts" feature — read from your device to show which of your contacts to invite. This list is never uploaded to or stored on our servers; it's discarded the moment you leave that screen.

We do not require or knowingly collect government ID or precise geolocation. Members do not need to provide any payment information to use YuKon3t socially — the only payments we process are from advertisers booking paid ad placements, handled by Stripe as described below. We never see or store your full card number.

2. How we use your information

  • To create and operate your account, and to authenticate sign-ins via emailed magic links or, if you choose, a username and password.
  • To confirm you meet our minimum age requirement before your account is created.
  • To operate core features: Circles, Channels, Collab Boards, Stories, Discover matching, connections, messaging, and voice/video calls and live sessions.
  • To let a Circle's owner invite that Circle's members to a private collaboration: being a member of a Circle means its owner can send you a collaboration invite even if you aren't connected, which you can decline.
  • To let the organizer or a co-admin of a private collaboration, when they start its live session, notify the collaboration's participants that the session is live and invite the members of Circles they created (the same collaboration invite described above, which you can decline).
  • To let a private Circle's owner or co-admins invite you to join it: if you're connected with one of them, they can send you an invite to that Circle, which you can decline. A private Circle is shown only to its members: its name, picture, description, member list and everything posted in it are hidden from everyone else, except that a person with a pending invite sees its name, picture and description so they can decide. Our administrators can still review any Circle to enforce our Community Guidelines.
  • To deliver push notifications you've enabled, such as incoming calls, new messages, and event reminders.
  • To let people who use Discover know when someone new joins: shortly after you finish setting up your profile and verify your account, if your profile is shown in Discover and your posts are public, other users may get a notification with your name and profile picture saying you just joined, linking to your profile. This happens once, never to anyone you've blocked or who has blocked you, and not at all if you turn off “Show my profile in Discover” first. You can stop receiving these notices about others under Settings → Notifications. We record when your profile was completed, whether you were announced, and when you were last sent such a notice.
  • To automatically screen text, photos, and video — including ad creative — for policy violations before they are shown to others.
  • To translate posts, comments, chat messages and event organizer updates into a reader's language: when someone taps “Translate” under text written in another language, or has turned on “Auto-translate” in Settings → Language (off by default), the text of that post, comment, message or update is sent to our AI provider (OpenAI, see Section 4) and the translation is shown to them alongside the original, which is never changed. Only the text is sent, not who wrote or asked for it, and links, @mentions and #hashtags are left out of what is sent. Messages in secret (end-to-end encrypted) chats are never translated: we can't read them. We save each translation so that anyone else who can already see the same text, and reads it in the same language, gets it without it being sent again; we don't record who asked for a translation. A saved translation is deleted when the text is edited or deleted, including when the account that wrote it is deleted.
  • Live translated captions in 1:1 calls: only when both people in a one-to-one voice or video call turn them on for that call (they are off by default, and either person can turn them off at any time, for both), each person's own call audio is sent from their device to our AI provider (OpenAI, see Section 4) to be transcribed while their microphone is on, the resulting text is sent to the other person's device through our calling provider (Daily.co), and it is translated by OpenAI into the other person's app language. YuKon3t does not store the audio, the transcripts or the translations, and does not log them; OpenAI processes the audio to produce the text and may keep what it receives for a limited time under its own terms (for example, for abuse monitoring); we keep only that captions were agreed to for that call, when transcription ran, and how many caption minutes each person has used this month (to enforce a monthly limit). Captions are never available in calls with more than two people. Calls are not end-to-end encrypted and are not linked to secret chats, so turning on captions in a call does not affect any secret chat.
  • To investigate reports, enforce our Community Guidelines, and maintain an audit trail of moderation decisions.
  • To compute your trust score from account age, verification status, and report history.
  • To review, run, and bill paid ad placements, and to display non-targeted ads to users of the service (see Section 5).
  • To detect and prevent fraud, spam, and abuse, including rate-limiting requests.
  • To log key product-usage events for reliability and to understand feature usage, in aggregate.
  • To communicate with you about your account, security, or policy changes.

3. Legal basis for processing (EEA/UK users)

Where the General Data Protection Regulation (GDPR) applies, we process your data under these legal bases: performance of a contract (providing the service you sign up for), legitimate interests (safety, fraud prevention, moderation), and consent (optional features like uploading media, enabling push notifications, or joining a call, which you actively choose to use). You can withdraw consent at any time by not using that feature, or by deleting your account.

4. Third-party service providers

We use a small number of specialized providers to operate YuKon3t. Each processes only the data necessary for its function, under its own privacy and security terms:

  • Netlify — application hosting and infrastructure.
  • Neon — our PostgreSQL database provider, storing account and content data.
  • Resend — sends sign-in and account-related emails.
  • Cloudflare (R2) — stores uploaded photos and videos, including Story and ad media.
  • Cloudflare (Stream) — a temporary copy of an uploaded video may be sent here for automated moderation scanning and caption generation, and QuickTime (.mov) videos are sent here to be converted to a widely playable MP4; the video is still served from R2 above, and the Stream copy is deleted once it is no longer needed.
  • Cloudflare (Turnstile) — a bot check on sign-up, sign-in, password reset, device verification, phone-verification code requests, and ad booking forms, used to tell real people from automated scripts. When it runs, Cloudflare receives technical signals from your browser and network connection (such as your IP address) and processes them under Cloudflare's own privacy policy; it runs only when you tap “Verify you're human”, and Cloudflare may then ask you to complete a short check.
  • Firebase App Check (Google), with Play Integrity on Android and App Attest (Apple) on iPhone — in the YuKon3t mobile app, on sign-up, sign-in and password reset, the app asks Google's Firebase App Check for a one-time token showing it is the genuine, unmodified app running on a genuine device. Google, and Apple on iPhone, process app and device integrity signals to produce it, under their own privacy policies, and we verify the token with Google. If it is valid, we may skip the “Verify you're human” tap; it never replaces that check on the website. We use it only for security and abuse prevention. We store no device identifiers from it, only an anonymous record of the result, platform and app version.
  • OpenAI — automated content moderation of text and images before publication, machine translation of posts, comments, chat messages and event organizer updates when a reader asks for it, and transcription and translation of call audio for live captions when both people in a 1:1 call turn them on (see Section 2). OpenAI may keep the content it receives for a limited time under its own terms, for example for abuse monitoring. We do not send full account profiles to this provider — only the specific content being screened or translated.
  • Daily.co — powers 1:1 voice/video calls and Collab live sessions, and carries live caption text between the two phones in a call while captions are on (not stored by YuKon3t). If a live session's host enables cloud recording, the recording is stored by Daily until the host or an admin deletes it.
  • Firebase Cloud Messaging (Google) — delivers push notifications to the Android and iOS apps. Web push notifications are sent directly to your browser's push service without a third-party intermediary of ours.
  • Stripe — processes payments from advertisers booking paid ad placements via a hosted Stripe Checkout page. We never receive or store full card numbers.
  • PostHog (PostHog Inc.) — if enabled, provides product analytics and session replay, processing data on our behalf. It records how the app is used: the pages and screens you visit, your taps and clicks, and recordings of what is shown on your screen during a session. A person profile is created only for signed-in users, and it is identified by your account ID (not your name or email). Message text in chats is excluded from recordings, and the contents of text inputs are masked. As described in Section 1, these analytics requests are flagged so PostHog does not derive your location from your IP address.
  • Sentry — if enabled, receives details about application errors (which may include limited technical context about the request that failed) to help us diagnose bugs.

We do not sell your personal information to anyone, including these providers, and we do not permit them to use your data for their own marketing purposes.

Separately, a post can embed a video hosted on YouTube, Vimeo, TikTok, Instagram, Facebook, or Dailymotion instead of an uploaded file. Viewing that embedded player loads it directly from that platform, which may set its own cookies or collect data under its own privacy policy — YuKon3t only stores which video is linked, not anything the platform itself collects when you view it.

5. Advertising

YuKon3t sells a small number of paid ad placements to fund the service. These are sold at a single flat rate with no audience targeting available to advertisers — we do not use your account data, activity, or trust score to choose which ad you see, and we do not share your personal information with advertisers. We record only aggregate, non-personal impression and click counts per ad campaign to measure reach and bill fairly; we do not track which individual user viewed or clicked a given ad, and we do not use third-party advertising or tracking cookies to do so.

Every ad is reviewed by a human before it goes live, and the same automated content screening described in Section 1 is applied to ad creative. If you submit an ad booking, see the "Advertiser information" item in Section 1 for what we collect from you. Clicking through to an advertiser's link takes you to a third-party site we don't control — see our Disclaimer.

6. International data transfers

YuKon3t is a global service, and our infrastructure providers operate data centers in multiple countries, including the United States. If you access YuKon3t from the EEA, UK, or elsewhere outside the provider's home region, your data may be transferred to and processed in a country with different data protection laws than your own. Our providers maintain appropriate safeguards (such as Standard Contractual Clauses) for these transfers where required.

7. Data retention

A guest preview session (see Section 1) lasts at most 2 hours; the record that a guest visit started (with its link tag, without an IP address) is kept with our other usage counts.

We retain your account and content data for as long as your account is active. If you delete your account, your profile, posts, messages, Stories, and Circle/Channel memberships are permanently deleted, subject to a short operational delay for backup rotation. Moderation records (reports and audit log entries) tied to enforcement actions may be retained separately for a limited period to maintain platform safety and legal compliance, even after an associated account is deleted. A photo or video post that our automated screening flags when you post it is kept, hidden from everyone except you and our moderators, until a moderator publishes or removes it; if nobody has reviewed it within 14 days, it is deleted together with its media. Uploads in the most serious categories (such as sexual content involving minors) are deleted straight away and not kept for review; a record that the upload was rejected, when, and the screening categories involved is kept with our moderation records. Ad campaign records, including advertiser contact details and creative, are retained after a campaign ends for our accounting and audit purposes. Recordings of Collab live sessions are retained by Daily.co until the host or an admin deletes them. Saved translations of a post, comment, message or event organizer update are deleted along with it, and when it is edited. Event organizer updates and attendance records are deleted with the event (see Section 1). YuKon3t does not store live call captions (audio or text), though OpenAI may keep the audio and text it processes for a limited time under its own terms; the record that captions were used in a call is deleted with the call record, and caption-minute counts with your account.

View-once photos and videos. A photo or video sent as "view once" in a one-to-one chat is stored in private storage with no public link. When it is sent, the photo (or, for a video, one still frame) is screened automatically like any other upload. When the recipient opens it, the file is deleted from our storage: normally immediately, and within a few minutes at most if their app could not confirm it. If it is never opened, the file is deleted 14 days after it was sent, or sooner if the sender deletes the message for everyone; if the chat or the sender's account is deleted first, the file can no longer be opened by anyone and is removed from storage within 15 days. We do not keep a copy for moderation or any other purpose, and the file itself is never included in our database backups. We do keep the message record: that a view-once photo or video was sent, by whom, when, and whether and when it was opened. We cannot prevent the recipient from capturing what is on their screen.

Profile pictures. Profile pictures are kept in private storage with no public link, and are shown only to people signed in to YuKon3t (not to anyone you have blocked or who has blocked you). A picture you add is stored as a small version, which signed-in members see, and a larger version, which only you and your connections can open. Both are screened automatically like any other upload. When you change your picture, the previous one is deleted from our storage. A picture added before profile pictures became private may stay reachable at its earlier public address for a limited time until we finish removing those copies. We cannot prevent someone who can see your picture from capturing what is on their screen.

Hidden chats. If you hide a chat, we store which chats you have hidden and when, and a one-way hash of the PIN you chose (never the PIN itself), together with a count of recent wrong PIN attempts. This is visible only to your own account; the other people in the chat are not told. Hiding changes where a chat is shown to you and what its notifications say. It does not change how the messages are stored, scanned or retained.

Forwarded messages. When you forward a chat message, we store a copy of it as a new message from you in each chat you picked, with a mark that it was forwarded. We don't record who wrote the original or which chat it came from. A forwarded photo, video or voice note points at the same stored file as the original, so that file is kept until no message (or post, story or Muse) uses it any more. Your copy follows the same rules as any message you send: it is included in your data export and deleted with your account or when you delete it for everyone; deleting the original doesn't delete the copies. Forwarded text is screened again before it is sent. Messages from secret (end-to-end encrypted) chats and view-once photos and videos can't be forwarded.

8. Your rights

Regardless of where you live, you can access, export, correct, or permanently delete your data at any time from Settings — for free, with no limit, and without needing to contact us. Depending on your location, you may also have the right to:

  • EEA/UK (GDPR): access, rectification, erasure, restriction of processing, data portability, and objection to processing based on legitimate interest.
  • California (CCPA/CPRA): the right to know what personal information we collect, the right to delete it, and the right to opt out of its sale — we do not sell personal information, so there is nothing to opt out of. We do not discriminate against users who exercise these rights.
  • Other jurisdictions: many countries have similar data protection frameworks; we honor equivalent requests on a good-faith basis regardless of where you're located.

To exercise a right that isn't self-service in Settings, contact us using the details in Section 12.

9. Children's privacy

YuKon3t is not directed to, and is not intended for use by, anyone under 16 years old. We do not knowingly collect personal information from anyone under 16. If we learn that we have collected information from someone under 16, we will delete it and close the associated account promptly.

10. Cookies

We use a session cookie to keep you signed in (for a guest preview, a temporary session cookie that expires after at most 2 hours) and a small, non-sensitive cookie to remember your light/dark/system theme preference. We do not use third-party advertising or tracking cookies on YuKon3t. If you complete a paid ad booking, Stripe's hosted checkout page (on stripe.com, outside YuKon3t) may set its own cookies under Stripe's own privacy policy.

The app also keeps some device-only preferences in your browser's local storage, such as your Data saver setting, which is saved on that device only. To load faster on slow connections, the app saves a copy of YuKon3t's own app files (code, fonts and icons) and a “You're offline” page on your device; that copy never includes your messages, posts, photos, profile pictures or other personal content. To decide whether to use less data, the app reads the connection information your browser provides (such as whether your device's data saver is on) and how long its own recent requests took; this is worked out on your device and is not sent to us.

11. Data security

We use industry-standard technical safeguards, including encrypted connections (HTTPS/TLS) everywhere, encrypted secrets management, rate limiting, and per-request access controls that verify every action server-side. Voice/video calls and live sessions are relayed through our video provider using encrypted connections. If you set a password, we never store it in plain text — only a salted bcrypt hash, which we cannot reverse to see your actual password. No method of transmission or storage is 100% secure, and we cannot guarantee absolute security. If we become aware of a data breach affecting your personal information, we will notify affected users and relevant authorities as required by applicable law.

12. Contact us

Questions about this policy, or requests to exercise your data rights, can be sent to the email address associated with your account's support channel, or by replying to any account notification email. We aim to respond within 30 days.

13. Changes to this policy

We may update this Privacy Policy as YuKon3t evolves. Material changes will be announced in-app or by email before they take effect. Continued use of YuKon3t after a change takes effect constitutes acceptance of the updated policy.