NightlyFinds
Write a ReviewAdd a PlacePendingCollectionsFeedFriends
Sign In

Draft for review. These policies are the working text for a soft launch. The operator details (legal entity, governing law, contact addresses, designated copyright agent) are being confirmed and the text is not yet the operative agreement.

NightlyFinds

AboutContent GuidelinesTerms of ServicePrivacy PolicyCopyright & DMCAData Sources & Attribution

Policies v1.1
Effective November 15, 2026

Questions: admin@nightlyfinds.com

Privacy Policy

Effective November 15, 2026 · version 1.1 · Operator: NightlyFinds, operated by its owner as a sole proprietorship (United States)

The short version: we collect the minimum a directory needs — an email address, a display name, and what you choose to post. We run no advertising, we place no third-party tracking cookies, we do not sell or share personal data for advertising, and we process data in connection with one purpose: making local discovery work.

1. Scope

This policy covers the NightlyFinds website and API. It does not cover venues, their websites, or links out of the Service. Questions, corrections, and deletion requests: admin@nightlyfinds.com.

2. What we collect

You give us

  • Account: email address, display name, and (if you add them) a bio and avatar. A role flag (user / admin) and, for the first sign-in, the account creation timestamp.
  • Content you create: reviews, tips, photos, questions, answers, curated lists, deal reports, ratings, votes, and reports you file. Each row stores your account id so authorship is attributable — that is a deliberate design choice, not an oversight.
  • Check-ins: a place, a timestamp, and the visibility you choose (public / friends / private). Live “here now” rows expire after two hours; the weekly crowd chart is built from aggregated hour buckets, not from a travel history.
  • Owner claims: if you claim a venue, we store the claim, its status, and the evidence you send.
  • Reports and appeals you send us, including anything you write in them.
  • Place submissions: when you add a new place, we store what you submit (name, verified street address, category, optional phone and note) with your account id as attribution. It stays hidden from search until neighbors or an admin approve it.
  • Approval votes: voting on a pending place stores your account id, the place, and — when a vote cannot count — the eligibility verdict as an anti-abuse audit trail. Votes are how the community builds the catalogue; the catalogue is what we defend.
  • Place updates: suggesting new hours, a phone number, or a moved address stores the proposal with your account id; neighbors vouching for it stores their account ids. Ineligible vouches are recorded as verdicts, not hidden — the audit trail is how a small site defends its catalogue at soft-launch scale. Address moves carry the verified coordinates we captured at proposal time.

Collected automatically

  • Session cookie (signed, HTTP-only) so we know you are signed in.
  • Search input: the text you search for and the location string you type, for the duration of the request. We do not keep a log of who searched for what.
  • Coarse geolocation only when you use “search this area” — the map bounding box, for that request.
  • Server logs: request metadata (timestamp, route, status, latency, IP address, user agent) written by our hosting provider for security, abuse prevention, and debugging. Retained about 30 days, then rotated out.
  • Browser storage: your theme choice (see §4). No fingerprinting.

From third parties

Place facts — names, addresses, coordinates, categories, phone numbers, hours — from open-data sources (Overture Places, OpenStreetMap, GeoNames). See Data Sources & Attribution. No personal data of venue staff is collected from those sources.

3. Why we use it (lawful bases)

  • Contract — to create your account, publish your content, show your check-ins, deliver sign-in.
  • Legitimate interests — security, abuse and spam prevention, rate limiting, moderation of reported content, product diagnostics, and legal compliance.
  • Consent — non-essential browser storage (theme), and marketing email if we ever send it (you opt in, you can opt out).
  • Legal obligation — responding to valid legal process, tax records, and notices under the DMCA.

4. Cookies and browser storage

NameWherePurposeLifetime
session cookiefirst-party, HttpOnly, SameSite=Lax, Secure in productionkeep you signed in; CSRF-safe form postsuntil you sign out or the cookie expires
nf-theme (localStorage)your browserremembers the theme you picked (system / light / dark / sepia)until you clear site data
nf-recent-locations (localStorage)your browserup to 5 locations you picked, offered back in the location box; never sent to usuntil you clear site data

