Your trip.
Your people.
Tales Ahead is an iPhone and iPad bingo app in development. You can use local boards on your device and join private online groups without an account. This page covers the current app, group service and website, optional preview measurement and support chat.
Who runs Tales Ahead?
Arne Kellmann, Odenwaldstraße 134L, 64372 Ober-Ramstadt, Germany. For privacy, support or content concerns, email contact@arnekellmann.de. Operator details.
Local boards
Boards you keep local stay in the app's storage on your device. The app does not send those boards to our service. Your device's backups may include app data according to your Apple backup settings. Exporting a board sends a file only to the destination you choose using the iOS share sheet; that destination's privacy practices apply.
Online groups
When you create or join an online group, the service stores the group title, nine event descriptions, an optional nickname, randomly generated group and member identifiers, each member's marked cells, board revision and expiry time. The other members of your group can see the title, events, nicknames and progress, subject to their own blocking choices. The service also records which member last changed each title or event, and which members you have blocked, so it can hide their content from your view. Every member can edit the common list; this resets everyone's marks.
Blocking hides that member's nickname and progress from your roster and hides title or event text last changed by them. It does not remove their access or stop them seeing the group. You can unblock or leave the group. Block choices and field authorship are deleted with the group.
A secret membership token identifies your installation without an account or password. The app keeps it locally; the server stores a one-way hash. Invite codes are also stored as hashes. Anyone holding a current invite can join, so share it only with people you intend to invite. Invite links put the code after #, which browsers do not send as part of the website request.
Storage, deletion and expiry
The group service runs on Cloudflare Workers and D1. Groups become inaccessible after 30 days without activity; a daily cleanup removes the expired group and memberships, normally within a further 24 hours. The host can delete a group sooner. Leaving or being removed erases your nickname and marks from that membership and revokes access; a token hash and request fingerprint remain until group deletion or expiry to prevent an old request from restoring your membership.
Deleting the app removes its local data but does not itself delete a group on the server. Leave or delete the group in the app first. Data may remain temporarily in Cloudflare's provider-managed recovery systems under its applicable retention rules; we do not promise immediate erasure from those systems.
Abuse reports and limits
If you submit a report, we store the reason you enter, group identifier, reporting member identifier and submission time for up to 31 days, even if the group is deleted; a handled report may be deleted sooner. Do not include unnecessary sensitive information. Reports are accessible to the operator for review; submitting one does not automatically remove content.
To reduce abuse, the service temporarily stores request counters using one-way hashes of the network address and day, or of the membership token. We do not store raw network addresses in the application database. Counters expire and are removed by daily cleanup. The hosting provider still processes network addresses and request metadata to deliver and secure the service.
This website
The website offers optional preview analytics and feedback with separate choices. We use no advertising, tracking cookies or external fonts. The optional support chat described below connects only when you open it. Cloudflare necessarily processes your IP address and normal request metadata when serving the website. Application request logging and log exports are disabled. Cloudflare Traces samples 2% of requests to this website and service to find faults. A trace contains technical metadata such as the URL, time, status and duration, and is kept for 7 days. We process it under Article 6(1)(f) GDPR. This does not prevent Cloudflare from handling operational or security data under its own policies. Cloudflare's privacy policy.
Optional preview analytics and feedback
You choose analytics and feedback separately in Preview privacy settings. Both start off. The preview and Support work without either choice. We store your choices in local storage to remember and honour them. Do Not Track and Global Privacy Control keep both purposes off. The private invite page does not load measurement.
If you accept analytics, the public homepage sends only preview views, the first marked square and the first bingo to PostHog Inc. with EU hosting. Each event includes its time, a Tales Ahead site label, a production or test label, and a randomly generated browser identifier. We give that identifier a fixed 30-day expiry and rotate it on its next use after expiry. Your browser can retain the expired local storage entry until then or until you clear website data. It lets us measure returning browsers on this website, not people across devices. We use a separate identifier for QA tests. We do not send prediction text, private group content, invite codes, membership tokens, page addresses, query strings or referrers. We do not enable session recordings, automatic click capture or person profiles.
If you accept feedback, the website checks for its active, one-question PostHog survey after your first real preview bingo. It sends survey display, dismissal and completion events; a completed response contains only your choice of Yes, Partly or No and survey/question/submission identifiers. Feedback alone uses a random identifier stored for this tab. If you also accept analytics, feedback uses the consented browser identifier. A timestamp in local storage prevents another question for seven days. Tab storage limits and deduplicates events, with at most 20 sends per tab per UTC day. A new day permits current preview use to count again. PostHog also receives technical connection data, including your IP address; we disable automatic geolocation enrichment.
PostHog is a US company. Its access or subprocessors can involve transfers outside the EEA under the safeguards in its processing agreement. We use a shared project for our websites and separate Tales Ahead events by site. We process optional analytics and feedback under Article 6(1)(a) GDPR and browser storage for these purposes under section 25(1) TDDDG. You can withdraw either choice in Preview privacy settings. Withdrawal stops future collection, aborts pending requests and removes local identifiers and storage used only for the withdrawn purpose across open tabs. Expiry or withdrawal does not erase events or responses that PostHog already received. PostHog’s retention and query windows govern those records; contact the operator for access or erasure. PostHog event retention · PostHog privacy policy · PostHog processing terms.
Optional support chat
Opening support chat connects a separate, clean support page to PostHog Inc. with EU hosting. PostHog is a US company; access by it or its subprocessors can involve transfers outside the EEA under the safeguards in its processing agreement. We use our existing shared support inbox for our websites; the support page address identifies Tales Ahead. PostHog receives your messages, contact details you choose to provide, and technical connection data including your IP address. We do not automatically send group content, invite codes, membership tokens or the address of the page where you opened chat. No analytics events, session recordings or account identification are enabled for this chat.
PostHog stores a browser chat identifier, ticket state and any contact details you enter in local storage so you can return to a conversation. These remain until you clear website data. The chat works without analytics consent. We process contractual support under Article 6(1)(b) GDPR and other enquiries under Article 6(1)(f) GDPR, with our legitimate interest in answering requested support. Browser storage is limited to providing the chat you explicitly request under section 25(2)(2) TDDDG. We delete correspondence when it is no longer needed unless legal duties or open claims require retention. Do not send private group exports, invite codes, membership tokens or passwords. You can instead email contact@arnekellmann.de. PostHog privacy policy · PostHog processing terms.
What the app does not request
No contact, location, camera, microphone or photo-library permissions are needed. There are no third-party app libraries, advertising identifiers, behavioral analytics or third-party login providers. Online group data is still collected as described above; “no account” does not mean “no data.”
Your choices
Use local boards if you do not want to send board content to our service. Use a nickname that does not identify you. You can leave a group, ask the host to remove its content, or contact us about access, correction or deletion. Include the group identifier if available, but never send your membership token or invite code in a support message.
We process online group data to provide the service you request, and limited abuse-prevention data to protect that service. Your applicable data-protection rights may include access, correction, erasure, restriction, portability, objection and a complaint to a supervisory authority, for example the Hessian Commissioner for Data Protection and Freedom of Information (HBDI), Wiesbaden. You can withdraw any consent at any time with effect for the future. The service is not meant for children under 16 without a parent's permission. Email the operator to make a request.
Datenschutzerklärung (Deutsch) · Impressum · Get help · Back to Tales Ahead