The Service is intended only for people aged 18 or over. A membership application requires a date of birth, and applications from people under 18 are rejected automatically.

Depending on the features you use, we process the following categories.

Sign-in and account data

• Sign in with Apple. When you sign in with your Apple ID, Apple sends us a stable Apple user identifier, the email address you choose to share (or a private relay address if you use Hide My Email) and, on your first authorisation, the name you choose to share, which we offer as a suggestion for your display name. We also keep an Apple sign-in token so that we can revoke The Bay’s access to your Apple ID when you delete your account or disconnect Apple.
• Email. If you sign in with an email link or add a recovery email, we process that address and its confirmation state.
• Phone number. A verified mobile number is required to apply for membership; we send a one-time code by SMS to verify it. The number is also used to match referrals and invitations.
• Profile. Username, display name, profile photograph, biography and main city.
• Account state. Account identifier, membership state and rank, membership dates, any special status such as staff, honorary or fee-exempt access, prompts you have dismissed, and which sign-in methods are connected.
• Sessions and security. Authentication sessions, one-time codes, QR sign-in tokens and website session records (browser label, site origin and timestamps). Session secrets are stored as hashes, not in their original form.

Membership application, referral and invitation data

• legal name, date of birth and verified phone number supplied in a membership application, the application status and reviewer decisions;
• referrals: which members vouched for an applicant, and the phone number an applicant selected to request a referral;
• invitations: when a member invites someone by phone, the invited number is stored with the invitation. The invitation message is sent by the member from their own phone, not by MOC;
• preview or promotional membership campaigns you claim.

Applications, referrals, invitations and reports are reviewed by MOC staff.

Membership and payment data

• subscription provider (Apple or Stripe), product, entitlement, renewal or expiry status, cancellation status and related transaction identifiers;
• Stripe and RevenueCat customer identifiers;
• membership history needed to apply the approval and rank rules in the Terms of Service.

Apple and Stripe collect and process payment-card or Apple Account payment details directly. MOC does not receive or store complete card details.

Community and communications data

• thoughts (threads), polls and poll votes, comments, reactions and mentions;
• Photo Dumps, including the caption, the city and the members you tag;
• Moments (photographs that expire after 24 hours) and the record of which members viewed them;
• announcements published by MOC and the audience they target;
• the Spaces you follow and the posts shared in them;
• photographs and other media you choose to upload;
• direct messages, group chats, the members-only group chat, event chats, marketplace chats, meetup coordination chats, message reactions, attachments and replies to Moments;
• profile connections made by scanning another member’s QR code, blocks you set, read and seen state (which posts, Moments and giveaways you have viewed), your notification inbox and mute or folder preferences;
• reports you file or that concern you, the details given, moderation decisions and enforcement records;
• MOC’s recorded decisions about promotions and bans.

Content posted to shared areas is visible to the audience indicated in the Service. Messages are visible to their conversation participants.

Events, signals and travel data

• events you create or organise, co-organisers, sign-ups, invitations, approval decisions, check-ins recorded by QR code and reminder deliveries;
• meetup and request signals with their city, date, context and responses;
• travel presences (city, dates and who may see them).

Atlas places data

• places you add to the Atlas (place identifier, address and coordinates);
• reviews with rating, comment, energy, crowd age, price level, tags and photograph, votes on review comments and likes on review photographs;
• places you collect, with the distance at the time of collection and the collection time;
• short-lived nearby place matches described under “Location and contact data”.

Greymarket marketplace and giveaway data

• listings (title, description, price, currency, condition, size, country and photographs), bookmarks and listing chats;
• deals (counterparty, agreed price, payment timing, notes and each party’s decision), deal feedback and ratings, review reminders and disputes;
• seller statistics derived from deals, such as completed deals, average rating, confirmed violations and open disputes;
• giveaway entries you make, winners drawn and the prize message sent to winners by direct message.

MOC does not itself process payment for transactions arranged between users through the marketplace.

Location and contact data

