Niighty Join TestFlight

Privacy Policy

Sprint 0 draft

What Niighty collects, why it collects it, how long it keeps it, and the control you have over location and friend sharing.

Effective date: To be set at launch Draft v0.2 · October 20, 2026

1. Who we are

Niighty is an early-stage nightlife app for OSU students. It helps you decide where to go on Friday and Saturday nights using three separate signals: live crowd reports, early interest, and weekend patterns.

In this policy, “Niighty,” “we,” “us,” and “our” refer to the Niighty project team responsible for the Service. The Service includes the Niighty iOS app, this website, and related features.

This policy does not cover third-party websites, maps, or services that have their own privacy policies. Our contact for privacy questions is privacy@niighty.app.

2. 18+ requirement

Niighty is for adults who are at least 18 years old. The Service is not directed to children, and we do not knowingly collect personal data from anyone under 18. We may ask you to confirm your age when you create an account.

If we learn that an account belongs to a person under 18, we will delete the account and its personal data. If you believe a minor is using Niighty, contact privacy@niighty.app.

3. Data we collect

We collect the categories below. Some are necessary to create an account and use core features. Others depend on permissions you grant or features you choose to use.

Account information

Email address, password (stored in hashed form by our authentication provider), authentication identifiers, and the date you create your account. In the current build, your email address is your account identifier and we do not verify that you own it.

Why To create and secure your account, sign you in, and contact you about the Service.

Legal basis Performance of a contract; our legitimate interests in keeping the Service secure.

Profile, age confirmation, and friend connections

The display name you choose; whether you have confirmed that you are at least 18 and when you did so; and your friend connections, including pending and accepted requests. Your friend list is not public.

Why To show your display name to friends you connect with, enforce the 18+ requirement, and operate the friends feature.

Legal basis Performance of a contract; consent for friend sharing; legal obligation for age gating where applicable.

We store these details with your account. Friend connections exist only when you add friends.

Crowd reports

The venue; crowd level (Dead, Normal, Busy, or Packed); vibe (Skip, Worth It, or Must Go); timestamp; whether the report was location-verified; and the approximate distance used for that verification.

To detect abuse, we may also store a hashed IP value associated with a report. We do not store the raw IP address for that check.

Why To calculate live crowd status and weekend aggregates, show the current vibe, verify reports, and detect misuse.

Legal basis Performance of a contract; legitimate interests in operating a trustworthy Service; consent where location is used.

You can submit a report without sharing location, but unverified reports carry less weight.

Location

While the app is open, we use your device’s location to show nearby venues and map context and to check whether a crowd report came from the venue. We store the verification result and approximate distance for a report, not a continuous location history.

If you enable optional on-site reminders after you have submitted reports, the app may also use background location (the Always permission) to detect when you arrive at a supported venue and prompt you to submit a report. Background location is off by default, is used only for that arrival prompt, and can be turned off at any time in the app or iOS Settings. The MVP does not require background location, and geofence reminders may be disabled.

Why To show nearby venues and map context, verify reports, reduce false or remote submissions, and — only if you opt in — send on-site reporting prompts. Location is not used as a passive crowd signal or for advertising.

Legal basis Consent, through the iOS location permission. You can deny or revoke it in iOS Settings.

If you deny location, the map still opens, but nearby venues may not be centered and live crowd status may not appear.

Last-known venue and friend-sharing settings

The venue you were last associated with, when it was updated, and which friends you have enabled sharing for. We keep one latest venue record, not a trail.

Why To show a venue name and “x minutes ago” to friends you explicitly authorize. Sharing is off by default and granted per friend.

Legal basis Consent.

The record supports the friends feature. It is visible to a friend only if you enable sharing with that friend, and it is deleted with your account.

Venue view events

The venue page you opened and the time. If you are signed in, the view may be linked to your account; signed-out views are not. These events are rolled up into hourly counts used for pre-heat labels, and raw events are deleted after 30 days.

Why To produce pre-heat interest labels and understand which venues people are exploring.

Legal basis Legitimate interests in understanding and improving the Service; consent where required.

RSVPs and interest signals

The venue or event you RSVP to or mark interest in, and the time. We show calibrated qualitative labels, not raw RSVP counts.

Why To produce pre-heat labels and understanding of early interest.

Legal basis Performance of a contract; legitimate interests in operating the Service.

Push notification tokens

A device push token and your notification preferences.

