Chartd Privacy Policy & User Agreement

Privacy Policy

Effective date: October 9, 2026

At Chartd, we take your privacy seriously and collect only what we need to run the app, the website, and our business services. This policy covers the Chartd mobile app, chartdapp.com, and the Chartd integration in ChatGPT and compatible AI services.

In the Chartd app

While location is on, the app records your phone’s location for the map’s busy-area feature. It is stored with your account, but other people see it only as unattributed busy areas. You can turn location off at any time in your device settings. Weekend picks by push, described below, also keep an approximate location for your phone, linked to your account, while they are on.
If you create an account, we store the information you provide — such as your username, email, and the events, photos, and other content you post — in order to operate your account and show your content to other users.
When you create an account we send one welcome email to your sign-in address. It contains no advertising, and we do not send you marketing email unless you ask for it.
Advertising and analytics in the app: Chartd shows you no ads. The iPhone app does include software from Meta and from Google (Firebase) that reports app installs, app activity, crashes and performance, which is how we measure our own advertising, see how people found Chartd, and fix what breaks. On iPhone that software only identifies you across other companies’ apps and websites if you allow it at the “Ask App not to Track” prompt, and you can change your answer at any time in Settings › Privacy & Security › Tracking. The Android app contains no advertising or analytics software at all; the only Google (Firebase) software in it is Firebase Cloud Messaging, which delivers its push notifications.
Other people on Chartd: if you go to someone’s event, they see things about you. What, and which parts you can switch off, is set out in What event hosts can see below.
Find Contacts: if you use Find Contacts, the app sends the phone numbers from the contacts you let it access to Chartd, to show you which of them belong to Chartd accounts. They are used for that lookup and are not added to your account or anyone else’s; we keep only a count of how many you looked up that day, to enforce a daily limit. If you add your own phone number to your profile, people who have that number in their contacts can find your profile this way. You can stop that by removing your number, or, in versions of the app that offer it, by turning off “Let people who have my number find me” in Settings › Privacy. Accounts we can identify as under 18 can’t be found this way.
Push notifications on iPhone and Android: when you are signed in to the Chartd app on a phone and allow notifications from Chartd, we store, linked to that account: the push token Apple (on iPhone) or Google (on Android) gives that phone, its time zone, the app version, which kinds of notification that version can show, which sign-in on that phone the record belongs to, and when the app last checked in with us. If you turn notifications off for Chartd, the app deletes that record the next time it opens. We delete a phone’s record when you sign out on it, and the records of all your phones when you use “Sign out everywhere” in the iPhone or Android app, when you delete your account, when Apple or Google tells us the token no longer works, and after 60 days in which the app has not checked in. If the app could not reach us when you signed out, that phone’s record is deleted the next time the app opens with a connection, or at the latest within 60 days; and if that was “Sign out everywhere”, your other phones stay signed in, and keep receiving notifications, until you sign them out too. Signing out on our website, when it can reach us, also signs your phones out without the app being able to tell us; their records are then deleted within 60 days, and until then those phones can still receive weekend picks by push if they were on, but no other push notifications from us. If another Chartd account signs in on that phone, the record moves to that account and keeps none of your settings.
Weekend picks by push: this is off until you turn it on. The app may ask you once, and the switch is in Settings › Notifications. While it is on, we also store that phone’s approximate location, rounded to about 11 km, so that on Friday afternoon we can tell you how many events are on near you that weekend; turning it off clears that location. Whenever your choice changes, we record it, where in the app you made it, and when. The notification shows a count of events and may name one public event, its start time and its host’s username. It also carries your account’s identifier, which is not shown, so that the Android app can drop a notification meant for a different account signed in on the same phone; the iPhone app cannot stop iOS showing one, but ignores it while the app is open and when you tap it. Notifications are delivered by Apple (on iPhone) and Google Firebase Cloud Messaging (on Android), through Amazon Web Services. We keep a record of each weekend notification we send — the week and whether it was sent, never the push token or the text — for as long as your account exists. Accounts we can identify as under 18 cannot turn this on.
Message, invite and event notifications: in versions of the app that offer them, while a phone allows notifications from Chartd, we notify the account that is active on it when someone sends that account a message, including co-host, vendor and door-team requests and the notices about them that appear in your messages; when someone invites it to a private event or approves its request to join one; and when an event it RSVP’d to in the app or holds a ticket for is cancelled, or its date, time or place changes. Not every one is sent: we limit how many we send, most tightly for messages from people you have not replied to, and we never send one from someone you have blocked or who has blocked you. A message notification shows the sender’s username and the message itself; a photo shows as “Sent a photo”. An invite shows who invited you, or who approved your request, and the event’s name, and an event notification shows the event’s name and what changed (never a private event’s address). These need nothing beyond your phone’s permission, and each kind can be turned off in Settings › Notifications. We send them only to a phone whose sign-in is still active with us. If you sign out on a phone while it cannot reach us, that phone can still receive them until the app next opens with a connection and tells us to stop sending to it, or for at most 60 days. If you switch accounts on an iPhone while it cannot reach us, notifications for the account you left can still arrive until the app next opens with a connection. Your phone’s own settings decide whether their text shows on the lock screen.
Notifications for hosts: if you host an event, we notify you of each ticket to it that someone buys from Chartd, showing the event, the ticket type and the price but never who bought it, and of new RSVPs (free tickets included) and likes as a count, at most once an hour per event, never naming anyone; a count that falls due between 9 pm and 9 am your phone’s local time waits until 9 am. They reach your phones under the same rules as the notifications above, and in versions of the app that offer it you can turn them off in Settings › Notifications.
How notifications are sent and kept: notifications are delivered by Apple (on iPhone) and Google Firebase Cloud Messaging (on Android), through Amazon Web Services, so their text passes through those companies on its way to your phone. Each one also carries, unseen, your account’s identifier and our identifier for the conversation or event it is about (for a host’s message, also our identifier for that message; for a ticket sale, our identifier for that notification), which pass through those companies too. To send them we keep a short work queue that points at the message, event or ticket, may record whose action caused it, and may copy who was invited or on its guest list, who had saved it to their calendar, its name, who hosted it, and its previous time and place; it never holds the text of a message and is deleted within a day of being processed. We keep a record of each message, invite, event and host notification — which kind, what it was about and whose action caused it, when, and whether it was sent, never the push token or the text — for 30 days, and for a cancelled event that record holds the event’s name. To count RSVPs and likes for hosts we keep which account, or which ticket for a sign-up without an account, RSVP’d to or liked which event for 90 days. Your choices for message, invite, event and host notifications are kept for as long as your account exists.

