Privacy Policy
Effective 20 July 2026 · Last updated 20 July 2026
The short version
KNOW collects what it needs to plan your night and nothing it doesn't. Your precise location is an input, never a display — no screen in the app shows it to anyone, including you. Your taste preferences are hidden from other users by default. Being suggested to strangers is off by default — connecting with new people is a switch you turn on, never something that happens to you. We do not sell your data and we do not share it with anyone for advertising. You can delete your account and your data from inside the app at any time.
The rest of this page is the detail behind those claims.
Who we are
KNOW ("KNOW", "we", "us") operates the KNOW mobile application. This policy explains what personal information the app collects, why we collect it, who we share it with, and the choices you have. If anything here is unclear, email privacy@knowapp.app and we'll answer in plain language.
Who can use KNOW
KNOW is for adults 18 and over. It's a nightlife app centered on bars and venues, and we gate on age at sign-up. We do not knowingly collect information from anyone under 18. If you believe someone under 18 has created an account, email privacy@knowapp.app and we'll remove it.
What we collect and why
Account and contact
| Data | Why we collect it |
|---|---|
| Email address or phone number | To sign you in. We send a one-time code; we don't store a password. |
| First name | Shown to friends, and used by the planner to address you. |
| Date of birth | To enforce the 18+ age gate, and to show your age on your profile. Someone deciding whether to meet a stranger reasonably wants to know it, so KNOW shows the number rather than hiding it in a band. The date itself is never displayed — not to you, not to anyone else. We show the age derived from your date of birth, never the birthday. A broader band (e.g. "26–35") is all that reaches the AI planner. |
| Gender | Optional, including "prefer not to say." Used for personalization and for an aggregate crowd-composition feature. It is never shown individually — only ever as an aggregate across enough people that no one person is identifiable. |
Location
Our location promise
Your precise coordinates are an input to the planner and nothing else. They are used to compute distance and walkability, and then they stop. There is no screen, no profile, no map pin, and no export that renders them — not to other users, not to your friends, not back to you. The finest-grained location KNOW ever displays is a neighborhood name.
| Data | Why we collect it | Who can see it |
|---|---|---|
| Home neighborhood (coarse) | So the planner starts your night somewhere sensible. | You, and others if you make it visible. |
| Home coordinates (precise) | Distance and walkability math inside the planner. | No one. Never displayed. |
| Travel coordinates (temporary) | If you're out of town, so plans center where you actually are. Doesn't overwrite your home, and expires after 12 hours — after that the planner falls back to your home neighborhood. | No one. Never displayed. |
| Check-in coordinates | To verify you're really at a venue, which feeds honest busyness data. | No one. Not readable by any app client — even yours. |
| Live presence | To show friends you're out, if you turn it on. | Only friends you've accepted, and only if you both enabled location sharing. Off by default. |
Your content
- Profile photo — shown on your profile and, if you share presence, as your marker on the map to friends.
- Photos and videos you post, and captions on check-ins — shown in the social feed.
- Bio and profile answers (your go-to order, a nightlife quirk, a guilty pleasure) — shown per your visibility settings.
- Messages you send the concierge — sent to Anthropic's Claude API to generate your plan. We don't store your messages verbatim; we distill them into a short memory summary that helps the agent plan better next time.
Taste and personalization
What you drink, the music and rooms you like, the occasions you go out for, your pace, and your price range. This is the fuel that makes the planner personal. These fields are hidden from other users by default — the agent reads them so it can plan; other people don't. You control visibility field by field in your profile settings.
| Data | Why we collect it | Who can see it |
|---|---|---|
| Sports teams you follow | So a home game becomes a plan — "your team's on at this bar tonight." Matched against a verified events list; we never guess that a venue shows a given game. | You. Used to personalize plans and nudges. |
| Who you usually go out with (crew size) | To shape how the planner talks to you — an easy solo one, or rally the whole crew. It changes the wording, not the venues. | You only. Never shown to others. |
| What you're after (intent) | Whether tonight is close friends, meeting new people, discovering a spot, or just a good drink. Shapes the kind of night the agent builds. | Hidden from other users by default. |
Background and connections
KNOW lets you add a few things about your world — your school, your industry, and your hometown. These are optional, and each has its own show/hide toggle. Because they're the natural starting points for a real connection, they show on your profile by default — but you can hide any of them in Settings → Edit Profile at any time.
Meeting new people is opt-in
KNOW can suggest people you might want to know — based on a shared school, industry, hometown, or friends in common. This is off until you turn it on. Appearing in other people's suggestions is a separate switch (Settings → "Discoverable by"), off by default, and distinct from whether a field shows on your profile. Hiding a field, pausing discovery, and blocking a specific person are three independent controls — turning one off never silently turns another on.
When you're discoverable, we use these background fields plus your mutual friends to rank who to suggest. We never use your precise location to match you to strangers, and we never show your exact location to a suggested connection — the finest location anyone ever sees is a neighborhood name.
Connecting on KNOW is mutual: one person asks, the other accepts, and either can remove the connection later. Accepting a connection is also what makes presence sharing possible — but it doesn't switch it on. Presence stays opt-in and off by default, for both of you, even after you connect.
Your connection count is a number, never a list
How many connections you have can be shown on your profile to other people using KNOW. Who they are is not: we do not publish your connection list, and no one can page through the people you know. The count is the same number regardless of who is looking, so it can't be used to work out whether you're connected to any particular person. If you and someone else have blocked each other, they don't see your count at all — not a zero, nothing.
Usage and diagnostics
- Onboarding events — which steps you viewed, finished, or dropped, so we can fix where the app confuses people.
- Agent usage — model, tokens, and cost per request, for monitoring spend, rate limiting, and detecting abuse.
- Feedback signals — whether you went, stayed, skipped, or swapped a stop. This is how the agent learns.
- Derived patterns — which nights you typically go out, and taste similarity scores used for recommendations. Computed by us from the above; not collected separately.
- Problem reports you submit, and crash diagnostics, so we can fix bugs.
- Push token, if you enable notifications, so we can send you a plan.
Who we share data with
We use a small number of processors, each for one job:
| Who | What they get | Why |
|---|---|---|
| Anthropic (Claude API) | Your concierge messages, and a personalization brief containing: your first name, your school, your age band (e.g. "26–35"), your neighborhood name, your taste fields (interests, venue types, what you're after tonight, pace, price band), the venues you've saved, and the short memory summary the planner keeps about you. Never your raw date of birth, never your coordinates, and never your gender — the first two are reduced to a band and a neighborhood name on our servers before anything is sent, and gender never reaches the planner at all. | To generate and refine your plan. Per Anthropic's API terms, this data is not used to train their models. |
| Supabase | Hosts our database, authentication, and file storage. | It's our backend infrastructure. |
| Apple (via Expo push) | Your push token and the notification text. | To deliver notifications. |
| Resend | Your email address. | To send your sign-in code. |
| Sentry | Crash and error diagnostics. | To find and fix crashes. We scrub request bodies before they're sent. |
| Busyness data providers | Venue names and venue coordinates only. No user data. | To show how busy a venue typically is before we have enough of our own data. |
We may also disclose information if legally required to (a valid subpoena, court order, or equivalent), or to protect the safety of our users. If that ever happens we'll tell you unless we're legally prohibited from doing so.
What we never do
- We never sell your personal information.
- We never share your data with third parties for advertising.
- We never display your exact location — to anyone, in any screen.
- We never display your date of birth — your profile shows your age, never your birthday.
- We never show individual crowd or gender data for a venue — only aggregates, and only once enough people are present that no individual is identifiable.
- We never store an exact home address. Only a coarse neighborhood is stored as text.
Your choices and rights
- Delete your account. In the app: Settings → Account → Delete Account. This removes your profile, content, check-ins, presence, and plans. Some records are anonymized rather than deleted where we need them for aggregate integrity or legal reasons — they stop being linked to you.
- Control visibility. Every profile field has its own show/hide toggle. Taste fields are hidden by default; background fields (school, industry, hometown) are shown by default and can be hidden individually.
- Control discovery. Being suggested to other people as a possible connection is off by default. Turn it on — or back off — in your profile settings.
- Turn off location sharing. Presence sharing is opt-in and off by default. You can revoke location permission entirely in iOS Settings — the app still works, the planner just gets less precise.
- Turn off notifications, in the app or in iOS Settings.
- Block and report other users. Blocking hides you from them and them from you.
- Access your data. Email privacy@knowapp.app and we'll send you a copy.
Depending on where you live (for example, California, or the EU/UK), you may have additional rights — to access, correct, delete, port your data, or to object to certain processing. We honor these requests regardless of where you live. Email privacy@knowapp.app.
How long we keep things
We keep your account data while your account exists. When you delete your account, we remove your personal data promptly. Operational logs and cost/usage records are kept for a limited period for security, billing, and abuse detection, and are not used to profile you.
Security
Data is encrypted in transit. Access to the database is governed by row-level security rules that are enforced by the database itself, not just the app — so a client cannot read another user's private data even if it asks. Sensitive fields (like check-in coordinates and raw crowd demographics) are locked so that no app client can read them at all. No system is perfectly secure, but we take this seriously and audit it.
Children
KNOW is 18+. We do not knowingly collect data from anyone under 18, and we delete such accounts when we learn of them.
Changes to this policy
If we change this policy materially, we'll update the date at the top and notify you in the app before the change takes effect. We won't quietly broaden what we collect.
Contact
Privacy questions, data requests, or anything about this policy:
privacy@knowapp.app.
Everything else: knowapp.app/support.