Privacy, minus the mystery

Your night out.
Your choices. Your data.

This policy explains what Drinkify handles, why it is needed, who can see it, and the controls you have—without hiding the important parts in legal fog.

Effective July 31, 2026Last updated July 31, 2026For users 21+
Read the policy
The short version
01

Foreground location only

Drinkify asks for precise location only when you use nearby-venue or check-in features. It does not request background location.

02

Limited first-party analytics

Drinkify counts fixed screen and home-feature opens and featured drink or food clicks. It does not use third-party analytics SDKs, advertising trackers, or cross-app behavioral ads.

03

You choose what to share

Media, check-ins, safety updates, and location access are feature-driven. You can edit content, manage permissions, block or report users, and request deletion.

01

Start here

Overview

This Privacy Policy applies to the Drinkify mobile app and this privacy website. Drinkify is a social app for adults 21 and older to connect with friends, plan gatherings, share stories, explore nearby venues, and use safety-focused features for nights out.

In this policy, “Drinkify,” “we,” “us,” and “our” refer to the operator of the Drinkify service. “You” means a person who visits this site or uses the app. Questions about the operator or this policy can be sent to support@drinkify.cc.

Good vibes only. Safe rides always.Alcohol is optional. Respect, consent, and never drinking and driving are not.
02

The details

Information we handle

Account and security

Your mobile phone number, account identifier, authentication session, and account-security activity. Supabase Auth and Twilio Verify process your phone number and one-time SMS codes for passwordless registration and sign-in. The current mobile app does not offer email-and-password login or authenticator-app TOTP. A legacy email identifier may remain on an older account while that account is being migrated or until it is deleted. Drinkify records a versioned 21+ affirmation and safety-pledge acknowledgement with your account, plus local completion flags on your device. It does not collect a birth date for this age attestation.

Profile and social activity

Information you add to your profile, such as your name, nickname, handle, zodiac sign, favorite drink, quote, and profile photo; plus friends, blocks, gatherings, invitations, gifts, game-player names, favorites, messages, and related activity. While online-status sharing is enabled, Drinkify stores one private foreground heartbeat and shows accepted, unblocked friends only a simple online indicator—not an exact last-seen time. The current app no longer asks for a birthday; a legacy value previously supplied may remain until it is cleared or the account is deleted.

First-party product analytics

When you are signed in, Drinkify records your account identifier, one fixed event name when you open a supported app screen or home feature or select the featured drink or food, and the server-recorded time. The analytics record has no content, phone number, contacts, location, venue-search text, device identifier, session identifier, or free-form metadata. Recently phone-verified administrators can view aggregate account totals, account-creation windows, tap counts, and distinct-user counts, but not individual raw analytics events.

Contact matching

If you choose Find from Contacts and grant permission, Drinkify reads phone-number fields from the contacts you make available. Numbers are normalized and sent through an encrypted connection to a restricted matching service. The service compares keyed representations of those numbers with discoverable Drinkify accounts, returns matching profiles, and does not add contact names, notes, addresses, birthdays, photos, or relationship details to your Drinkify profile. You can revoke contact access in device settings and control whether your own verified number may be discovered by other users' contact matching.

Content and media

Photos and videos you select or capture, audio included in a video, story captions, story views, venue submissions, check-ins, safety messages, and content reports. Story objects use private Supabase storage and are delivered to authorized viewers through short-lived signed URLs. Blocking stops Drinkify from issuing new story links, but a link issued before the block can remain usable until its 10-minute expiration. Profile photos, venue photos, venue banners, and administrator broadcast media currently use public Supabase object URLs. Someone who copied one of those public URLs may be able to open it outside the app until the object is physically removed. Images are re-encoded before upload, but selected videos may still contain embedded file metadata. Other users may also copy or share content outside its intended audience, so only post media you are comfortable sharing.

Foreground location and venue searches

