ardeo

Privacy policy

ardeo · Last updated 27 September 2026

ardeo records prayer walks. Recording a walk means recording where you walked, which is sensitive, and this policy exists to say plainly what happens to that information.


Who we are

ardeo is made by Plugged Worship, a volunteer ministry group based in New Zealand. Plugged Worship is not a registered company, church or charitable trust. In this policy “we” and “us” mean Plugged Worship.

We are the agency responsible for your personal information under the Privacy Act 2020. Our privacy officer can be reached at privacy@ardeo.nz.


The short version


What ardeo records

Location. While a walk is recording, ardeo reads your phone’s GPS position repeatedly. This is the core function of the app and cannot be turned off while recording, though you can pause or stop at any time.

ardeo does not read your location when you are not recording a walk. There is no tracking between walks.

If you turn on background recording, the app keeps recording while your screen is off, while you are in other apps, and — on Android — after the operating system shuts it down or the phone restarts mid-walk. That is asked for separately from basic location permission, and it has its own setting, because it is a bigger thing to agree to. The location library that does this keeps its working data on your phone and sends nothing anywhere itself.

Steps. If your phone has a step counter, ardeo reads it during a walk and shows the count in the walk summary. Steps never affect the recorded distance, and the count is not uploaded.

Walk statistics. Distance, duration, moving time, start and end times.

Coverage areas. Your route is converted, on your phone, into a grid of hexagons roughly 65 metres across. These record that you passed through an area, not the path you took through it.

Prayer notes. What you prayed for on a walk: the categories you pick, and anything you write, up to 600 characters each. Each note is pinned to a point on your walk, and that point and the time you made the note stay on your phone. What the note says goes with the walk to whoever you share the walk with (see Who can see what). The notes on a walk you keep private are not uploaded at all.

Prayer notes you made before your phone took the 26 September 2026 update were made under the promise that they would never leave it, and they still will not — whatever you share their walk with.

Walks shared before then could carry a separate note on the walk itself. Those notes are still shown with their walks. Nothing writes one any more.

Your profile. A display name, a handle, and a photo if you add one.

Groups. The groups you create or join, your role in each, and — for a group you run — its name, description, logo and cover picture.

Planned walks. A group’s admins can plan a walk for the group: a title, a date and time, where to meet, and a note. The meeting place is words you type, never a point on a map. When you say you are coming, that is recorded against your account. When you finish a walk that started close to a planned walk’s time — from half an hour before to three hours after — the app offers to count it toward that walk, and records which planned walk it counted toward if you say yes.

Account details. Your email address, and the name your sign-in provider gives us. If you use Sign in with Apple you can choose to hide your email, and we receive a relay address instead of the real one.

Technical information. When your phone talks to our servers, those servers see its IP address and record it in their logs, along with the time and what was asked for. We do not use this to track you; it is how the services diagnose faults and stop abuse.


Signing in

Apple and Google sign you in through their own screens on your phone. They tell us your email address and name, and they know you signed in to ardeo.

Email links are sent for us by Resend, from sign-in@ardeo.nz. To send one, Resend is given your email address and the message, which contains a single-use sign-in code that expires after an hour.


Where it goes

Your account, profile, groups and walks are stored in one place: our database, hosted by Supabase in Sydney, Australia.

Every walk you save is uploaded once the app has worked out its coverage — the statistics, the grid squares, which audience you chose, the note on the walk if it is an older one that has one, and for a walk you share, what its prayer notes say. That includes walks set to private. What stops anyone else reading a private walk is row-level security enforced by the database itself, not a filter in the app, and it is tested against a real database rather than a stand-in.

Your route line is never uploaded, at any setting, to anyone. The server has no column to store one. That is deliberate and it is the strongest guarantee in this policy: the cheapest way to be certain a route is never leaked is to have nothing to leak.

If you sign in on a new phone, your saved walks come back to it from our database — with their statistics and grid squares, but no route line, because there is none to send, and no prayer notes, because without the point each one was pinned to there is nowhere on the walk to put them.

Information that leaves New Zealand

