Cronomz

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:

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:

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.

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:

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

4. Cookies and storage on your device

NameWhat 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 storageThe 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

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

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:

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:

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

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