On chartdapp.com

Contact and bug-report forms open a message in your own email app; we receive only what you choose to send us.
Newsletter signup: if you subscribe for updates, we store your email address, together with the submitting IP address and browser information, which we keep to prevent abuse of the signup form. We use your email only to send you Chartd news. Email us at any time to unsubscribe.
Business plan agreements: when a business signs a service agreement, we store the business name, signer name, typed signature, email, selected plan, the sales representative named on the form (if any), a snapshot of the signed contract, and the identifier of the Chartd account that signed it, together with the submitting IP address and browser information. These records document a legal agreement and are retained for as long as the law and the agreement require.
Importing events from a spreadsheet: if your business has a Basic, Essentials or Pro plan, you can add many events at once, on this website or in versions of the app that offer it, by uploading a CSV or Excel file or by giving us the link to a Google Sheet. Our server, which Amazon Web Services hosts, reads the cells of the file you upload. For a Google Sheet, our server fetches it from Google each time you ask for a preview and does not keep reading it afterwards; this works only when the sheet is shared so that anyone with the link can view it, or is published to the web, and we send Google nothing that identifies you. We do not keep the file itself or its name. To show you a preview, we keep what we read from each row, together with the map location we found for it, and the settings listed below for an upload record, until you publish or for at most 24 hours. We send each row’s address, and its country when the file gives one, to the location service of Amazon Web Services to find its place on the map and its time zone; nothing else from the file is sent to that service. The events you publish are public, under your name, like any event you post. For 30 days we keep a record of each upload you publish: when it was made; what kind of file it was (CSV, Excel or Google Sheet); how many rows it had and how many of them could be published; which events it published, and which rows were skipped and why; if its events were later removed, when, and how many were removed or kept; the time zone you chose for it, if any, and the date order its dates were read in; your device’s or browser’s time zone, and the country of your device’s region setting or your browser’s language; whether it came from the app or this website; and, if we remove an upload for breaking our rules, our reason. For 7 days after publishing you can remove all of that upload’s events at once, except any that already have tickets, and people who RSVP’d to one of them in the app may be notified that it was cancelled. To enforce daily limits we keep counts of your uploads, address lookups and published events for at most 2 days. We do not send your spreadsheet, or anything we read from it, to an AI company to import it. Once you publish your events, they can reach AI companies like any other public event, through the AI features and the Chartd integration in ChatGPT and compatible AI services described below.
Posting events on this website: once you have a Chartd profile, you can create, edit and delete your events on this website as well as in the app, and we store and show them as we do an event you post in the app. Public events are visible to everyone, and with “I’m the host” turned off your username is not shown with it. When you add a cover photo, your browser makes a new copy of the picture, resized when it is large, and only that copy is uploaded, so the location and camera details a photo file can carry are not sent to us. To place an event on the map, our server, which Amazon Web Services hosts, sends the address you type to the location service of Amazon Web Services, which returns the matching address, its map location and its time zone; nothing else is sent to that service. We read the times you enter in the time zone of the event’s location, or, when we cannot tell, in your browser’s time zone or one you choose, and for public events, we save that time zone with the event. To enforce a daily limit on these lookups we keep a count of them for your account for at most 2 days.
Private events and invitations on this website: you can create a private event, choose its guests and how people can join, upload its cover, and approve or deny requests to join or remove a guest. A cover uploaded here is stored privately and shown to people who can access the event, including the host, an accepted co-host and invited guests. You can allow a limited link preview that shows the event name, host and dates to anyone with the link; a cover that was already public may also appear. The preview never shows the address, guest list or comments. Co-host and vendor requests you send from this website are direct messages sent from your Chartd account, as in the app.
Live events on this website: when you turn on “Event is live” and allow your browser to share a precise location, we save that location as the public event’s map location. It is visible to everyone as the place to go.
Host tools on this website: you can download attendee and audience lists or the event dashboard’s CSV, send host messages, and manage tickets and guests on this website as well as in the app. The host or a Chartd administrator can mark people present or absent on a public event’s guest list. For a private event, the host and an accepted co-host can see which guests hold a free ticket, and the host can admit those ticket holders from the list; that admission cannot be undone. A door-helper request is stored as a direct message from your Chartd account. You can record or void a cash sale at the door; we keep the event, ticket tier, amount, optional walk-in name, who recorded it and when, and whether it was voided. These use the ticket, attendance, message and cash records described under What event hosts can see. Downloaded files are made in your browser and saved on your device; Chartd does not automatically upload them to another service. Hosts may choose to upload them to the private tools and service providers permitted by the host terms below.
Connecting your events page: if your business has a Basic, Essentials or Pro plan, you can connect the public web page where it lists its events, on this website or in the app. We store the link, its domain, when you connected it, when we last read the page and how that went (including any error message), and whether you paused or disconnected it. Once a night our importer reads the page and adds the events it lists to Chartd under your name; they are public like any event you post, and they change or come down when your page changes them. To place them on the map, our importer sends each listed address to Mapbox, and, as described in Artificial intelligence below, it may send the text of the page to OpenRouter when it needs help reading the listings. Pausing stops the nightly reading. Disconnecting stops it too and takes the page’s events off the map, except any that already have tickets, and we keep the record of the connection so that connecting the same page again brings its events back. We delete that record when you delete your account.
Ticket purchases are processed by Stripe. We never see or store your card details; we receive the purchase details (event, ticket tier, and the email you used at checkout) so we can deliver your ticket.
Location on the map page: when you open the live map, your browser asks whether to share your location. If you allow it, your approximate coordinates are used to search for events near you and are sent to our events database as part of that search; we do not store them or link them to you. If you decline or ignore the prompt, the map opens on a default city and everything else works the same. You can change or revoke this at any time in your browser’s site settings.
Website analytics: we use Cloudflare Web Analytics, which measures page loads and performance for this site. It is privacy-focused: it does not use cookies, does not fingerprint visitors, and does not build a profile of you across sites. The map page also loads Mapbox, which receives usage telemetry as part of serving map tiles. This website runs no advertising trackers.

