There is a specific awkwardness about building an app whose core action is taking a photograph.
A city scavenger hunt asks somebody to point a camera at a building, a street or a fountain. That is harmless. But the moment the camera is up, other people are in the frame. The person walking past with a coffee. The person on the bike. The dog.
And underneath every one of those photographs is a location, which is the other half of the question.
The questions we design against
When we worked out what the app should do with a photograph, we wrote down four questions.
Does the photograph need to leave the device? If the answer is no, it does not leave it. The check that matters is whether the photo is compared against something on the device or sent somewhere to be compared. Sending it is a decision with consequences; not sending it is the absence of one.
Does anything need to be kept after the check? There is a version of this product where there is a gallery of everything you have photographed, and a version where the photograph is used to unlock the next stop and then has no further purpose. The second version is harder to build and much easier to defend.
Is the location needed, or is the location incidental? Knowing roughly where somebody is is enough to generate a hunt. Knowing exactly where they are, continuously, is a different product with a different set of obligations.
What is the shortest path out? If somebody wants their data gone, how many emails and how many days does that take? A privacy policy that describes a process nobody has ever walked through is not a policy.
Plain language is the point
People do not read policies, and the ones who do read them are looking for two things: what do you collect, and what do you do with it.
So the policy is written in short sentences and it says what happens, in order, without hedging. It is here: pinghunt.com/privacy-policy.
And if you want everything associated with an account removed, that is a page of its own, not a paragraph to be found: pinghunt.com/delete-account.
Why write about this at all
Because a game that asks you to walk around a city holding up a phone has a particular responsibility, and because the answer is not a technical detail - it is a product decision that shows up in the interface, in the network traffic and in the store listing.
We have written up more of the design and the trade-offs, with screenshots, here: pinghunt.com/docs.
The general principle, if you are building something that takes photos in public: decide what the photograph is for before you decide where it goes, and write the deletion path before you need it.
Top comments (0)