🛡

NiteCrew

Privacy Policy

Last updated: October 1, 2026

NiteCrew provides social planning, venue discovery, games, and harm-reduction safety tools. This Privacy Policy explains what data we collect, how it is used and shared, and your choices. Movement estimates are not medical measurements or a way to determine whether you are safe to drive. We do not sell your data or use it for advertising.

1. Who We Are

NiteCrew is an independent mobile application. If you have any questions about this policy, contact us at: daniel@gravity666666.com

2. Data We Collect

Account Information

Email address, display name, and username handle — used for your account, recovery, and social features
Password — stored as a secure one-way hash rather than readable text
Authentication and session records, including Google or Apple provider identifiers and sign-in information when you use social sign-in. Providers may supply your name, email, and, where available, a profile picture

Profile Information (provided by you)

Phone number, age range, interests, and profile photo — stored on our servers when provided for your profile and related features
Home address, saved home coordinates, and preferred ride app — stored on your device and synced to our servers for ride-home features
Valuable items and checklist state — stored on your device and synced to our servers; group-member checklist information may also be shared within a group
Profile photos may appear in social and plan features. Profile-photo URLs can be accessed without signing in, so do not upload an image you need to keep private

Location & Safety Data

Location may be accessed for Safe Mode, SOS, group location sharing, safe zones, Friend Radar, Free Right Now, nearby venues, and ride-home features
Current coordinates are sent to our servers for enabled sharing and proximity features. Nearby-venue searches also send coordinates to Google Places and record search coordinates in server-side usage events
Trusted contact names and phone numbers, and safe zone names, coordinates, and radii — stored on our servers
SOS messages can include your name, current location, and a map link. The app opens a pre-filled SMS composer; you must send the message yourself

Safe Mode & Movement Data

Session timing, movement baseline, and session history are stored locally on your device
Accelerometer and gyroscope recordings are processed on-device for movement estimates in Safe Mode and Drink Pace Tracker; raw sensor recordings are not transmitted to our servers
Computed test scores and result categories can be sent in usage events. A test result can also update your group status; results are therefore not exclusively local

Group Session Data

Group names, invite codes, membership, chat messages, status information, ride requests, reports, and item verifications — stored on our servers for group features
Location is shared with members of an active group when you enable group location sharing
Ending a group session stops active sharing and clears active location coordinates, but does not automatically delete the group, its chat, or all associated history

Events & Plans

Plan details — including title, description, schedule, venue or address, activities, and cover or poster media — are stored on our servers when published
Plan attendee roster, RSVP responses, poll votes, and chat messages are stored on our servers so the plan can be coordinated
Reports about plan content or activity are stored for moderation and are restricted to administrators, not disclosed to the plan host
Plan access depends on your invitation or membership. Invite previews withhold private addresses; rosters, chat, and voting are protected by plan access controls
Invite links contain bearer tokens. Server-side token hashes, expiry information, and use limits allow links to be validated and controlled. Anyone with a valid link may be able to open its invite preview
Unpublished plan drafts are saved locally. Optional calendar actions can copy plan details into a device calendar, calendar file, or another calendar service you select

Bar Hopping

Saved venue details — including names, addresses, coordinates, ratings, hours, photos, list order, and visited status — are stored on our servers
Venue comments, author information, timestamps, and optional uploaded photos — stored on our servers or file storage. Other app users viewing that venue can see its comments and attached photos
Personal lists can be shared with selected groups. Saved lists are not automatically erased when a group session ends

Friends & Social Data

Friendships, friend requests, Crew relationships, and blocks — stored on our servers to support social features and access controls

Friend Radar

Friend Radar is opt-in. Current coordinates are stored server-side while broadcasting, and eligible friends who are also actively broadcasting can receive proximity information
Inactive broadcasts are excluded using freshness checks. Stopping Radar clears current coordinates, but the broadcast record may remain; inactivity is not a promise of immediate deletion

Free Right Now

Your selected activities, note, audience, availability duration, and location signal are stored on our servers to show availability and find matches
Availability signals use rounded coordinates. Separate, time-limited location-sharing records can contain precise coordinates and accuracy
Map visibility requires active, eligible sharing on both sides and respects your selected audience. Friends receive approximate positions; Crew members may receive precise positions

Push Notifications

With notification permission, device push tokens are stored on our servers to deliver game, friendship, group, plan, chat, availability, and proximity alerts
Push tokens and notification payloads are processed by Expo and the relevant platform push providers to deliver alerts. Notification previews may be visible on your lock screen
You can change app notification preferences or revoke permission in device settings

Achievements & Game Data

XP, badges, and titles — stored on our servers and may be visible to friends
Nine Lives match history (participants, outcome) — stored server-side and associated with your account
Number Bomb, The Drop, Tick Tick Boom, and Dice Roll exchange player names, actions, and live game state with participants. Live game state and feature-usage logs are different records; ending a game does not erase usage logs
Cocktail Builder generates draws on-device; feature interactions may be recorded in account-linked usage events

Usage Events & Technical Logs

Feature interactions are recorded server-side and can be associated with your account ID. These records are not fully anonymous
Event metadata can include feature or plan identifiers, actions, platform, venue information, movement-test scores and categories, and nearby-search coordinates
Usage records help measure feature adoption and improve the app. Technical errors may also appear in server logs used for troubleshooting