What event hosts can see

When you RSVP to an event, save it to your calendar, claim a free ticket or buy a ticket, the person hosting that event is shown some things about you. This section says exactly what, and which parts you can switch off. It is limited to that host’s own events: a host is never shown anything about events of somebody else’s that you went to.

1. That you are coming to their event. The host, any co-host who has accepted, and Chartd’s own administrators can see your Chartd name against their event, whether you RSVP’d, claimed a free ticket or bought a ticket, which ticket tier you hold, whether you were checked in at the door, whether you did not turn up, and whether the ticket was refunded. This is what the host already knows from running the door, and there is no setting for it. For a private event, the host and an accepted co-host can also see which guests have claimed a free ticket.
2. Grouped statistics about their audience — this part is not optional. If you bought a ticket to, or saved, one of a host’s events in the last 365 days, you are counted in grouped counts they can see about their audience: age range, city, the interests on your profile, and how often people come back. These are counts of groups. They never carry your name, and no group of fewer than three people is ever shown — anything smaller is folded into a single “other” total. There is no switch for this and we are not going to pretend there is one. It is also worth knowing that at a small event a group of three does not hide much.
3. Lists of people grouped by how they have engaged with their events. A host can see lists such as people who have come to three or more of their events, people who have not come in six months, people who checked in but never paid, and people who came to their last event for the first time. Those lists carry the name on your Chartd profile and how many of that host’s events you have appeared at — and no age, no city, no interests, no email address and no phone number. They are only shown for groups of three people or more.
4. A host can email you only if you turn that on. The switch is off unless you turn it on, and we have never turned it on for anybody. When it is on, a host whose event you bought a ticket to or saved in the last year can send you a message about their events: they write it and Chartd sends it, so they never see your email address. Every message carries a one-tap link to stop that one host and another to stop all hosts, and neither needs you to sign in. Nobody receives more than one of these a day, from anybody. You are never sent one by someone you have blocked. If you switch it off, a message a host has already queued is not sent to you.
Host messages by push. A Pro host’s message can also reach you as a notification, but only if you turn on Host Broadcasts by Push in Settings › Notifications; it is off until you do, and you can turn it off there at any time. The notification shows the host’s username and the message’s subject. The rules for email apply to it too: only hosts whose event you bought a ticket to or saved in the last year, never from someone you blocked, never from a host you stopped with the link in one of their emails that stops emails from that host (the link that stops emails from all Chartd hosts does not turn this off; the switch in Settings › Notifications does), and at most one such notification a day from anybody. Whenever your choice changes, we record it, where in the app you made it, and when, and keep that for as long as your account exists.
5. Files a host downloads. A host can download a file of the people who came to one of their events, or a file of one of the lists in point 3. Those files carry your Chartd name and the same attendance facts — and no age, no city, no interests, no phone number, no email address and no ticket number. We record every attendee-list and audience-list download: which host, which event or list, when, and how many rows — never who was in it. A file a host has downloaded has left Chartd. We cannot recall it, and if you ask us to delete your data we cannot delete their copy. Before their first download a host has to accept a specific set of obligations about it, which are set out in If you are an event host in the User Agreement below, and we record that they did.
The event dashboard’s CSV: a host can also save a file of their own events’ details and activity totals, including the RSVP usernames on each event’s guest list. This file is made from the dashboard data already loaded in the browser; it does not make an audited attendee-list or audience-list export request. It can include an under-18 attendee’s RSVP username. Chartd does not record each download of this dashboard file. The host must accept the same obligations before downloading it, and is responsible for the copy they save.
Hosts’ own recordkeeping tools: hosts may upload the information Chartd makes available to them to a private CRM, Google Sheets, accounting software or service providers acting only on their behalf for their own event operations, customer records, financial reporting, payout reconciliation and bookkeeping. They must limit access, keep the information confidential and secure, and follow the retention, consent and contact restrictions in the host terms. This permission does not give hosts additional personal information, permission to sell it, or permission to contact you outside Chartd using information obtained through Chartd.
Tracked links. A host can make links to their event that carry a short code. The code identifies the link the host made, never you. When you open such a link, or RSVP, claim a ticket or buy one through it, Chartd adds one to that link’s counts. To count each RSVP and ticket only once, we keep a record of which link it came through; no host is ever shown that record. The host and any co-host who has accepted see only totals for each link, never a list of names. If a host sends a link to just one person, that link’s totals can show what that person did. On this website the code is not stored in your browser.
People helping at the door. A host can ask people with a Chartd account to help check tickets at their event’s door. A helper sees only whether a ticket is valid, its ticket type and how many people have been checked in so far. A helper the host has allowed to take cash also sees the door sales they recorded themselves (ticket type, amount and time), never a name. They do not see your name, your email address or the guest list. If you help at someone’s door, the username on your Chartd account is stored against each ticket you scan. The host and any co-host who has accepted can see how many tickets you scanned, and anyone checking tickets at that event who scans the same ticket again is shown your username.
If you are under 18. If the date of birth on your Chartd profile means you are under 18, you are not counted in any of the grouped statistics in point 2, you are not in any of the lists in point 3, you are in none of the attendee or audience files in point 5, and no host can email you or reach you through Host Broadcasts by Push — we refuse to send it regardless of any switch. We can only do this for accounts that have given us a date of birth; an account that has never given one is treated as an adult.
If you have no Chartd account. If you take a free ticket or buy one on this website without an account, the host sees the name you typed if you gave one, and otherwise a masked form of your email address, like ab***@e***, instead. They never see the address itself. If the host is notified of your ticket, as a sale or as part of a count of new RSVPs, the notification never carries your name or email address. You are in none of the grouped statistics, in none of the lists, in no downloaded list, and no host can email you through Chartd. A walk-in who pays cash at the door is recorded the same way, with no account: the host, an accepted co-host, or a door helper the host has allowed to take cash may type the name you give when recording the sale, and giving one is optional. That name is shown only to the host, the accepted co-host and Chartd’s administrators — a door helper sees the sales they recorded but never the name — and it appears in those people’s attendee lists and in files they download. It is never used for grouped statistics or for email.
How long we keep it. Ticket records are kept indefinitely: ticket payments are made to Chartd, which pays hosts by hand, so these are payment records. The exception is a door sale: a ticket a host or their team records for cash is the host’s own record of cash they collected at the door. Chartd never receives that money, pays nothing out on it and charges no fee on it. These records are kept with ticket records. The log of attendee-list and audience-list downloads is kept for 24 months. A message a host sends through Chartd is kept for 24 months, and the per-person delivery record behind it — which is the part that holds the address we delivered to — is kept for 180 days. A message a host wrote and never sent is deleted after 30 days. The record of you turning host email on or off is kept for the life of your account and is deleted when you delete your account. While host messages by push are switched on at Chartd, when a host’s message goes to a group you are in, we keep a record of it for push for 30 days, whether or not it reached you as a notification, including when you have not turned on Host Broadcasts by Push. A file a host has already downloaded is not recoverable by us at all.
Where the controls are. The host-email switch is in the Chartd app’s privacy settings in the latest version — under Settings › Privacy on both iPhone and Android — and in the footer of every message a host sends you. The Host Broadcasts by Push switch is in Settings › Notifications. Deleting your account from the app removes your consent record and your per-host mute list. For attendee-list and audience-list downloads, if you ask us what a host holds about you, we can tell you which hosts have downloaded a file that could include you and when, but not what is in a copy that has already left Chartd.