Why To deliver notifications you enable, including optional on-site reporting prompts if that feature is turned on.

Legal basis Consent, through the iOS notification permission.

Analytics events

Events about how you use the app, such as screens viewed, actions taken, app version, device type, and performance information. We use PostHog for product analytics.

Why To understand how the app is used, diagnose problems, and improve the product.

Legal basis Legitimate interests in improving the Service; consent where required.

Venue chat and content reports

Messages you post in venue chat and reports you submit about content, venues, events, or users.

Why To provide chat, review reports, moderate the community, and enforce our Terms.

Legal basis Performance of a contract; legitimate interests in safety and moderation; legal obligations.

Venue chat is visible to other users in that chat. Do not post personal information you want to keep private.

4. How we use data

We use the categories above to:

  • Provide, operate, and maintain the Service.
  • Create and secure accounts, and authenticate sign-ins.
  • Verify crowd reports and calculate live crowd status.
  • Produce pre-heat interest labels from venue views and RSVPs.
  • Show a last-known venue to friends you explicitly authorize.
  • Send notifications you enable.
  • Moderate content and enforce our Terms of Service.
  • Detect, prevent, and address abuse, fraud, and security issues.
  • Understand usage and improve features and reliability.
  • Comply with law and respond to lawful requests.
  • Communicate with you about the Service.

Automated processing. We use rules to combine reports, down-weight unverified reports and new accounts, and calculate crowd levels. These rules do not make legal or similarly significant decisions about you.

6. California privacy rights and no sale

If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act (CCPA/CPRA), may provide you with the following rights:

  • To know and access the categories and specific pieces of personal information we collect.
  • To delete personal information, subject to exceptions in the law.
  • To correct inaccurate personal information.
  • To opt out of the sale or sharing of personal information.
  • To limit the use and disclosure of sensitive personal information.
  • To be free from discrimination for exercising these rights.

We do not sell personal information. We do not sell or share precise location for cross-context behavioral advertising. We use precise location to show nearby venues and map context, to verify crowd reports, and, when you use the friends feature, to determine your last-known venue. If you opt in to optional on-site reminders, background location may be used on your device to detect arrival at a supported venue and prompt a report; this is off by default and can be turned off at any time. Friends receive your display name, venue name, and timestamp — never your coordinates or a location trail. We treat precise geolocation as sensitive personal information and do not use it to infer characteristics about you.

To make a request, contact privacy@niighty.app. We may need to verify your identity before acting. You may use an authorized agent where the law allows. We will honor the rights that apply to you under applicable law.

This draft is not a representation that any particular privacy law applies to Niighty today. Final applicability and required disclosures will be confirmed before launch.

7. Friends and location sharing

Friend location is a separate, opt-in feature. This is exactly how the MVP is designed:

  • Friend connections. We store pending and accepted friend connections and the display name your friends see. Your friend list is not public.
  • Off by default. Creating an account, accepting a friend request, or adding a friend does not turn sharing on.
  • Per-friend switch. You enable or disable sharing for each accepted friend. Turning one friend off does not affect any other friend.
  • Venue name, not coordinates. A friend with access sees your display name, the venue name, and how long ago it was updated (“x minutes ago”). They do not see your coordinates, a map pin for you, your crowd reports, your chat messages, or a list of past venues.
  • Latest venue only. We keep one last-known venue record per account, updated while you use the app in the foreground. It is not a location trail.
  • Revoking access. If you turn sharing off, the friend can no longer read your last-known venue. If you delete your account, the record is deleted.
  • No coordinates. The friends feature returns venue names and timestamps, not latitude or longitude.
  • Sensitive location. Under California law, precise geolocation can be sensitive personal information. We use location to show nearby venues and map context, verify reports, support the opt-in friends feature, and — only if you enable them — send optional on-site reminders. We do not use it for advertising.

Crowd reports are aggregated before other users see them. Friends do not see which reports you submitted.

8. Retention

We keep personal data only as long as needed for the purposes described in this policy, with the specific periods below.