With your permission, the app can access precise location while you are using it to center maps, find nearby venues, and offer proximity-based check-ins. Search text, the visible map area, and coordinates may be processed through Supabase and Google Places or Maps. Drinkify does not request background location or continuously broadcast your location.

Safety and moderation

Safety preferences, ride-plan and emergency-contact text you choose to enter, safe check-in messages, reports, report details, and moderation actions. Ride-plan and emergency-contact notes are intended as private account settings; only add another person's details with permission. The current app does not run live or background location sharing and clears the unused legacy share-location preference when settings are saved.

Support and privacy requests

If you contact support, we handle your sender address, message, attachments, account-verification information, and the request and resolution history. Never send a one-time sign-in or admin verification code.

Technical information

Service providers may process IP address, request time, device or app information, session identifiers, and security logs as part of hosting, authentication, and fraud prevention. The current Drinkify app does not include third-party ad, attribution, analytics, or crash-reporting SDKs. The limited first-party analytics described above is processed directly through Drinkify's Supabase backend.

Access is also limited by account eligibility, friendship, group membership, blocking, moderation status, and the visibility controls for each feature.

Who can see what you share
FeatureTypical audience
Profile detailsEligible people who can discover your profile in the app, subject to blocks
Profile photoDisplayed to eligible people in the app; the underlying public object URL can be opened by someone who has copied it
StoriesAuthorized friends or administrator-story viewers through 10-minute signed links; blocks stop new access but do not revoke a link already issued
Direct messages and giftsThe sender and intended recipient
Group messagesCurrent members of the group, subject to blocks and moderation controls
Gatherings, games, and safety check-insRelevant invited members or participants
Venue check-insFriends when you choose the option to tell them
Reports and report detailsAuthorized moderators and service personnel who need access
03

Purpose

How we use information

  • Register, secure, and support your account.
  • Show the profile, social, messaging, story, gathering, gift, game, venue, and safety features you request.
  • Find nearby places and support optional venue check-ins.
  • Deliver phone-verification texts and other service-related communications.
  • Moderate user-generated content, respond to reports, prevent abuse, and keep the community safer.
  • Measure aggregate account growth and use of supported screens, home features, and featured drink or food selections so we can evaluate and improve the app.
  • Maintain, troubleshoot, and protect the app and its infrastructure.
  • Comply with law and enforce service rules.

This privacy website does not intentionally set advertising or analytics cookies.

04

Outside Drinkify

When information is shared

Information may be disclosed in these limited situations:

  • With other users, when a feature is designed for sharing, such as profiles, stories, messages, gatherings, gifts, or check-ins. Accepted and unblocked friends can also see a simple online indicator while you have online-status sharing enabled, but not your exact last-seen time.
  • With service providers, including Supabase for authentication, database, storage, realtime updates, edge functions, and first-party analytics processing; Twilio Verify for sending and protecting phone-verification texts; Google services for places, Android maps, or geocoding; Apple or the device platform for mapping on supported devices; the final website host; and the support-mail provider selected for launch.
  • At your direction, when you copy or share an invite, open directions in a maps app, or share information with another app you choose. That app’s policy then applies.
  • For safety and legal reasons, when reasonably necessary to respond to valid legal process, protect rights and safety, investigate abuse, or enforce service rules.
  • As part of a business transfer, if the service or its assets are reorganized, financed, acquired, or transferred, subject to applicable law and continued protection of the information.
05

Controls

Your choices

Device permissions

Use iOS or Android settings to allow or revoke camera, microphone, photo-library, and location access. Some features will not work without the permission they need.

Profile and content

Edit your profile, remove stories, manage friendships, leave gatherings, choose whether to tell friends about a venue check-in, and turn friend online-status sharing off. Online-status sharing is on by default. Turning it off removes your server heartbeat and stops foreground updates; friends' already-open screens clear the cached dot on their next refresh, normally within 30 seconds.

Safety and community

Block users and report profiles, stories, messages, gatherings, or gifts that violate community expectations.