Most of the services we rely on are overseas. Supabase holds your data in Australia; Resend, Expo, Apple, Google, GitHub and Cloudflare are based in the United States; FormSubmit, which delivers the beta sign-up form, is run from Sri Lanka. We use them under their terms of service, which require them to protect the information they handle for us and to use it only to provide their service. We do not send any of them your walks except Supabase, which stores them.


Who can see what

A finished walk is given to one of four audiences. They are four separate audiences, not a ladder. A friend does not see a walk you shared to a group they are not in, and a group does not see one you shared to friends.

  You Friends A group you shared to Anyone signed in
The line you walked On your phone only Never Never Never
The grid squares you covered Yes If shared to friends If shared to that group If shared publicly
Distance, duration, date and time Yes If shared to friends If shared to that group If shared publicly
What your prayer notes say Yes If shared to friends If shared to that group If shared publicly
Where and when you made each prayer note On your phone only Never Never Never
Display name, handle, photo Yes Yes Yes Yes
Coverage totals for an area Yes Yes Yes Yes

People in a group can see who else is in it, and each member’s role.

A walk posted as a group. A group’s admins can post one of their walks as the group. It is still their walk, seen by exactly the audience they chose for it, and it always says who walked: the feed shows the group’s name and logo, with “Walked by” and the admin’s name beneath. It can only be done for a walk shared to that group or to everyone, and the group’s name comes off it if the admin stops being one.

Planned walks are seen by the group they belong to and nobody else: what the walk is, when, where to meet, who planned it, and who has said they are coming. If you leave the group, you drop off every “coming” list in it.

A walk you count toward a planned walk is still seen by exactly the audience you chose for it. People in that group who can see the walk also see which planned walk it counted toward; anyone else who can see it is not told. The planned walk’s totals — how many walked, how far together, how much ground — and its combined map are added up for each reader from only the walks that reader can already see, so a walk you kept private counts in your own view of the totals and nobody else’s. The combined map is grid squares, like every other map in ardeo, with no routes and no start points.

What sharing a walk actually reveals

A shared walk travels as the list of 65-metre squares it passed through. That is coarser than a route line — it does not show which side of a street you took, or where you doubled back, or how long you stood still — but it is still a record of where you were and when, with your name on it, for whoever you shared it with.

It is not trimmed at the ends. If a walk started at your front door, the square containing your front door is in that list. The Hide the start and end of my walks setting trims route lines, and no route line is uploaded, so today that setting does not change what a shared walk reveals. Until it does, treat sharing a walk that starts at home as telling that audience roughly where you live.

Keeping a walk private avoids this entirely: a private walk is visible to nobody but you.

The coverage map

The coverage map counts every walk, private ones included. That is the point of it — the ground that was prayed over, not the people who covered it.

What makes that safe is what the coverage figures do not contain: no account, no walk, and no time finer than a calendar day. A square reports how many distinct walker-days touched it and the most recent date. Two people on one street on one day is 2; one person walking it three times in a day is 1. There is no way to join two squares back into a journey.

There is no administrator view

No report exists, in the app or internally, that shows which member of a church walked where. There is no such report because there is no route to build one from. Group reporting is participation counts and coverage totals.

We can technically read the database, as whoever runs a service can. We look at individual accounts only to answer a request you make, to fix a fault, or when the law requires it.


Finding people, and being found

Signed-in walkers can search for people by handle only, three characters minimum. Display names are not searchable, so finding someone means already knowing their handle. Groups, by contrast, can be found by name. Your display name, handle and photo are visible to anyone signed in who finds you.

Friend requests have to be accepted. A pending request grants nothing.

Once you are friends, your friends can learn which groups you are in. The app suggests groups to each walker by naming friends of theirs who are already in them — “Ana is in this group” — so a friend may see a group of yours suggested to them with your name beside it.

People you may know

Before you search, the app suggests walkers you might know: friends of your friends, and people in your groups. Each suggestion says why, by naming up to two of your own friends or groups — “Friends with Ana”, “In Hope Church with you”.

