Koding Krew Apps

Rally Point — Privacy

Last updated 11 August 2026 · applies to the private test build

Drafted by an engineer, not a lawyer. It is accurate about what the app does — every claim was checked against the database schema rather than remembered — but it has not had legal review.

Rally Point helps a group agree where to meet and when to leave. It is built so that the sensitive thing — where you live — cannot leak, because for the most part there is nowhere in it to put that at full precision.

What is stored

Your account. An email address and a display name. If you sign in with Apple or Google, we receive whatever that provider passes on — with Apple's “Hide My Email” that is a relay address, and the app works normally with it.

Your profile. A callsign, an optional avatar, and a coarse home region — a town and state, never a street address. Anybody sharing an event with you can read this, which is exactly why it is coarsened before it is written rather than only when it is shown.

Your saved home, if you set one. Precise coordinates, so the app can pre-fill your drive time without you typing an address every time. Only you can read it. It is deliberately kept in a separate table from your profile for that reason, it is never shown to anyone else, and it is never drawn on a map.

Events and convoys you take part in. Names, locations, times, the stops an organizer publishes, who is going, seats offered and needed, and any notes you add. Visible to the other people in that event. Locations an organizer publishes are precise — that is their purpose.

Your travel figures. A drive time in minutes, a distance rounded to whole miles, and the name of the town you set off from. The other people in your convoy see these three things. They are all that is kept.

Your garage, if you use it. Vehicles, service records, costs and receipt photos. Private to you.

Your agreements. Which documents you accepted and when. Append-only, so the record cannot be quietly revised.

What is not stored

Where you actually are, or set off from. When you work out a drive time, the coordinates you gave are sent to the routing provider, the answer comes back, and the coordinates are discarded. They are not written to the database and not put in a log. There is no column that could hold them.

Any trail of your movements. Live ETA, if you switch it on, runs only while the app is open and on screen, and each update replaces the last. Closing the app stops it. Nothing accumulates.

The shape of your journey. The app can draw the route a convoy published, because both ends of it are already shared with everybody in the event. It never requests, receives or draws the route from your starting point, because that line begins at your house.

What leaves the app, and to whom

There is no analytics, no advertising, no tracking, and no third-party SDK collecting anything. Nothing about you is sold or shared for marketing, and nothing is used to build a profile of you across other apps or websites.

Your choices

Permissions the app asks for

Each is requested at the moment it is used, never on first launch, and each can be declined without breaking the rest of the app.

PermissionAsked whenUsed for
LocationYou tap “Use where I am now”One reading, to work out a drive time. Discarded after.
CalendarYou tap “Show my calendar”Read-only, so you can pick an event you already saved. Never written to.
CameraYou photograph a receiptThe photo, stored privately to you.
Photo libraryYou attach an existing receiptThe photo, stored privately to you.

This is a test build

It may break, lose data, or be reset. Keep a note elsewhere of anything you would be sorry to lose.

Contact

Questions, or a deletion request: the person who invited you, or AppFeedback@kodingkrewapps.com.