Gatherjar › Privacy
Privacy Policy — Gatherjar
Last updated: 11 November 2026
This policy explains what happens to data when you use Gatherjar (the “App”), the event planning website published by Cronomz — “we”, “us”.
Contact: support@gatherjar.com
Gatherjar keeps what you put into an event (its details, the guests’ names and answers) so everyone with the event link sees the same plan. Accounts are optional (sign in with Google), and there are no ads and no analytics. We never sell or share your data. Venue search and maps come from Google, optional AI helpers use Claude by Anthropic, and the App runs on Cloudflare.
1. The short version
| Do I need an account? | No. Hosts and guests are recognised by a secret link and a cookie on their device. Anyone can choose to sign in with Google so their events follow them to any device (section 2a). It is never required. |
| Who can see my event? | Anyone who has the event link. Treat the link like a group chat invite: share it only with people you want there. |
| What do guests have to give? | A name, typed or tapped from the host’s list of who’s invited. A phone number is optional and only the host (and co-hosts the host chooses) see it. |
| Do you run ads, analytics or tracking? | No. There is no advertising, analytics or tracking code in the App. |
| Do you sell my data? | No. We never sell, rent or share personal data. |
| How do I delete things? | Hosts can delete the whole event, and guests can remove themselves, right in the App (section 7). |
2. What we store about an event
When you create or answer an event, our database (Cloudflare D1, see section 6) stores:
- The event — its title, description, the host’s name, date and start and end time or dates (or the date options), place (or the place options; for a place picked from the venue finder, only its name and Google place ID, see section 5), time zone (which the host can change), whether and when the host cancelled or postponed it (with their note to guests, if they wrote one; a postponement note is removed once there’s a new date), the date before the host last moved or postponed it, the place before the host last changed it, whether it’s an online event (a video call, whose link is stored as the place’s link), the host’s language (so the invitation opens in it), colour, seat limit (and whether it counts only children), what it costs guests if the host writes it (“we split the bill”), polls, bring list and announcements, and, if the host adds them, the names of the people they’re inviting (so guests can tap their name instead of typing it). If someone on that list removes themselves from the event, their name stays on the host’s list, marked as not coming, so the host’s updates stop asking them.
- The schedule and budget — the stops the host adds to each day (time, place, address, map link, note; for a place picked from Google, only its name and Google place ID) and their costs, in the event’s currency, and how many people the host expects (shared costs are split among at least that many). The currency is guessed from the host’s country when the event is made. A day can split into groups (for example diving and a spa day): the host names the groups and puts stops in them, and each guest chooses which group they join, or the host puts them in one. Which group a guest joined is saved with the event and the other guests and the host see the names in each group. Costs of a group’s stops are counted only for the people in it. The host can set a maximum number of people per group, and can send a reminder (a push notification, or a message they send themselves) to the guests who haven’t chosen a group yet; Gatherjar only remembers when the last reminder was sent so it can’t be sent more than once an hour.
- How people are getting there — the flights, trains, buses and ferries that people add: where from and to (an airport code and name, or a station or port), the local date and time at each end and the time zone there, the flight or train number, a short note and who is on it. A guest adds their own (and can tick the people in the event travelling with them, or say they’re on a journey someone else added); the host can add some for the group or for people they list. Everyone in the event, and the host, can see every journey (someone with only the link, who hasn’t answered the invite, can’t). We never store booking codes, ticket or seat numbers, passenger names or passport details. They are deleted with the event, and a guest’s own journeys are deleted if the guest removes themselves. Gatherjar works out from the journeys when people land at the same place close together, so it can suggest sharing a ride, and a push notification (a day before a flight, and a few hours before any journey) goes only to the people on it who turned reminders on.
- Saved places — the event’s shortlist of places people want to go: each place’s name, area, map link, a short note, the link and account of the post it came from (if it came from one; a place copied from someone’s Your places, section 2g, brings its post link along), who added it, and who likes it (♥). Everyone with the event link sees the list and who added each place; only the host sees who liked which place. A place leaves the list when the host puts it into the schedule or a vote, or when the host or whoever added it removes it, and everything goes with the event. A guest’s likes are deleted if the guest removes themselves.
- Changes guests suggest — when a guest suggests another date or place, a change to a stop, a stay or a journey, or a place for everyone to stay: what it’s about, the date or time, the place (with its map link) and the note they wrote. Only that guest and the host can see it. It is deleted when the host uses it, puts it to a vote or lets it go, when the guest takes it back, if the guest removes themselves, and with the event. If reminders are on, the host gets a notification about it and the guest is told what the host did. When the host takes a date or place a guest suggested out of a vote, we keep a short note for that guest (which date or place) so they see it next time they open the event, until they tap OK.
- Where people stay — the stays the host adds for the group or for some of the guests (name, address and map link, or for a place picked from Google its Google place ID instead of those two, check-in and check-out dates, cost, note and who is in it), and a stay a guest adds for themselves. A stay a guest adds for themselves is visible only to that guest and the host, unless the host turns on “Show who is staying where”, which shows every stay to everyone with the link; the host’s stays are always visible to everyone with the link. They are deleted with the event, and a guest’s own stay is deleted if the guest removes themselves.
- Each guest — the name they typed, their phone number if they chose to give one, whether they’re coming and how many people they bring (and how many of them are children, if they say) (when the host picks a date, a guest who hasn’t answered yet, or said they were coming before there was a date, gets the answer from their vote for that date, and is asked to confirm it), a note to the host if they write one (for example an allergy), and any messages that guest and the host or co-hosts send each other in the event (only that guest, the host and co-hosts can see them, and they’re deleted with the event), the time zone their device is set to (so the host and co-hosts can see what time the event is for them; nobody else sees it), their poll answers, the places they suggested, the bring-list items they claimed and, if they wrote one, what exactly they’re bringing. If the host lets guests do so, also the polls they start and the announcements they post, shown with their name. If they remove themselves, those stay in the event without their name. The host is added as a guest of their own event, marked as going. When a guest who was coming says they can’t, the host gets a short note on their event page (the guest’s name and what they had said they’d bring, now back on the list) until they tap OK, and a notification if reminders are on.
- Your dashboard — the list of your events, what needs you, and your most frequent places and people are worked out from the events above each time you open it. Nothing extra is stored for it, and it only uses events you host or joined on that device. When you open a new event on a device that already answered others, the name you used there is offered so you don't have to type it again; it never leaves your device's own events.
- A fingerprint of each secret link — we store a one-way hash of the host and guest links, not the links themselves, so we can recognise you without being able to recreate your link.
2a. If you sign in with Google
Signing in is optional, for hosts and guests. If you choose Sign in, Google asks you to share your basic profile with Gatherjar, and we store:
- your Google account ID, email address and name, so we can recognise you next time;
- which events are linked to your account: events you host, and the events you joined as a guest, on the browser where you sign in or while signed in;
- a sign-in session for each browser you use, stored only as a scrambled (hashed) form of the session cookie, which expires after 60 days without use.
We use the email address only to show which account is signed in, and other people never see it: in an event you appear with the name you typed there. We only email you if you turn on reminder emails (section 2c), and, if you bought Pro, once a few days before it ends (it doesn’t renew by itself). We don’t receive your Google password, contacts or anything else from your Google account. Google handles the sign-in under the Google Privacy Policy.
Deleting your account: tap your initials at the top of your events → Delete account. The account, its sessions and the places saved in Your places are deleted straight away. Your events stay and keep working with their host links; delete them separately if you want them gone.
2b. Guests the host removed
When a host removes a guest and chooses to stop them joining again, we keep a scrambled (hashed) form of that guest’s link for the event, so their browser can’t rejoin it, and, if they were signed in, a note of their account so it can’t rejoin either. Both are deleted with the event.
2c. Reminders
Reminders are optional. They are sent the day before an event, when a vote is about to close, when someone hasn’t answered yet, and when bring-list items are still unclaimed, never at night in the event’s time zone. Each reminder is sent once.
- On your phone (notifications). If you choose Remind me on this phone and allow notifications, your browser gives us a notification address and encryption keys for this browser. We store them with the event you turned reminders on for (and which guest you are, or that you are the host) and the language to write in. Besides reminders, guests get the event's announcements (from the host, or from another guest when the host lets guests post) and a note when they get a place from the waitlist. Messages are encrypted for your browser and delivered by your browser’s own push service (for example Google for Chrome, Apple for Safari, Mozilla for Firefox), which can’t read them. Turning the switch off, blocking notifications, or deleting the event removes this.
- By email. Only if you signed in and choose Email me reminders. We send them to your Google account’s email address through Resend, our email provider, under the Resend privacy policy. Every email has an Unsubscribe link, and you can switch them off in any event.
- Through WhatsApp. The host’s Remind people screen prepares messages that the host sends from their own WhatsApp. We don’t send these and receive nothing back.
- In your calendar. Add to calendar files include alarms that your calendar app shows itself. Nothing is sent to us.
To avoid sending a reminder twice, we keep a note of which reminders went out for each event. It is deleted with the event.
2d. Bills and paying each other back
Bill splits. You can also start a bill split, which is only about the bills: it has a name, a currency, the host and a list of people, but no date, place or answers. The host types the names of the people on it, so you may be on a list by a name someone else typed; nobody has to join, and the host can add every bill alone. Typed names are held until someone picks them: a person who opens the link taps their name and is asked Is this you?, after which the bills already on that name are theirs to see. There is no sign-up, and a name is not proof of who someone is: anyone with the link can pick a free name, so share it only with the people on the list. A person can let go of the name they picked, and the host can give a name back to the list; the bills stay on the name. Until someone picks a name, they can see only the title, the host’s name, the names on the list and which are taken: bills, payments and who owes whom are visible only to people who picked a name, and to the host. Everything below applies to a bill split in the same way.
Anyone who answered an event (and its host) can add a bill the group paid, and say how it is split. Gatherjar never holds or moves money: people pay each other directly through their own bank or e-wallet, and Gatherjar only keeps track. We store:
- Bills — the title, shop name, date, currency and exchange rate, the total, each line (item, tax, service charge, tip, discount) with its amount and the people who share it, who paid, who added it, the schedule stop it belongs to (if any), a note, and an optional photo of the bill (a long receipt can be up to four photos). The names of the people on a bill are kept on it, so the bill still reads correctly if someone later removes themselves.
- Flags — if a person on a bill taps This looks wrong, or someone left off it taps I was there too, we keep who and an optional note. Only the person who added the bill and the host can see who flagged it. If the person who added it answers that the bill is right as it is, we keep that answer and their optional reply, which the person who asked sees.
- Payments between people — when someone taps I paid: who, to whom, the amount, an optional screenshot of the transfer, and whether the other person confirmed it. Only the two people involved and the host can see the screenshot.
- How to pay me — an optional text (for example a bank account number or e-wallet number) and an optional payment QR image that a person saves so others can pay them back. Everyone in the event who answered, and the host, can see it. When a host starts the next split from one they host (“Start the next one”), their text is copied into the new split (not the QR image).
Everyone who answered an event, and the host, can see its bills and who owes whom. Images are stored in Cloudflare R2 (see section 6) and served only through Gatherjar, which checks who is asking. Photos of bills and transfer screenshots are deleted 90 days after the event (after its last day; for a bill split, 90 days after anyone last used it): the bills and payments stay, without the picture. Payment QR images are deleted with the event. A bill someone deletes is kept for one hour, with its photos, so they can tap Undo; after that it is gone for good. The older “money jar” (the host collecting a fixed amount from each guest) is switched off.
2e. Reports
Every event page has a Report link for events that are scams, abusive or illegal. A report stores the event it is about, the reason you pick, the details you write (optional), your email address if you give one (optional, so we can reply), and a scrambled (hashed) form of your IP address, which lets us limit reports to a few per person a day. The host is not told who reported their event. Reports are kept until we have looked at them and are deleted with the event.
2f. Buying Pro
Pro is bought for a month or a year by a signed-in account, and makes every event that account hosts Pro while it lasts. It is paid once for the time chosen and doesn’t renew by itself. (Pro for a single event was sold until 17 October 2026; those events keep it.) Payment is handled by the payment provider (section 6): we never see or store card numbers, bank logins or e-wallet details. We store a record of each purchase: what was bought (a month or a year of Pro for which account, or, for older purchases, Pro for which event), the price and currency, which provider handled it, the provider’s order number or purchase token, whether it is waiting, paid, failed or refunded, and when. The account also stores the date its Pro ends, and for which end date the “Pro ends soon” email was sent. We keep purchase records for as long as tax and accounting rules require, even after the event is deleted (without the event’s content).
2g. Your places
Your places is a list of places you want to go someday, kept outside any event. You can add places from a post or a link (as in “Places from a post”, section 6a), from a Google search (section 5), typed in, from Google Maps lists you export with Google Takeout, or by sharing a post or a place to Gatherjar from another app. For each place we store its name, the area or neighbourhood (from the post, the link or what you typed; never an address from Google), a map link, its Google place ID if it was picked from Google, a short note, a kind (café, beach…), the city or trip area it’s in (such as “Bandung” or “Bali”), and the link and account of the post it came from. Google Takeout files are read once and not kept: only the place names, notes and links in them are saved.
Only you see your list. If you are signed in, it belongs to your Google account; if not, it belongs to this browser (the gj_dev cookie, section 4) and moves to your account when you sign in. When you plan an event and leave Add my saved places on, the places in the event’s city or trip area are copied into the event’s saved places (section 2), where everyone in the event can see them; when you join someone else’s event, you are asked before yours are added. Places copied into an event stay in your list.
3. Who can see what
- Everyone with the link of a bill split sees its title, the host’s name and the names on the list (and which are taken), not the bills.
- Everyone with the event link sees the event details, the schedule and budget, the guest list with names and answers, the names the host listed as invited who haven’t answered yet, the bring list, announcements and poll results. Names next to poll answers are hidden from guests if the host made that poll anonymous; the host still sees them. A name is not proof of who someone is: anyone with the link can tap a name from the host’s list, so share the link only with the people you’re inviting.
- Bills and payments are visible to the host and to the guests who answered; a screenshot of a payment is visible only to the two people involved and the host.
- Only the host, and the guests the host makes co-host, see guests’ phone numbers, the notes guests leave for the host, and the messages between each guest and the hosts. The App uses phone numbers only to give the host a WhatsApp button for that guest.
- We can see stored events when needed to keep the App running, fix a problem or answer a support request. We don’t read events otherwise and we don’t use them for anything else.
4. Cookies and storage on your device
| Name | What it’s for |
|---|---|
Host cookie (gj_h_…) | Remembers that you are the host of an event on this device. Lasts one year. |
Guest cookie (gj_g_…) | Remembers which guest you are in an event, so you can change your answers. Lasts one year. If your browser has forgotten you and you come back in under your name (“Yes, that’s me”), that browser gets its own guest cookie, and the host is told and can undo it. “Not you?” removes it (and, if you choose, deletes what was saved under that name). |
Sign-in cookie (gj_s) | Only if you sign in with Google: keeps you signed in on this browser. Lasts 60 days and is renewed while they use Gatherjar. “Sign out” removes it. |
Sign-in check (gj_oauth) | Only while signing in: protects the trip to Google and back. Lasts 10 minutes. |
Person check (gj_hv) | Only after the person check in section 6 runs: shows for 12 hours that this browser passed it, so it isn’t asked again. It holds a signed expiry time, nothing about you. |
Your places (gj_dev) | Only if you save a place to Your places without signing in: tells Gatherjar which saved places are this browser’s. It is a random code, and we store only a scrambled (hashed) form of it. Lasts 400 days; when you sign in, the places move to your account. |
Invite counter (gj_open_…) | Set when someone who hasn’t answered opens an invite, so we count that the invite was opened once, not on every visit. It holds no information about you, and the count it feeds is a daily total with the browser language, nothing else. Lasts 60 days. |
Language cookie (lang) | Remembers English or Indonesian if you choose one. Lasts one year. |
Appearance cookies (gj_theme, gj_mode) | Remember the theme and the light, dark or automatic setting you choose in the Appearance menu. Lasts one year. |
| Browser storage | The name you used as a host (to fill it in next time), the last area you searched for venues, and which events you turned phone reminders on for, and which events you asked to see translated. These never leave your device. |
These are all needed for the App to work. There are no advertising or tracking cookies.
5. Venue search, maps and your location
- Venue search. When you use “Find a place”, the App sends what you typed (a place name, an area such as “Kemang”, and the kind of place) through our server to the Google Places API, which returns places with their rating, price and opening hours. We don’t store the search or the results; only the name and Google place ID of a place you choose are saved with the event. Its address, price and map link are not kept: they are looked up from Google again when someone opens the place’s details.
- “Near me”. If you tap it and allow it, your browser gives the App your approximate location, which is sent through our server to Google with the search so results are nearby. It is not stored.
- Buka bersama times. “Use my location” for the maghrib time works out the time inside your browser. That location isn’t sent anywhere.
- Place details. When you open “Details” for a place, the App asks the Google Places API, through our server, for that place’s current address, rating, type, price level and opening hours. Only the place ID is sent. The answer is shown to you and not stored.
- Map card. In the same “Details” sheet, a Google map is loaded straight from Google into the page, and “Directions” opens Google Maps.
- Schedule map. The schedule on the Plan tab can show a day’s stops on a Google map with a route between them. This is the same free Google map as the map card, loaded straight from Google; your browser is sent the stops’ place IDs, or their names and addresses, so Google can draw the route. For a stop that was typed in rather than picked from the venue finder, our server first asks Google’s Geocoding service where it is (sending its name and address, and the area the trip’s other places are in), so the route doesn’t break on a name Google can’t find; the answer is kept as described in the next item.
- Whole-trip map (Pro). The “All days” map is the Google Maps JavaScript API, loaded straight from Google only when you open it. To place the pins, our server asks Google where each stop is (by its place ID, or by its name and address, which is sent to Google’s Geocoding service). We don’t store these coordinates in our database: they are kept in a temporary cache at the edge of our hosting provider for up to 29 days and then asked for again. The same locations let Gatherjar tell when a stay is far from where its days go, and let the host put a day’s stops in a sensible order. No names of guests are sent. The host’s “Maybe” places are shown on this map too, and only to the host. When the host taps a place on this map to add it, our server asks the Google Places API for that place’s name and address (only its place ID is sent), and the host can add it to the schedule or to their Maybe places; nothing is stored unless they add it.
- Fonts. The App loads its typeface from Google Fonts.
For the map card, the schedule maps and fonts your browser connects to Google directly, so Google receives your IP address and may use cookies, under the Google Privacy Policy. Place information is shown under the Google Maps Terms.
Daily search limit. To keep venue search free, each device can search, and open place details, a limited number of times a day. To count this, we store a daily counter next to a scrambled (hashed) form of your IP address (for an IPv6 address, only the part that identifies your network). The same kind of counter limits how many events one device can start in a day and how often the AI helpers can be used outside an event. Counters from earlier days are deleted, so it is kept for one day at most.
6. Hosting and other services
- Cloudflare hosts the App, its database (stored in the Asia-Pacific region) and its image storage (R2). Like any web host, it handles your IP address and the pages you request. Cloudflare also keeps the App’s logs (errors, and details of each request such as the page address, which can include your IP address) for up to 7 days so we can find and fix problems. The App uses the country and time zone Cloudflare detects to suggest your language, holidays and time zone. Before the AI helpers or the venue search are used outside an event, Cloudflare Turnstile may check that you are a person and not a bot: it runs in your browser, usually without showing anything, and Cloudflare receives technical signals from your browser to do so. See the Cloudflare privacy policy.
- Public holidays for countries other than Indonesia come from date.nager.at. Our server asks for a country’s holiday list; no information about you is sent.
- Exchange rates come from Frankfurter (the European Central Bank’s daily reference rates), to show a rough amount in your own currency next to costs in another one. Our server asks for the rate between two currencies; no information about you is sent.
- WhatsApp. Share buttons open WhatsApp with a message you can edit and send yourself. We receive nothing from WhatsApp.
- Payments for Pro (only if you buy it): on the website, Midtrans (QRIS, GoPay, ShopeePay) and Polar (cards, in US dollars; Polar is the seller of record, so it handles the receipt and sales tax or VAT); and in the Android app, Google Play. You pay on their page or sheet, under their privacy policy. We send them the item and price, a purchase number, your account’s ID (Polar only) and your email address for the receipt; they tell us whether the payment went through and, if it is refunded, that it was.
6a. The AI helpers (Claude, by Anthropic)
Some optional buttons use Claude, an AI model made by Anthropic, to fill things in for you. They only suggest: nothing is saved until you choose it. When you use one, our server sends Anthropic only what that helper needs:
- Describe it in one sentence and From the group chat: the text you typed or pasted. A pasted chat can contain other people’s names and messages, so paste only the part about dates and leave out anything private.
- Suggest a list for the group: the event’s title, type, description and number of people.
- Places from a post (when you paste a link to a TikTok, an Instagram post, a YouTube video or a web page, its caption, or a screenshot): Gatherjar opens the link the way a link preview does, without signing in to anything, and sends what the post shows publicly (its caption, the place it’s tagged with, text on the video and its cover picture), or what you pasted, to Claude to list the places in it. The post itself isn’t stored; only the places you choose to keep are saved with the event (see “Saved places” in section 2). A Google Maps link is read without Claude.
- Your places: to tell which city or trip area a saved place is in, its name, its area and its map link, and for a place picked from a Google search its address (which isn’t stored), are sent to Claude; for Google Maps lists, the names, notes and links in them. When an event’s place is set, its name (and the address the host just picked, if any) is sent the same way to tell the event’s city or trip area, which is kept with the event and remembered for the same name.
- Translate (for a guest reading the event in another language): the event’s own texts, and nothing else, are sent to Claude to translate them into the language the page is in: its title, description, cost line and announcements, the bring list with what guests wrote they’re bringing, the notes on its saved places, and the schedule’s stops, their notes and the rides between them, the bills’ names, and the polls’ questions and choices (not place or date choices; no names of who wrote any of them). The translation is stored with the event (and deleted with it), so the same text isn’t sent again when someone reloads the page or the next guest asks; only texts that are new or changed since are sent, also when something is added while the page is open translated. Your browser remembers that you asked, so the page opens translated next time.
- Rewrite the update (casual, polite or short): the group update, which includes the event’s date and place and the first names of who’s going or hasn’t answered.
- Bills (Pro): a photo of a bill that someone adds with Snap the bill (or up to four photos of a long receipt, sent together) is sent to Claude, which reads the items, tax, total and the number of guests printed on it so the group can split them. The person adding it checks the result before saving.
- Payment screenshots: while the helpers are on, a transfer screenshot someone adds to I paid is sent to Claude automatically, so the person being paid can see at a glance whether it matches the amount and whose account it went to. Their phone compares that with the payment details they saved; nothing extra is sent.
- While Claude drafts the plans (which can take a few minutes), Gatherjar keeps a note with the event that a draft is running and, if it failed, why, so the host can close the page and come back. The request to draft is passed to a background job through Cloudflare’s queue service, which holds it only until the job runs.
- Read a ticket (Pro): when someone uploads a photo, screenshot or PDF of a ticket or booking email, or pastes its text, Gatherjar sends it to Claude to read the route, times and flight or train number, which the person then checks. We ask Claude to leave out booking codes, ticket and seat numbers, names and passport details. To put the other travellers on the journey too, Gatherjar also sends the names of the people in the event (as they appear in Gatherjar), and Claude says which of them are on the ticket; the names printed on the ticket are not passed on. The file or text is sent once, only to read it, and is not stored; only the journeys the person chooses to add are saved (see section 2).
- Plan the trip (Pro): the destination, the event’s description, the number of days and people, how packed the host wants the days (packed, balanced or relaxed), where people stay (names, addresses, dates and who is in each stay), how people get there and home (the routes, local times, flight or train numbers and the first names of the people on each journey, but no booking codes or seat numbers), the stops already in the schedule, the event’s saved places (names, areas, notes and how many people like each one, not who), the results of the event’s place and activity votes (the options and how many people chose each), how many children are coming, the notes guests left for the host (with their names, for needs such as allergies), and the host’s answers to Claude’s questions about the trip (the feel, places they want to see, budget, and any group needs they mention, such as food or mobility). The plans Claude writes are then checked by our server (distances, times, opening hours) and, where something doesn’t work, sent back to Claude once with what to fix. When the trip’s destination is the event’s place and it was picked from Google, our server first asks the Google Places API for its address (only the place ID is sent), so Claude knows where the trip is; the address is not stored. Claude’s place searches go to the Google Places API as described in section 5, and it can look up an exchange rate from Frankfurter (section 6; only the two currencies are sent). So the host can come back to the ideas they didn’t pick (Plan B), Gatherjar stores those answers, the suggested plans and the stops the host set aside (“Maybe”) with the event; only the host can see them, and they are deleted with the event. How to get between stops (for example “Taxi, 20 minutes”), if the host keeps it, is saved with the schedule like the stops themselves.
- Ask Gatherjar (Pro, hosts only): what the host types into the assistant is sent to Claude together with a summary of the event as it is then (its name, dates, place and description, the guests’ names and answers, the polls, the schedule, stays, bring list and bills, the payments marked so far, and what the host owes or is owed). Phone numbers and bank or e-wallet details are not sent. Claude answers or fills in a form, which the host checks and saves. Gatherjar keeps the last ten questions and answers with the event so the assistant can follow on (“and add Budi too”); the host can clear them with “New chat”, and they are deleted with the event.
Anthropic processes this as our service provider to give the answer, under its commercial terms, which don’t allow it to train its models on it, and keeps it only for a limited time; see the Anthropic privacy policy. Gatherjar doesn’t store what you send, only the results you keep. To prevent abuse, each device can use the helpers a limited number of times a day, counted the same way as the venue search (section 5).
7. How long we keep it, and deleting it
Events and their guest answers are kept so the link keeps working, until they are deleted. Old events are deleted automatically: a free event 60 days after its last day, and a Pro event 2 years after it (an event without a date counts as over 90 days after it was made). A host’s events count as Pro while their Pro yearly lasts; when it ends or is refunded, they follow the free rule again, with the same notice before anything is deleted. Bill splits are not deleted automatically: after 90 days with no change and nothing left to pay they only move to an archive on the host’s dashboard, and they are kept until the host deletes them. The host gets a notification at least 7 days before (and an email, if they are signed in), and can download the guest list first. An event is never deleted without that notice: if it goes out later (for example when free early access ends and older events become due at once), the event is deleted 7 days after the notice instead. Before that, things can be deleted any time:
- A whole event — the host opens Event settings → Postpone, cancel or delete → Delete event. The event is deleted with all its guests, answers, votes, schedule, bring list and announcements. (Cancelling instead keeps the event, marked as cancelled with the host’s note, until the host deletes it.)
- Yourself, as a guest — tap your name at the top of the event and choose Leave this event. The host is told that you left. Your name, phone number, answers, votes, suggestions and bring-list claims are deleted. Money you paid that the host confirmed stays in the host’s records under your name (see section 2d).
- An answer under the wrong name — tap the name at the top of the event, choose Not you? and then Remove it and pick my name. Everything saved under that name on this device is deleted the same way. If the host added that name (for example in a bill split), the name and the bills it is on stay in the event for the right person; only what you added under it is deleted.
- A guest, as the host — the host can remove any guest from the People tab, which deletes the same data.
- Your account — see section 2a.
- Your places — remove a place on Your places (tap it, then Remove), or delete your account. Places saved in a browser that never signed in are deleted after a year with nothing saved or changed.
- Can’t use the App? Email us the event link (and, for your own answers, the name you used) and we’ll delete it for you.
Deleted events are removed from the database straight away. Cloudflare may keep backups of the database for a limited time (up to 30 days) before they expire. We also make our own backup copy of the database about once a week, kept privately in our Microsoft OneDrive storage so we can recover from a mistake. We keep the newest 8 copies (about two months), so a deleted event is gone from our backups once the copies made before it was deleted have been replaced. Photos and screenshots are not in these copies.
8. What we do not do
- We do not show ads, and we do not use analytics, advertising, attribution or crash-reporting code.
- We do not sell, rent or trade personal data, or use it for advertising.
- We do not ask for passwords or contacts, and nobody has to give an email address. People share theirs only if they choose to sign in with Google.
- We do not send messages to your guests on your behalf; you share the link yourself. Guests only get reminders they switched on.
9. Your rights
You have the right to access, correct, delete and object to the processing of your personal data. Guests can change their name, phone number and answers in the event at any time. For anything else, write to us. If you believe your data has been handled unlawfully, you may complain to your local data protection authority.
10. Children
Gatherjar is not directed to children under 13, and we do not knowingly collect personal data from children.
11. Changes to this policy
If Gatherjar starts handling data differently, this policy is updated before that change goes live, and the “Last updated” date above changes with it.
12. Contact
Cronomz
Email: support@gatherjar.com