• city and country selected for your profile, travel, event or signal features;
• location of places and events, including address and coordinates;
• coarse last location. While location permission is granted and the app is in use, the app periodically sends your device location to our backend. The server immediately rounds it to an approximately one-kilometre grid and keeps only the latest value, which is deleted with the account. We use it to decide whether a nearby meetup signal is relevant to you and for Atlas features;
• nearby place matches. The same device location is compared with Atlas places within about one kilometre. For each match we keep the place, the closest observed distance and when it was seen, so that you can collect the place for up to 48 hours. These records contain no raw coordinates and are deleted after 48 hours, when you collect the place or when the account is deleted;
• place scanner and destination suggestions. When you open the Atlas scanner or ask for a destination near you, the device location is used for that request only;
• address-book matching. When you deliberately use the referral or invitation feature, the app sends the phone numbers in your address book (not the names) to our backend to find matching accounts. They are used for that request only; a number is stored only when you request a referral from, or invite, that person.

Exact coordinates are used for the request and are never stored as a location history. Location and contacts permissions can be withdrawn in iOS Settings at any time; the related features then stop working.

Discord data

If you connect Discord, we process the Discord account ID, username, display name, avatar reference and role-synchronisation status. We use this only to link the accounts, add you to the MOC server and add or remove the membership role. Disconnecting Discord removes the managed member role and the stored account link.

Device, usage and technical data

• push token, platform and push delivery records (notification content, delivery status and errors);
• app version, build and platform used for maintenance, minimum-version checks and app updates. Update checks send version information and a random installation identifier to Expo;
• an anonymous launch event sent to Expo on each app start (random installation identifier, app version, platform and operating-system version), which is not linked to your account;
• product interactions such as reactions, votes, attendance, read and seen state and feature use;
• IP address, request metadata, timestamps, security events and error logs generated by our infrastructure and service providers;
• camera, photo-library, contacts, location and notification permission status. We use these capabilities only for the feature you choose: the camera is used to scan QR codes and to take photographs you choose to share, and the microphone is not used.

We do not use personal data for third-party advertising, sell personal data, or track users across other companies’ apps or websites.

• Apple: your sign-in details and, through RevenueCat, your subscription status.
• Stripe: subscription and billing status for a website subscription.
• Other users: referrals and invitations naming your phone number, mentions, tags in Photo Dumps, event invitations and check-in verifications, reports, and ratings and feedback on deals with you.
• Discord: the account details listed above when you connect Discord.

We process personal data for these purposes and legal bases:

Where processing relies on consent, consent may be withdrawn at any time. Withdrawal does not affect processing already carried out lawfully.

• Your username and rank are visible to every signed-in user. Your display name, profile photograph, biography and main city are visible only to members, to you and to MOC staff; other users see a masked profile.
• Shared content is visible to the audience shown in the app: the main feed and Spaces to members, announcements to the audience MOC selected, Moments to members for 24 hours, listings and giveaways to signed-in users.
• Messages are visible to the participants of the conversation. Every member is a participant of the members-only group chat.
• Membership applications, referrals, invitations and reports are visible only to MOC staff.
• Event organisers see sign-ups and check-ins for their events. Deal counterparties see the deal terms, feedback and ratings.
• Blocking a profile hides you from each other in feeds, profiles, search, notifications and new conversations.
• After account deletion, retained shared content shows the label “Deleted member”.

We disclose data only as necessary to operate the Service, comply with law or protect users. Current categories of recipients include:

• Supabase (EU hosting) for authentication, database, storage and backend services;
• Apple for Sign in with Apple, App Store subscriptions, push notifications, Apple Maps and location services;
• RevenueCat for subscription validation and management;
• Stripe for website checkout, billing, invoices and the customer portal;
• Expo for app updates, push-notification delivery and launch telemetry;
• Google Maps Platform for place search, place details and time zones, requested through our backend;
• Discord when you connect Discord and for server-role management;
• Bird (MessageBird) for delivery of verification SMS messages;
• Postmark for delivery of account emails;
• Vercel for hosting the MOC website;
• professional advisers, authorities or courts where disclosure is required or reasonably necessary.

These providers process data under their own terms and, where they act as our processors, under data-protection commitments. Notification content passes through Expo and Apple only for delivery.

We may disclose data in connection with a merger, financing, reorganisation or sale of all or part of the business, subject to applicable law and appropriate safeguards.