Raw crowd reports crowd_reports
Retention30 days
Deleted after 30 days. Aggregated status and history remain in anonymized form.
Raw venue view events venue_view_events
Retention30 days
Deleted after 30 days. Hourly rollups and pre-heat labels may remain in aggregate form.
Last-known venue user_last_venue
RetentionLatest record only
One record per user, replaced when it changes. Not a trail. Deleted with the account.
Aggregated crowd status and weekend history
RetentionRetained
Anonymized or aggregated; not linked to your account.
Account information
RetentionWhile your account is active
Deleted when you delete your account.
Profile, age confirmation, and friend connections
RetentionWhile your account is active
Deleted when you delete your account; friend connections are removed for both sides.
RSVPs and sharing settings
RetentionWhile your account is active
Deleted with the account.
Push tokens
RetentionWhile notifications are enabled
Deleted on account deletion or when a token is no longer valid.
Analytics events
Retention12 months
Deleted after 12 months, or earlier if you delete your account (account-linked analytics identifiers are deleted or de-identified). PostHog event retention is set to 12 months.
Venue chat messages
Retention12 months after posting
Deleted after 12 months, or earlier if you delete your account or the message is removed for moderation.
Content reports
Retention24 months after the report is closed
Kept to enforce our Terms, review repeat abuse, and meet legal obligations; reporter identifiers are removed when the account is deleted except where retention is required by law.

Account deletion cascades. Deleting your account cascades through personal data in our active systems, including your account, display name, age-confirmation record, friend connections, crowd reports, RSVPs, last-known venue, sharing settings, raw venue view events, chat messages, push tokens, and account-linked analytics identifiers (deleted or de-identified). Content reports you submitted are anonymized and retained only as needed for moderation or legal obligations. Anonymized aggregates that cannot reasonably identify you may remain. We may retain limited information where required by law or to resolve disputes.

Deleting the app from your phone does not delete your account or the personal data stored by the Service.

9. Service providers

We use the following providers to operate Niighty. They process data to provide services to us or as independent providers under their own terms and privacy policies.

Supabase

Authentication (email and password), PostgreSQL database, edge functions, and storage.

Email and SMS providers

Not used for sign-in in the current build: Niighty does not send sign-in codes or confirmation emails. If email or SMS delivery is added later (for example, for password reset), a delivery provider will receive the recipient address or number and the message needed to deliver it.

PostHog

Product analytics used to understand usage, diagnose problems, and improve the app.

Vercel

Hosting and delivery of the Niighty website, including request logs and standard server metadata such as IP address and user agent.

Expo

App build tooling and push notification delivery.

Apple

App Store and TestFlight distribution, Apple Maps, and push notification delivery through Apple Push Notification service.

Google

Google Maps where used (for example, on Android) and push notification delivery where applicable.

Map providers may receive technical data needed to serve maps, such as device information, IP address, and map requests. Their handling is governed by their own privacy policies. We configure these services to collect only what the Service needs.

10. Security

We design Niighty to protect personal data with encryption in transit (HTTPS/TLS), access controls and least-privilege permissions, PostgreSQL row-level security, separation between raw crowd reports and the aggregate status the app reads, rate limits and anti-abuse checks, and monitoring for misuse.

These measures reduce risk, but no system is completely secure. We cannot guarantee that unauthorized access will never occur. If we become aware of a security incident affecting personal data, we will notify users and authorities as required by applicable law.

11. Your rights and choices

Depending on where you live, you may have the right to access, correct, delete, restrict, or object to processing, request a portable copy of your data, and withdraw consent. To make a request, email privacy@niighty.app. We may need to verify your identity before acting.

Controls available with the Service:

  • Location. Grant or revoke location permission in iOS Settings. The first request is for When In Use access.
  • Notifications. Turn notifications on or off in iOS Settings or in the app.
  • Friend sharing. Use the per-friend switches in the app. Sharing is off by default.
  • Account deletion. Use the delete-account option in the app’s settings. Deletion cascades your personal data as described in Section 8. If you cannot access the app, email privacy@niighty.app and we will help verify and process your request.

Withdrawing consent does not affect the lawfulness of processing before withdrawal. We will respond within the time required by applicable law. We will not discriminate against you for exercising a privacy right where discrimination is prohibited.

California residents: see Section 6 for the CCPA/CPRA notice.

12. Changes to this policy

We may update this policy as Niighty develops and before launch. We will post the new version here and update the effective date. If changes are material, we will provide additional notice in the app, by email, or on this page before they take effect.

This is a Sprint 0 draft with no effective date. The final policy may differ substantially from this draft.

13. Contact

Questions, requests, or concerns about privacy: privacy@niighty.app. This address is a placeholder for the Sprint 0 draft and will be confirmed before launch.

For the rules that govern use of the Service, see our Terms of Service.

Back to top ↑