This works the other way too, and it is worth knowing what it reveals. If you are friends with Ana, Ana’s other friends may see you suggested to them as “Friends with Ana” — so being someone’s friend lets their other friends learn, one suggestion at a time, that the two of you know each other. It never shows anyone a friend list: a suggestion names only the viewer’s own friends, at most two of them, and a walker is shown at most twenty suggestions. Suggesting people in your groups reveals nothing new, since members of a group can already see who else is in it.

Nobody is suggested to you who already has a friend request with you in either direction, who has blocked you or whom you have blocked, or whose account has been deleted. To stop appearing in a particular person’s suggestions, block them.

Blocking and reporting

You can block any walker. A block works in both directions: it ends any friendship or friend request between you, hides each of your walks from the other at every sharing setting, public included, and keeps each of you out of the other’s search results and suggestions. The walker you block is not told.

You can report a walker, a walk, a group or a planned walk. A report records who sent it, what it is about, the reason you chose and anything you write. It is emailed to us at hello@ardeo.nz, through Resend, so that we can review it. Nobody else can read a report — not the person or group reported, and not you once it is sent — so the walker you report cannot find out it was you. If you delete your account, reports you sent are kept, no longer linked to you, because they still need answering. Reports other walkers made about you, or about your walks, are kept after you delete your account too, for the same reason.

Photos you upload

A profile photo, and a group’s logo or cover picture, are re-encoded by our server before they are stored: a profile photo or logo as a 512-pixel square, a cover at 1600 × 900. Rebuilding the image from its pixels discards every piece of embedded metadata, including the GPS coordinates a phone camera writes into a photo. The file you uploaded is never stored, and there is no path by which an unstripped image can reach our storage.


Who else is involved

Service What it does for ardeo What it sees
Supabase (Sydney, Australia) Database, sign-in and photo storage Everything described above that is uploaded
Resend (United States) Sends sign-in emails, and sends us each report Your email address and the sign-in message; for a report, what it says and your handle
Apple and Google App stores, and sign-in if you use them Your account with them, and that you use ardeo
LINZ Basemaps, run by Toitū Te Whenua Land Information New Zealand Map imagery Which areas you look at on the map, and your IP address. Never your walks.
Expo (United States) Delivers app updates Your phone’s platform, app version and IP address when it checks for an update, and a random identifier the app creates for this install so updates can be rolled out in stages. It is not tied to your account
GitHub (United States) Hosts this website, including the page a sign-in link opens Your IP address when you visit. The sign-in code never reaches it: it travels in the part of the link a browser does not send.
Cloudflare (United States) Runs the ardeo.nz domain and forwards email sent to it Messages you send to an @ardeo.nz address, on their way to us
FormSubmit, run by Devro LABS (Sri Lanka) Delivers the beta sign-up form on this website to us by email The name and email address you enter, and your IP address

Email you send us arrives in a Google Gmail inbox that Plugged Worship uses.

We do not use advertising networks, analytics SDKs, or third-party trackers.


Donations

ardeo is free to use. Its running costs — servers, email, and the App Store and Google Play fees — are covered by donations, made by bank transfer to the account shown on ardeo.nz/donate. Donating is entirely separate from the app: it has nothing to do with your ardeo account, and giving or not giving changes nothing about what you can do in the app.

Who receives it. The account belongs to Sooyong Kim, who runs ardeo, and donations are put towards its running costs.

What we see. Only what any bank transfer shows the person receiving it: the name on the paying account, the amount, the date, and whatever you put in the reference and particulars fields. We never see your card or login details, and there is no donation form on the website collecting anything from you.

We use those details only to keep a record of donations. We do not add donors to a mailing list, link a donation to an ardeo account, or share donor details with anyone. If you would rather not be identified, use a reference that does not name you — though your bank will still show your account name.

ardeo is not a registered charity, so donations are not tax-deductible and we cannot issue donation receipts for a tax credit.


Joining the beta

While ardeo waits for App Store and Google Play review, you can ask to test it early using the form on ardeo.nz. The form asks for your name and email address, and nothing else.

The form is delivered by FormSubmit, a service run by Devro LABS in Sri Lanka, which passes your name and email to us as an email to hello@ardeo.nz. FormSubmit sees what you typed and your IP address in order to send it.