There are no advertising cookies, no third-party pixels, no social-media trackers, and no session-recording tools. We honour Global Privacy Control (“do not sell/share”) signals; there is nothing to opt out of, because we do not sell or share personal data for advertising. Browsers that signal “Do Not Track” are treated as if they had asked us not to set non-essential storage.

5. Public by design — read this if you post

NightlyFinds is a community directory. Your display name, your reviews, tips, photos, answers, curated lists, deal reports and public check-ins are visible to the public and indexed by search engines, and are published under CC BY 4.0 (see Terms §5). Your email address is never shown publicly. Before you post, assume the whole world can read it — including the venue. Don’t include staff names, surnames of patrons, order tickets, addresses of private homes, or health information about yourself.

6. Who we share data with

  • Vercel Inc. — runs the web app and API (hosting, logs, analytics for operators). Processes request metadata and function logs.
  • Supabase, Inc. — managed Postgres that stores accounts, content, and check-ins, inside our project with a least-privilege database role.
  • Search hosting (Meilisearch, self-hosted) — the search index, which contains public place data. It contains no account emails and no private check-ins.
  • OpenStreetMap / tile provider — map rendering, no personal data.
  • Authorities, professional advisers, insurers, and acquirers — only where legally required, to defend or enforce our rights, or in a restructuring, always under confidentiality and only the data that is needed.

We do not sell, rent, trade, or share personal data for advertising, and we do not let advertisers target you.

7. Retention

  • Account, content, and moderation records: for the life of the account.
  • Live “here now” check-in rows: 2 hours. Aggregated hourly crowd buckets: kept (they are counts, not personal data about you once aggregated).
  • Server logs: ~30 days.
  • DMCA notices and counter-notices: kept as legal records, including the complainant’s contact details.
  • After account deletion: email address and profile fields are deleted; your content stays with an anonymised byline (see Terms §5, “Deletion and anonymisation”).

8. Your rights

You can ask us to access, correct, export, restrict, object to, or delete your personal data; to withdraw consent; to be informed about who we share it with; and to lodge a complaint with your data-protection authority. We will verify your request (usually by replying to the address on the account) and answer within 30 days, extendable by two months for complex requests, and free of charge unless requests are manifestly excessive.

Self-service today: your account page shows your content and lets you delete it. For a full export (JSON of everything tied to your account) or a deletion, email admin@nightlyfinds.com. Under CCPA/CPRA we disclose the categories in §2, we disclosed them at collection, we do not “sell” or “share” personal data, and we do not use sensitive personal information beyond §2.

9. Where data lives and transfers

Our database runs in us-east-2 (Ohio, United States) and our hosting is distributed from United States regions. If you are outside the United States, we transfer your data to the United States on the basis of Standard Contractual Clauses (with the UK Addendum where relevant) and the safeguards in §10.

10. Security

TLS in transit; secrets kept out of the repository and out of logs; the application connects with a least-privilege database role (no DDL); admin surfaces are role-gated; rate limits and review-first moderation slow abuse; dependency licences and supply-chain drift are checked on every commit. No system is perfect: if you believe we have compromised your data, email admin@nightlyfinds.com.

11. Children

The Service is not for children under 13 (16 in the EEA and UK). We do not knowingly collect children’s data; if we learn we have, we delete it. If you are a parent who believes your child sent us data, contact us.

12. Changes

Material changes are announced at least 15 days ahead, in-app and at admin@nightlyfinds.com, and this page carries a new effective date. The previous version is available on request.

13. Contact

NightlyFinds, operated by its owner as a sole proprietorship (United States). Privacy contact: admin@nightlyfinds.com. In the EU/UK you may also contact your local supervisory authority.

AboutContent GuidelinesTermsPrivacyCopyright & DMCAData sourcesContact

© 2026 NightlyFinds. All rights reserved.

Map: © OpenStreetMap contributors · © OpenMapTiles (hosted by OpenFreeMap) · Icons: OpenMoji (CC-BY 4.0). City gazetteer: GeoNames (CC-BY 4.0). Place data from open datasets, carried with attribution; reviews and photos are copyright their authors and reproduced here by licence to NightlyFinds. Content marked DEMO is synthetic sample data, not a real business.

NightlyFinds, operated by its owner as a sole proprietorship (United States). Independent — not affiliated with, endorsed by, or sponsored by any business listed.