3. How We Use Your Data

Authenticate and recover accounts, save preferences, and enforce privacy and access controls
Provide safety tools, user-initiated SOS messages, group sharing, and ride-home handoffs
Coordinate plans, invitations, RSVPs, voting, chat, calendar actions, and moderation
Support friends, Crew, opt-in discovery and availability, venues, shared lists, games, and achievements
Deliver permitted notifications, investigate technical problems, and measure feature use to improve the app

We do not sell personal data, sell analytics to third parties, or use your data for advertising.

4. Sharing & Third-Party Services

Other users receive the profile, group, plan, venue-comment, game, and availability information appropriate to the feature and its access controls. Share only content you intend those users to see
Trusted contacts receive the information in an SOS or other SMS when you send it. A group ride helper may receive the location and destination needed to assist with a ride
Google and Apple process social sign-in requests under their own privacy policies
Google Places processes venue and address searches, including coordinates where relevant, and supplies venue details and photos
Resend processes email delivery, including account-recovery messages and the recipient email address
Expo and platform push providers process tokens and notification payloads for delivery
Uber or Lyft handoff links can include pickup coordinates and destination coordinates or address. Those services process the information under their own privacy policies
Calendar apps or services receive plan details when you choose to add, export, or share a calendar event
Hosting, database, and file-storage providers process the data needed to operate NiteCrew

We do not share your data with advertisers or data brokers. Services you choose to open have their own privacy policies.

5. Data Storage & Security

Account, profile, social, safety, plan, venue, notification, and usage data are stored on our servers or service-provider storage as described above
Local drafts, session history, movement baselines, and native calendar-event mappings are kept on your device. Raw motion recordings are processed on-device; computed results may be transmitted as described above
App communication with our public servers uses HTTPS. Passwords use one-way hashing, and access controls protect restricted features

No storage or transmission method is completely secure. Publicly accessible profile-photo links and content shared with other users should not be treated as confidential.

6. Device Permissions

Location (GPS)

Location permission supports enabled safety, proximity, availability, venue, and ride features. Current sharing uses foreground location updates; keeping a feature enabled does not guarantee updates while the app is in the background. You can stop sharing in the app or revoke permission in device settings.

Push Notifications

Notification permission enables the alerts described above. Denying permission prevents push delivery; you can still use other app features, but should not rely on receiving safety or coordination alerts.

Motion Sensors

Safe Mode, Movement Baseline, and Drink Pace Tracker use motion sensors to compute movement estimates. Raw samples are processed locally; computed results can be used in server-side usage events and group status.

Camera & Photos

Camera access supports QR scanning and optional photo capture. Photo selection supports profile photos, venue-comment photos, and plan media. Images you choose for upload are transmitted to store or publish that content; we do not upload your entire photo library.

Calendar

On supported devices, adding a plan to your calendar requests calendar access and writes its title, schedule, location, notes, and link. Calendar and event identifiers are stored locally, not sent to our servers. Calendar-action usage events can include a plan identifier and platform. Exports or external calendar links share event details with the calendar app or service you choose.

SMS

The app opens a pre-filled SMS composer for supported safety actions. You must send the message yourself. We do not read your SMS history or send SMS automatically.

Contacts

We do not access your device's contacts. You manually enter trusted contact names and phone numbers within the app.

7. Data Retention

Local data remains until removed using available app or device controls. Uninstalling and data removal depend on your device and backup settings; uninstalling does not delete your server account
Account and saved feature data are retained while your account exists or until removed through available deletion controls
Plans, conversations, moderation reports, and saved lists are not automatically erased simply because an event or group session ends. Ending group sharing clears active location coordinates, not all group history
Stopping Friend Radar clears current coordinates. Inactive broadcast records may remain, although stale broadcasts are excluded from live discovery
Ended or expired Free Right Now signals and related history are generally purged after 24 hours by periodic cleanup, rather than deleted immediately when availability ends
Usage event logs currently have no fixed automatic deletion period and can remain associated with your account ID after account deletion
Settings offers Delete Account, which removes your account and associated records covered by that process, including your profile photo. It does not automatically remove every usage log or uploaded file
For deletion of remaining data, contact daniel@gravity666666.com so we can review your request. Do not assume that stopping a feature, deleting your account, or uninstalling erases every server-side record

8. Your Rights

Depending on your location, you may have the right to:

Access the personal data we hold about you
Request correction of inaccurate data
Request deletion of your account and data
Request a copy of your personal data
Object to or restrict processing of your data

To exercise any of these rights, contact us at daniel@gravity666666.com. We will respond within 30 days.

9. Children's Privacy

NiteCrew is intended for users who are of legal drinking age in their country (18+ in most countries, 21+ in the United States). We do not knowingly collect data from minors. If you believe a minor has created an account, contact us immediately.

10. Changes to This Policy

We may update this policy as the app changes. The last-updated date identifies the current wording. Please review the policy periodically; any notice required by applicable law will be provided.

11. Contact Us

For any privacy-related questions or requests, please contact us at:

daniel@gravity666666.com