We use your name and email only to send you a beta invite — through Apple’s TestFlight or Google Play’s testing programme, which means giving your email address to Apple or Google for that purpose. We do not add you to a mailing list or use your details for anything else. Asking to join the beta does not create an ardeo account.

We delete beta requests once ardeo is listed in the stores. To have yours removed sooner, email privacy@ardeo.nz.


Keeping and deleting

Walks are kept until you delete them or delete your account.

To delete a walk, open it from your profile or your walk list and choose Delete walk. It is removed from our database straight away — its statistics, its notes and its grid squares with it — and from every feed and planned walk it reached, then from your phone. A walk that has reached our database can only be deleted while your phone is online: deleting it from the phone alone would let it come back the next time you sign in. Unlike deleting your account, deleting a walk does take its coverage back out of the totals, because a single walk is usually deleted for having counted when it should not have.

To delete your account, open Settings → Delete account in the app, or see our deletion page if you no longer have the app. Deleting in the app takes effect straight away: you are signed out, and your profile disappears from search, from your friends and from your groups at once. Everything else is removed from our database within 30 days.

Deleting removes your profile, your photo, your walks and their statistics, your notes, your grid squares, the walks you planned for a group and your answers to say you are coming. Planned walks and answers are hidden from everyone the moment you delete. A group you own passes straight away to the admin who has been in it longest. If it has no admin, the group — and everyone’s membership in it — is deleted along with your account.

The coverage totals you contributed are not reversed — a coverage count records that an area was prayed over on a given day. It has no person attached to it and cannot be traced back to you, so those counts stay. Other people’s records of their own neighbourhoods are built from the same totals, so removing yours would corrupt theirs.

Reports about you are kept. If other walkers reported you, or a walk or planned walk of yours, those reports stay after your account is gone: the reason they chose, what they wrote, and the id of what they reported, which leads to nothing once your account is removed. Each report was also emailed to us when it was made, naming you by the display name and handle you had then, and those emails stay in our inbox.

Your address is held until removal completes. After you delete in the app, the address you signed in with can’t be used to sign in to ardeo until removal completes: a sign-in link sent to it is refused, so it can’t make a new account in that time either. Once removal completes, the address is free to make a new account.

Copies outside the live database do not disappear the same moment. Our providers’ service logs, which can include your email address and IP address, are kept by those providers for up to 30 days. Supabase’s own backups roll over on its schedule. After those periods, no copy that identifies you remains, apart from the reports above.

Deleting in the app also clears your walks, routes included, off that phone. Otherwise, data held only on your own phone goes when you delete the app, or when a different account signs in to ardeo on it. We cannot recover it for you.


Your rights

Under the Privacy Act 2020 you can:

Email privacy@ardeo.nz. We will answer within 20 working days, as the Act requires, and tell you if we need longer and why. We may need to confirm the request comes from you before we act on it.


If something goes wrong

If a privacy breach involving your information happens and is likely to cause serious harm, we will tell you and the Privacy Commissioner as soon as we practicably can, as the Privacy Act requires, and say what happened and what you can do.


Children

ardeo is not directed at children under 13 and we do not knowingly collect their information. If you believe a child under 13 has an account, email privacy@ardeo.nz and we will delete it.


Changes

When this policy changes, we update this page and the date at the top. If a change affects what we do with information you have already given us, we will tell you in the app or by email before it takes effect.

What changed on 27 September 2026

What changed on 26 September 2026

What changed on 24 September 2026

What changed on 23 September 2026

Account deletion moved from an email-only request to in-app self-service, with email kept as a fallback for a lost phone or lost access to the address you signed in with. Deleting in the app is immediate — you are signed out right away, and removal from our servers completes within 30 days, rather than the 7-day human confirmation this page used to describe.

What changed on 18 September 2026

The app changed a great deal after the first version of this policy was written on 26 August, and several things it said are no longer true. Rather than edit them away quietly:


Contact

Privacy questions and requests: privacy@ardeo.nz Everything else: hello@ardeo.nz