Some providers may process data outside Estonia or the European Economic Area. Where required, we use an adequacy decision, the European Commission’s Standard Contractual Clauses, or another lawful transfer mechanism, together with supplementary safeguards where appropriate. Information about a specific transfer mechanism is available from the privacy contact above.

We keep personal data only for as long as reasonably necessary for the purposes described above:

• account, profile, membership and application data are generally retained while the account exists;
• only the latest coarse location is kept, and it is deleted with the account; nearby place matches are deleted after 48 hours, on collection or with the account;
• Moments are deleted 24 hours after publication, or earlier when the author stops being a member; replies to a Moment remain in the conversation as text;
• Photo Dumps leave the main feed 48 hours after posting but remain on the author’s profile until the author deletes them or the account;
• meetup coordination chats are deleted 48 hours after the meetup date;
• one-time codes and QR sign-in tokens are short-lived; website sessions expire or can be revoked;
• push tokens are retained while needed for delivery and removed when the account is deleted or the token becomes invalid; push delivery records are kept for a limited period for troubleshooting;
• the Apple sign-in token is deleted when you disconnect Apple or delete your account;
• referral and invitation records are deleted with the account of the person who created or received them;
• personal profile content (Photo Dumps, Moments, collected places, blocks, connections, notifications and read state) is deleted with the account;
• shared threads, polls, announcements, comments, listings, deals, reviews, events, conversations and giveaway records may be retained under a de-identified “Deleted member” profile while needed to preserve community discussions, transaction evidence, safety records and dispute history, subject to moderation and legal-retention requirements;
• subscription, invoice, accounting, fraud-prevention, dispute and legal records may be retained for the period required by law or needed to resolve a claim;
• infrastructure logs, launch telemetry and backups are retained on limited rolling schedules set according to security, recovery and legal needs.

When data is no longer required, we delete it or irreversibly anonymise it.

You can edit your profile in the app and manage your sign-in methods (Apple, recovery email and phone number) in Settings. Notifications, location, contacts, camera and photo permissions can be changed in iOS Settings, Discord can be disconnected, and website sessions can be revoked. You can block or report any profile from that profile’s page.

Account deletion can be started in Profile → Settings → Manage Account → Delete Account. Deletion:

• revokes The Bay’s Sign in with Apple authorisation and disconnects Discord;
• permanently deletes the authentication account and every sign-in method;
• deletes your personal content and account data: Photo Dumps, Moments, collected places, blocks, connections, notifications, referrals and invitations, push tokens, location data, travel presences, event sign-ups and check-ins, read state and your membership application;
• removes the profile’s username, display name, photograph, biography, city and membership status.

Shared discussions and transaction, conversation, event, review, giveaway, moderation or legal records may remain under the de-identified label “Deleted member” where they are needed by other participants or for safety, fraud prevention, transactions, disputes or legal obligations.

Deleting a The Bay account does not automatically cancel a subscription managed by Apple or Stripe. Cancel an Apple subscription in your Apple Account subscription settings and a Stripe subscription through the MOC billing portal.

For additional access, correction, deletion or objection requests, email info@mocworldwide.com.

Subject to applicable law, you may have the right to:

• access personal data and receive a copy;
• correct inaccurate or incomplete data;
• request deletion or restriction;
• object to processing based on legitimate interests;
• receive data in a portable format where applicable;
• withdraw consent;
• lodge a complaint with a supervisory authority.

In Estonia, the supervisory authority is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon). You may also contact the authority in the EEA country where you live or work.

We may need to verify your identity before fulfilling a request. Statutory exceptions may apply.

We use measures designed to protect personal data, including authenticated access, row-level database controls, restricted administrative access, private media storage with time-limited links, hashed session secrets, encrypted storage of sign-in tokens, encrypted connections and access logging. No system can guarantee absolute security.

The Service is not directed to anyone under 18, and applications from people under 18 are rejected. If we learn that a minor has provided personal data, please contact us so that we can investigate and delete it where appropriate.

We may update this policy when the Service, providers or legal requirements change. We will publish the updated version and its effective date and, where required, provide additional notice in the Service.

MOC Worldwide OÜ
Registry code 17538821
Harju maakond, Tallinn, Kesklinna linnaosa
Tartu mnt 67/1-13b, 10115
Estonia
info@mocworldwide.com