Messages

Deleting a conversation hides it from your account. The other person may still keep their copy, and safety or moderation records may remain.

06

Lifecycle

Retention and deletion

We keep information while it is reasonably needed to provide Drinkify, maintain safety and security, resolve disputes, and meet legal obligations. The exact period depends on the type of information and why it is kept.

Account-linked raw product-analytics events are kept for no more than 90 days. Processing account deletion removes those linked raw events through a database deletion cascade. De-identified daily aggregate counts cannot be connected back to an account and are also kept for no more than 90 days. Recently phone-verified administrators receive aggregate counts only.

Drinkify stores only the latest foreground heartbeat for each signed-in session used for friend-only online status. A stopped heartbeat no longer shows you online after about 90 seconds and is scheduled for deletion once it is more than 10 minutes old. Disabling online-status sharing removes all of your server heartbeats immediately; friends' already-open screens clear the cached dot on their next refresh, normally within 30 seconds. The sharing preference remains until you change it or delete your account.

Safety check-in history is limited to the newest 10 entries for each account and is retained for no more than seven days. A separate notification copy sent to gathering members follows the notification retention rules.

Retention follows the reason the information exists.Account and social records are generally kept while the account or feature remains active. User-requested deletion removes or de-identifies eligible records, while reports, fraud-prevention records, legal holds, support correspondence, and security logs may be kept longer when reasonably necessary. Provider backups are overwritten through their normal protected backup cycle rather than edited one record at a time.

User stories are designed to leave active display after 24 hours. An administrator may select a shorter or longer display period for an official Drinkify story, up to 30 days. That does not necessarily mean every stored copy, log, or backup is erased at that exact moment. Moderation, security, and legal records may be kept longer when reasonably necessary.

Delete your Drinkify account

In the app, open Profile → Account → Delete Account and confirm the request. Once processed, account-associated information is deleted or de-identified unless it must be retained for security, safety, legal, or dispute-resolution reasons. Account deletion queues associated uploaded media for verified physical removal. A previously copied public- media URL can remain usable until that removal completes. Copies another person independently saved outside Drinkify, such as screenshots or downloads, cannot be removed from that person's device. Linked raw product-analytics events are deleted with the account; de-identified daily counts can no longer be tied to it and age out within 90 days.

View web deletion instructions
07

Protection

Security

Drinkify uses administrative, technical, and organizational safeguards appropriate to the service, including authenticated access, permission controls, encrypted network connections, and additional verification for sensitive moderation tools. No internet service can guarantee perfect security, so protect your device and mobile service account, never share an SMS verification code, and report suspicious account activity.

08

Requests

Your privacy rights

Depending on where you live, you may have rights to request access, correction, deletion, restriction, objection, portability, or information about how your personal information is handled. You may also have a right to appeal a denied request or contact your local data-protection authority.

We may need to verify your identity before completing a request. Some rights have legal exceptions—for example, when information is needed for safety, fraud prevention, a legal claim, or another person’s rights.

09

Eligibility

Drinkify is for adults 21+

Drinkify is intended only for people who are at least 21 years old. Do not create or use an account if you are under 21. If you believe an ineligible person submitted information, use the contact route below so the account can be reviewed and appropriate action can be taken.

The app asks for an explicit 21+ self-attestation before account creation and records the current affirmation and community-pledge versions. This is a self-attestation, not identity-document or independent age verification.

10

Updates

Changes to this policy

We may update this policy as Drinkify changes. The “Last updated” date at the top will show when the policy was revised. When a change is material, we will provide additional notice in the app or through another appropriate channel.

11

Questions and requests

Contact Drinkify

For a privacy question, rights request, support issue, or account-deletion request, email Drinkify Support. You can also open Profile → Account → Help & Support in the app.

support@drinkify.cc

Include the phone number on your account when account verification is needed, but never include a one-time verification code.

Never send a one-time sign-in or admin verification code in a support request.

Back to top