← Back to function.cx

Privacy Policy

1. What we collect

• Account: your email address and password (the password is stored only as a hash by our authentication provider, never in readable form), plus the display name and initials you choose.
• Your date of birth. Asked once, when you create your account. We use it for two things and nothing else: to check you meet our minimum age, and to check whether you meet the age limit on an event that has one. Nobody else can see it — not other members, not hosts, not the host of an event you are going to. It is not shown on your profile and there is no way to look it up. Hosts see only whether a guest could get a ticket, never a date or an age. Because it is what an age limit is enforced against, it is set once and cannot be edited afterwards; email hello@function.cx if it is wrong.
• Profile, if you add it: a profile photo, a short bio, your city and state, and Instagram or TikTok usernames. All of this is optional.
• Event activity: events you host, RSVPs and tickets you hold, and whether a host scanned you in at the door.
• Things you post: reviews and ratings you write, photos or clips you upload about an event, comments you leave on a post, and any captions.
• Activity on the platform: who you follow, events you save, posts you like, and reports you file.
• Camera and microphone, only while you use them. Posting a photo or clip, and scanning tickets at the door as a host, asks your browser for camera access; recording a clip with sound also asks for the microphone. Nothing is captured until you allow it, nothing runs in the background, and nothing reaches us unless you actually post it.
• Abuse prevention: a short-lived record of actions you take (for example "created an event at 9:04pm") so we can rate-limit spam. It holds no content.
• A one-way fingerprint of your connection. To stop one person taking a whole event's tickets across several accounts, we count recent actions per internet connection. Your IP address is combined with a secret key held only by our database, and only the resulting hash is stored. We never store the address itself, and the hash is not readable as an address by anyone who does not hold that key. These records are cleared automatically within about a day.
• Payment records: for a paid ticket, the amounts charged, Function's fee, and Stripe's identifiers for the payment. Not the card.

2. What we don't collect

• No phone number. We never ask for one.
• No card numbers. Card details are entered on Stripe's own checkout page. They never reach our servers, and we could not see them if we wanted to. What we store is what Stripe gives us back: identifiers for the payment and the amounts.
• No bank details. If you host paid events, your bank and identity details go to Stripe during their onboarding. Function never receives them.
• No analytics or advertising. Function runs no analytics, no advertising, and no tracking scripts, and sets no cookies at all. We do not build a browsing profile of you and we do not track you across other websites. One third-party script does load: Cloudflare Turnstile, the challenge on the sign-up form that blocks automated account creation. It is bot protection, not analytics, and it is described in section 8. Our hosting and database providers keep standard server logs, which include IP addresses, for security and reliability.
• No location tracking, but we do ask once. The app can ask your browser for your location to pick the nearest city, and asks before it does. The coordinates are compared against a built-in list of cities on your own device and are never sent to us or to anyone else — all that is saved is the name of the city it landed on, the same as if you had picked it from the menu. Say no and nothing happens; the city stays wherever you set it. We never track your location in the background or build any history of where you have been.

What your browser does store. Signing in stores a session token in your browser so you stay signed in, and the app keeps a few preferences there too. These are necessary for Function to work, are not used to track you, and are cleared when you sign out or clear your browser data.

3. Children

4. How we use it

• To run your account and show you events near the city you chose
• To issue and check tickets at the door
• To show hosts who is coming to their event
• To enforce rules that depend on attendance — for example, only people scanned in at an event can review it or post photos from it
• To check age limits — whether you meet our minimum age, and whether you meet the limit on an event that sets one
• To keep private addresses private, revealing them only to confirmed guests close to the event
• To respond to reports and remove content that breaks our rules
• To detect, investigate and prevent fraud, abuse and security incidents
• To send you a small number of service emails: a welcome message, password resets, and confirmations
• To comply with the law and to establish or defend legal claims

We do not use your information to make automated decisions that produce legal or similarly significant effects about you.

5. Who can see what

Public: your display name, profile photo, bio, city and social usernames; the events you host; and reviews you write. Visible to signed-in members: the photos and clips you post, and, if you RSVP to a public event, your name and photo on that event's guest list.

Private: your email address, your date of birth, who you follow, the events you save, and any reports you file. Guest lists for events with a private address are hidden entirely. Hosts can see who holds a ticket to their own event, and can see the list of people following them.

A host who sees your name on their guest list holds it in their own right. Our Terms require hosts to use that information only to run the event — not to market to you, export you, or pass you to anyone else — but a host is a separate person, not part of Function, and we cannot reach into what someone else has written down. If a host misuses your details, tell us at hello@function.cx and we will act on it.

Photos are served from public web addresses that are long and unguessable. Anyone given such a link directly can view that image, so treat a shared image link as public.

6. How long we keep it

