small detours

Small Detours · Privacy Policy

Privacy Policy

What Small Detours keeps on your phone, what it sends to our server, and how long.

Last updated: 15 November 2026 · Applies to Small Detours for Android (package com.smalldetours), version 0.5.26 and the versions that follow until this page changes.

The short version

  • The app has no account, no ads, no analytics and no crash-reporting service.
  • Your moments, photos you add, paintings, walks, pins and exact location points stay on your phone unless you choose to share a piece of them.
  • If you use Together or Guess where, what you send is stored on our server for up to 30 days from the day it was created, then our server deletes it.
  • Notifications are optional. If you turn them on for a space, a Firebase Cloud Messaging token for your phone is stored on our server, encrypted. A notification never contains your words, photos, names or places.
  • If you buy Premium, Google Play takes the payment. The app sends the purchase token to our server so it can ask Google whether the purchase is still valid; the token is not stored.

1. Who we are

Small Detours is published on Google Play by WizPlayo, the developer name shown on the app's Google Play page. For any question about this policy or about your data, write to wizplayo.developer@gmail.com.

2. What stays on your phone

These are kept in the app's private storage on your phone and are not sent to us:

When you add a photo, the app uses Android's photo picker, so it receives only the pictures you choose, and keeps its own copy in its private storage.

The app turns Android's automatic cloud backup and phone-to-phone transfer off for its data.

3. Location

4. What our server receives

Our server receives data only when you use the features below. Everything is sent over HTTPS.

4.1 Together (a private space for two people)

When you create or join a space and send something, our server receives and stores: the display names you type for yourself and the other person (up to 40 characters each), the title and prompt of the space, the words and photo you send, and your messages (up to 400 characters each, up to 100 per space), with the time they were sent. Before a photo is sent, the phone decodes it, resizes it so its longest side is at most 1280 pixels, and saves it again as a JPEG that fits within a 700 KB limit.

These contents are stored in readable form on the server, not end-to-end encrypted. The server keeps only SHA-256 digests of the keys, never the keys. The invitation link carries its key after the #, a part that a browser does not send to a server. Anyone who has an unused invitation link can join, so send it privately.

While the app is open and you belong to shared spaces, it asks our server about each space about every 20 seconds to see whether something new has arrived.

4.2 Guess where (a cropped map piece with a clue)

If you share a map piece, our server receives and stores: the drawn lines; the pins (as positions inside the frame, with no latitude or longitude); for each pin, the title (up to 100 characters), note (up to 600) and image of the moment you attach; the clue (up to 140) and the answer (up to 160). The answer is held back from the guest until the sender reveals it.

4.3 Notifications for a space (optional)

If you turn notifications on for a space, the app asks Android for permission and then sends our server: the space (authorised with your key), a registration name the app makes up, your phone's Firebase Cloud Messaging registration token and the app's package name. Our server stores the token encrypted (AES-GCM, with a secret kept on the server) and uses it only to ask Google to wake your phone. The message sent through Google carries only a version number and a random reference; it asks Google to keep an undelivered message for up to 24 hours. The sentence you see ("Something new in a shared space.") is built on your phone.

Firebase Cloud Messaging also creates a Firebase installation ID on your phone and sends Google basic device and app information (for example the app version, Android version and device model) so that messages can be delivered. Google describes this at firebase.google.com/docs/android/play-data-disclosure. The app does not include Google Analytics or Firebase Analytics, and Firebase's automatic start is switched off: nothing is requested from Firebase until you turn notifications on.

4.4 Premium (optional)

Google Play handles the payment; we never see your card or your Google account details. To decide whether Premium is on, the app sends the purchase token that Google Play gave it, with the app's package name, to our server. Our server asks Google's Play Developer API whether the subscription is active and answers yes or no with the end date. The token is used to answer that request and is not stored by our server. The app does this when it starts, when you buy or restore, and again when the last check is more than 24 hours old.

4.5 Tester code (only if you have one)

If you type a tester code, the app sends it to our server to check it against a stored SHA-256 digest and to learn when the test period ends. The server keeps the digest and the start and end time of the period; it keeps no person, address or device identifier for this.

4.6 Technical information

Like any server, our server and Cloudflare receive the IP address and technical details of each request. Our code uses the address only to limit how many requests one address can make in a minute; that count is held in memory and is not written to storage. Our code writes no access log, and request logging (observability) is switched off on our server. Cloudflare runs the infrastructure and keeps its own records under its own policy, which we do not control.

5. Services we rely on

This page uses no cookies, no scripts, no analytics and no third-party requests.

6. Sharing

We do not sell your data and do not use it for advertising. We pass it on only: to the other person in a space, or to the guest of a map piece, because you sent it to them; to the services in section 5, which handle it on our behalf to run the app; and where the law requires.

7. How long things are kept, and deleting them

WhatWhereHow longHow it is deleted
Moments, photos, paintings, walks, pins, location points, draftsYour phoneUntil you delete them or uninstall the appIn the app: Delete page for one moment, Clear my pages for all moments, remove a pin, Start a fresh map for all paths and pins; or uninstall. Files you saved or shared outside the app are not touched
A Together space (names, title, words, photos, messages)Our serverUp to 30 days after the space was createdOur server deletes it automatically when the 30 days end. The person who created it can close it earlier in the app: it is then deleted for both people at once. Leaving a space removes it from your phone only; the copy on the server stays until it is closed or expires.
A Guess where pieceOur serverUp to 30 days after it was createdDeleted automatically at 30 days, or when the sender closes it
Notification registration (encrypted token, reference)Our serverUntil you turn notifications off for the space, leave it, or it is closed or expiresTurn notifications off for the space, or leave or close it: the app asks our server to remove the registration (if there is no connection it tries again later). It also goes when the space expires
Purchase tokenNot storedOnly while a request is being answeredNot applicable
Tester code checkOur serverUntil the test period endsOnly a digest of the code and the period's times are kept
Request-rate countsServer memory onlySeconds to minutesNot written to storage

There is no account, so we cannot look up content by your name or email address; a space or a map piece is identified only by its private link. Cloudflare and Google keep their own records as described in section 4.6 and in their policies.

8. How it is protected

These are the measures that exist today, not a promise that nothing can go wrong:

9. Children

Small Detours does not ask for your age. We do not knowingly collect personal information from children. If you think a child has put personal information into a shared space, write to wizplayo.developer@gmail.com with the link of the space (without the part after the #).

10. Your choices

11. Changes

If this policy changes, the "Last updated" date at the top changes with it. The current version is always at this address.

12. Contact

WizPlayo · wizplayo.developer@gmail.com