How We Protect and Share Your Data

We do not sell your data. We do not give your profile, your events, your photos, your messages or your ticket history to advertisers or to data brokers. The one thing that goes to an advertising company for advertising purposes, said plainly: the iPhone app reports app installs and app activity to Meta and to Google (Firebase) so that we can measure our own advertising, and both of those companies also sell advertising. See Advertising and analytics in the app above for how to switch that off. Separately, Apple and Google deliver our push notifications, including the text of messages sent to you, as our service providers and only to deliver them (see the next point).
We share data with the service providers needed to operate Chartd (for example, Stripe for payments, our hosting providers, and Apple, Google (Firebase Cloud Messaging) and Amazon Web Services for delivering push notifications), and with event hosts. Service providers receive only what they need to do their job; the AI companies we use are covered separately in Artificial intelligence, and what it is sent below. Event hosts are a separate recipient group; the information they receive is described in What event hosts can see above. Amazon Web Services also hosts the server that looks up the map location and time zone of an address you enter when you post an event on this website, as described in Posting events on this website above. Amazon Web Services also hosts the server that reads a spreadsheet a business imports, and looks up the map location and time zone of its addresses, as described in Importing events from a spreadsheet above.
We regularly review our security practices to keep them up to date.

Artificial intelligence, and what it is sent