• Event photos and clips are kept until you delete them. A post leaves the For You feed 24 hours after you make it, but it stays on your profile and on the page of the event it was taken at, visible to anyone who is signed in, for as long as it exists. The file itself is kept for the same period. Deleting a post removes it, and its file, everywhere at once. If the host deletes the event, your post stays on your profile without the event attached. If a post was taken at a link-only event, it does not name that event except to the host and to people who currently hold a ticket to it or have saved it. If Function removes an event, posts made at it stop being shown to other people; you can still see and delete your own.
• Your account data is kept while your account exists. Deleting your account removes your profile, email and password, your events, your tickets, your reviews and comments, your follows, your saved events and your posts, and deletes the photos and clips you uploaded.
• A record that you accepted our terms survives deletion. We keep which version of the Terms you accepted and when. It is the only proof that the agreement existed, so it outlives the account it belonged to.
• Abuse-prevention records — including the hashed connection fingerprint — are cleared automatically after a short period.
• Payment records outlive the account, deliberately. When you delete your account, the record of a payment is kept but is detached from you: the link to your profile is removed, leaving the amounts and Stripe's identifiers with no name attached. This is so disputes, chargebacks and accounting still work; it is not a copy of your identity. It does not preserve a route to a refund — once the payment record no longer names you, we can no longer show that you were the person who paid, and a self-serve refund on that ticket is refused. If you are holding a refundable ticket, refund it before you delete your account. Stripe keeps its own records under its own policy and legal obligations.
• Moderation and legal records. We may keep a limited record of content we removed, of reports and copyright notices we received, and of the accounts involved — held separately from your account and after it is gone — where we need it to enforce our terms, to run our repeat-infringer policy, to investigate fraud or safety, to comply with a legal or preservation obligation, or to defend a claim.
• Child safety. Where the law requires us to report and preserve material — in particular apparent child sexual abuse material under 18 U.S.C. § 2258A — that obligation overrides any deletion right in this policy.

7. What we don't do

Function does not sell your personal data, does not share it for advertising or cross-context behavioural advertising, and has not done so in the past 12 months.

8. Service providers

We use a small number of providers to run the platform, and share only what each needs:

• Supabase — database, sign-in, and file storage
• Netlify — website hosting
• Private Email (Namecheap) — sending our emails
• Cloudflare — Turnstile, the challenge shown on the sign-up form to block automated account creation. To score the challenge, Cloudflare receives your IP address and characteristics of your browser, under its own privacy policy. The challenge itself appears only on the sign-up form, but the script that powers it loads with the rest of the app, so Cloudflare can see that a browser requested it on any page.
• Stripe — payments, host onboarding and payouts. Stripe receives the buyer's card details and the host's identity and bank details directly, and handles them under its own privacy policy.

We may also disclose information where we believe in good faith that the law requires it, that it is necessary to enforce our terms, or that it is necessary to protect someone's safety. If Function is involved in a merger, acquisition or sale of assets, information may transfer as part of that, and we will say so here beforehand.

9. Security

Passwords are stored only as hashes, never in readable form. Card and bank details never reach us at all. Traffic to Function is encrypted in transit, and access rules in the database restrict every record to the people entitled to see it. IP addresses used for rate limiting are stored only as one-way hashes.

No system is perfectly secure. We cannot guarantee that information will never be accessed by someone who should not have it. If a breach affects your personal information, we will notify you and any regulator as the law requires.

10. Your choices and your rights

You can delete your account yourself, at any time, from your profile in the app — you do not need to email anyone and you do not need our permission. It takes effect immediately and cannot be undone. You can also edit or remove your profile photo, bio and social usernames at any time, delete your own posts and reviews, and unfollow or unsave anything.

Depending on where you live, you may have the right to:

• Know what personal information we hold about you and how we use it
• Get a copy of it
• Correct it if it is wrong
• Delete it
• Opt out of sale or sharing — we do neither, so there is nothing to opt out of
• Not be discriminated against for exercising any of these rights. We will not refuse you service, charge you differently, or give you a worse experience for it.

Deletion is self-serve in the app. For anything else, email hello@function.cx from the address on your account. If we cannot tell that a request is really yours, we will ask you to confirm it from that address before we act — that check exists to stop someone else deleting or downloading your data. An authorised agent may act for you with written permission. We aim to respond within 45 days.

Do Not Track and Global Privacy Control. Function does no cross-site tracking and serves no advertising, so there is nothing for these signals to switch off. We honour them by not doing the thing in the first place.

11. If you are outside the United States

Function is operated from the United States and is intended for people in the United States. If you use it from another country, your information is transferred to, stored in and processed in the United States, where privacy law may differ from your own. By using Function you understand that.

12. Changes to this policy

We may update this policy. When a change is material we will give notice — by email to the address on your account, in the app, or both — before it takes effect. The "last updated" date at the top always reflects the current version.

13. Contact

The controller of your personal information is We make the function LLC, a North Carolina limited liability company, at 1183 University Drive, Ste 105 #2292, Burlington, NC 27215, United States.

Questions about this policy, or a request about your data: hello@function.cx. Written requests can be sent to the postal address above.