This section describes AI features inside the Chartd app and website. Using Chartd from your own AI conversation is covered separately in Chartd in ChatGPT and compatible AI services below.

We use two AI companies, and here is exactly what each one gets. When you use AI search or “Plan My Day”, your question goes to OpenAI, along with the names, venues and times of the upcoming events near you that we want it to rank. If you build an event by pasting text or attaching a flyer photo, that text or photo goes to OpenAI as well. If you are a business on our Pro plan, your own event performance figures — views, taps, tickets sold, gross sales and guest counts — go to OpenAI to produce the analytics and forecast cards. Separately, if a host connects a website so we can import its events, our nightly importer may send the text of that page to OpenRouter when it needs help reading the listings.
We do not tell them who you are. This is the part worth being precise about: your Chartd account id, your name, your email and your device identifiers are not sent with any of it. The request carries the question and the event details and nothing that identifies you, and it is sent by our servers rather than by your phone, so your IP address does not go either. We keep a count of how many AI requests an account has made, to enforce plan limits — we do not keep the text of what you asked.
Two things we will not pretend about. The list of nearby events we send alongside your question is chosen by distance, so it does imply roughly what area you are in, even though no location is sent as such. And if OpenAI returns an error, our logs can briefly include part of what was sent.
What it is not used for. Neither company is given your data to advertise to you, and nothing here is sold. We do not use AI to decide anything about you — it ranks events and reads listings.

Chartd in ChatGPT and compatible AI services

What we receive: When you use Chartd through ChatGPT or another compatible AI service, that service sends the event-search terms, chosen event destination, category, dates, result limit, or event identifier needed for your request. We use those inputs to find and return public events. You do not sign in to or connect a Chartd account for this integration.
Location: For a nearby search, we use only a coarse city supplied by your AI service. We ignore coordinates and other location fields, and do not send them to our event database. A city or venue you explicitly choose is a search destination, not a statement of where you live. Searches that do not ask for nearby events ignore the supplied location hint. You can choose a destination or search more broadly without using that hint.
Who processes the request: Amazon Web Services hosts this integration, and Supabase processes the event lookup. The service and event database are hosted in the United States. We return public event titles, descriptions, categories, venues, addresses, dates, organizer names or labels, and Chartd links to the AI service you are using. This integration does not provide private events, guest lists, account information, or payment details, and cannot RSVP or buy tickets.
Records and retention: The integration application does not save search history, write your searches to the event database, or log request bodies. This does not mean there are no provider logs. AWS operational logs, such as invocation identifiers, times, duration and errors, have a 14-day retention setting; deletion after expiry is not immediate. Supabase API and database logs have one-day retention under our current project plan and can include request URLs and search filters, together with request times, network addresses and response status. Requests to Supabase come from our server; we do not forward your client IP address or account identity to it.
Your AI service: Your request and the results may remain in your AI conversation. That service controls its own conversation retention and data use. For ChatGPT, see OpenAI's privacy policy and the data controls available in your account. The operational-log periods above do not set the retention of your AI conversation.
Your choices and requests: You can stop using or disconnect Chartd in your AI service at any time. This stops future requests through that connection but does not erase existing provider logs or your conversation history. Use your AI service's controls to manage that history. To ask about access to or deletion of records held by Chartd, email hartley.caleb@chartdapp.com. Because this integration does not link requests to a Chartd account, we may need the approximate time and details of a request to locate relevant operational records; we cannot promise to identify or individually erase every entry in provider logs before their retention period ends.

Your Choices

The host-email switch is off by default. You can turn it on or off in the Chartd app’s privacy settings, under Settings › Privacy on both iPhone and Android. Each host email includes a link to stop emails from that host and another to stop emails from all hosts; neither requires you to sign in.
Weekend picks by push are off until you turn them on. You can turn them off at any time in the Chartd app under Settings › Notifications, or stop all notifications from Chartd in your phone’s settings. Signing out on a phone removes its record, as described above.
In versions of the app that offer them, message, invite, event and host notifications are on while your phone allows notifications from Chartd; each kind can be turned off in Settings › Notifications. Host Broadcasts by Push is off until you turn it on there.
The grouped audience statistics described in point 2 of What event hosts can see are not optional and cannot be switched off. Turning off host email or using an unsubscribe link does not stop that aggregate sharing.
To access or delete information we hold about you, email hartley.caleb@chartdapp.com. Note that signed business agreements are legal records and may need to be retained even after a deletion request.

Changes to Our Privacy Policy

We may update our privacy policy from time to time to reflect changes in our app or to comply with legal requirements.
Any updates will be posted on this page with a new effective date, and we encourage you to review it regularly.

By using our app or website, you agree to this privacy policy. If you do not agree, please do not use Chartd.

Chartd User Agreement

Last updated: October 9, 2026

Before using Chartd, please read this User Agreement carefully. By using Chartd, you agree to be bound by the terms and conditions of this Agreement.

User Conduct

You agree to use Chartd for lawful purposes only.
You agree not to post any content that is obscene, defamatory, threatening, or infringes on the rights of others.
You agree to be respectful to other users and to treat them with kindness and respect.

User Content

You are solely responsible for the content that you post on Chartd.
By posting content on Chartd, you grant us a non-exclusive, royalty-free, worldwide license to use, copy, distribute, and display your content in connection with Chartd.
You represent and warrant that you own or have the necessary rights to the content that you post on Chartd.

If you are an event host

This section applies whenever you host an event on Chartd and are shown, download, or send messages to the people attending it. What Chartd shows you about them is set out in What event hosts can see above. Before your first download and before your first message to attendees, Chartd asks you to acknowledge these obligations in the app or on this website and records that you did.

You may use attendee, ticket-sales and financial information from your own events to run and promote those events, manage your own customer records, and carry out financial reporting, payout reconciliation and bookkeeping, subject to the contact and consent restrictions below. Nothing else is a permitted use.
You may upload this information to your private CRM, Google Sheets, accounting software or other service providers acting only on your behalf for these permitted purposes. Limit access to the staff and providers who need it, require them to keep it confidential and secure, and do not allow them to use it for their own purposes. You must not sell, rent, trade or publicly share the information, give it to another business for its own use, or upload it to advertising audiences, data brokers or shared mailing lists.
You must delete it from your own systems and require your service providers to delete it when you no longer need it for a permitted purpose, and you must delete an individual’s information promptly if that person or Chartd asks you to. If the law requires you to retain particular accounting or transaction records, retain only what is required, restrict its use to that requirement, and delete it when the required retention period ends.
A file you download leaves Chartd. From that moment you are responsible for it: for keeping it secure, for complying with the privacy and marketing laws that apply to you, and for honouring a deletion request about it. Chartd cannot recall that file and cannot delete it on your behalf.
Chartd records every attendee-list and audience-list download — which host, which event or list, when, and how many rows — and an attendee may ask what you hold about them. A dashboard CSV is prepared locally and its download is not recorded; the same obligations apply to that file.
The only way to email your attendees through Chartd, or to send them a promotional notification, is Chartd’s own message tool, which sends on your behalf without giving you anyone’s address and honours every unsubscribe and notification setting. You must not use attendee information obtained through Chartd to contact anyone by any other means, and you must not try to work out or obtain an attendee’s email address, phone number or date of birth from what Chartd shows you.
You must not use grouped statistics to identify or single out an individual, including by combining them with other information. You may organize exported records in the permitted tools for the purposes above, but must not enrich them to discover personal details Chartd has not provided, or use them for unrelated profiling or advertising.
Breaking any of this ends your access to these tools and may end your access to Chartd altogether under the Termination section below, and we may remove your events.

Cash at the door. Door sales you, your co-host or your door helpers record are your responsibility. That cash is collected at the door by you, not by Chartd: Chartd never receives it, pays nothing out on it and charges no fee on it, and a door sale is never part of what Chartd pays you. You see each door sale on your event — its ticket tier, the amount, the walk-in’s name if one was typed, and who recorded it. A walk-in’s name is optional, and nobody should type anything other than the name the guest gave.

Liability

We are not responsible for the content that is posted on Chartd.
We have the right to remove any content that violates our User Agreement or that we deem inappropriate in our sole discretion.
We are not liable for any damages that result from your use of Chartd, including but not limited to any direct, indirect, incidental, special, or consequential damages.

Termination

We reserve the right to terminate your access to Chartd at any time, without notice and without liability to you.
Upon termination of your access to Chartd, you must immediately delete the app from your device.

Modifications

We reserve the right to modify this User Agreement at any time to reflect changes in our app or to comply with legal requirements.
Any updates to our User Agreement will be posted on our website, and we encourage you to review it regularly.