WordSeams Privacy Policy
Last updated: June 2026
This Privacy Policy explains how WordSeams handles personal data.
WordSeams is operated by Edmund Delaney trading as Quiet Logic. In this Privacy Policy, “WordSeams”, “Quiet Logic”, “we”, “us” and “our” mean Edmund Delaney trading as Quiet Logic.
You can contact us at:
- Privacy and data-rights questions: [email protected]
- Support and Terms questions: [email protected]
- App/game feedback: [email protected]
1. Scope of this Privacy Policy
This Privacy Policy applies to:
- the WordSeams website;
- the WordSeams launch list;
- support, feedback and data-request communications;
- the WordSeams mobile app;
- related WordSeams services, including backend services, Daily submissions, display names, leaderboards, diagnostics and analytics where available.
WordSeams is a mobile word puzzle game. The WordSeams website is used to introduce the game, collect launch interest, and provide legal, support, feedback and data-request information.
Some features described in this Privacy Policy may apply only in beta, testing, staging, limited-release or public-release versions of WordSeams.
2. Who controls your personal data
For the purposes of UK data protection law, Edmund Delaney trading as Quiet Logic is the controller of personal data processed in connection with WordSeams, unless this Privacy Policy says otherwise.
We use service providers to help operate WordSeams. These providers process data on our behalf or under their own terms, depending on the service.
3. Summary
Depending on how you use WordSeams, we may process:
- your email address if you join the website launch list;
- messages and contact details if you contact support, privacy or feedback addresses;
- technical website and hosting logs;
- anonymous or pseudonymous app player identifiers;
- optional display names;
- gameplay submissions, scores, streaks, results, leaderboard entries and Daily Challenge data;
- Daily submission/replay evidence, including submitted words and turn/path data;
- local app data stored on your device;
- app version, build, device and diagnostic data needed to operate, secure and improve the service;
- optional product analytics data if you consent and analytics are enabled.
The app uses an anonymous-first model. It does not currently use email/password app accounts. Display names are presentation names for gameplay and leaderboard display. They are not verified real identities.
The game does not currently include chat, direct messaging, profile photos, voice or video, contacts or social graph features, or user media upload features.
The app does not currently use advertising IDs, ad tracking, an active ad SDK, location access, camera access, microphone access, contacts access, photo library access, payment data, health data, clipboard reads, real names or in-app email collection.
4. Website launch list
You can join the WordSeams launch list by providing your email address through the website form.
The launch list is used for:
- WordSeams launch updates;
- early access updates;
- product updates;
- release news.
We currently collect email address only. We do not collect your name by default for the launch list.
We use EmailOctopus to manage the launch list and send emails.
The launch list uses single opt-in. You can unsubscribe at any time using the unsubscribe link in our emails.
Contacting support, privacy or feedback does not automatically add you to the launch list. We do not add support or feedback contacts to unrelated marketing lists unless they separately sign up.
Launch-list emails are not app accounts. Unsubscribing from launch-list emails does not delete app gameplay or backend data, and deleting app data does not unsubscribe you from launch-list emails.
5. Support, feedback and data requests
If you contact us, we may process the information you provide, such as:
- your email address;
- your name, if you choose to provide it;
- the contents of your message;
- screenshots or diagnostic information you choose to provide;
- support details copied from the app;
- information needed to handle a privacy or data-rights request;
- information needed to identify app/backend data, such as an in-app player/support ID, display name, Daily or Season participation details, device/build details or a future support code if implemented.
The app may include a support-info copy feature, for example by tapping app version information in Settings. This may copy app/support details such as version, build, channel and support/backend/player identifier where available. This is intended to help you contact support or make a data request.
We use support, feedback and data-request information to respond to your request, investigate issues, improve WordSeams, handle legal or privacy obligations, and maintain appropriate records.
6. Website hosting, security and logs
The WordSeams website is hosted using Cloudflare Pages.
Cloudflare and related infrastructure services may process standard technical data as part of hosting, security, performance and delivery. This may include:
- IP address;
- request date and time;
- requested page or file;
- browser or user-agent information;
- device or operating-system information;
- referrer information;
- security, error or diagnostic log data.
We use this information to operate the website, keep it secure, diagnose issues, prevent abuse and understand service reliability. We do not use this website log data to build advertising profiles.
7. Cookies and similar technologies
The WordSeams website is intended to use only strictly necessary functionality.
The website is not intended to use:
- Google Analytics;
- Meta Pixel;
- TikTok Pixel;
- advertising pixels;
- heatmaps;
- session recording;
- embedded social widgets;
- cookie-based analytics;
- non-essential tracking cookies.
A cookie banner is not currently used because the website is intended not to set non-essential cookies or similar tracking technologies.
We may use strictly necessary cookies, local storage or similar technologies if they are required for essential functions such as site security, form submission, service delivery, fraud prevention or load balancing.
If we introduce privacy-friendly or cookieless analytics later, we will update this Privacy Policy as appropriate. If we introduce non-essential cookies or similar tracking technologies, we will add an appropriate consent mechanism before those technologies load where required.
8. App player identity
WordSeams uses an anonymous-first app/backend model rather than conventional email/password app accounts.
This may include:
- backend anonymous player ID;
- anonymous authentication/session data;
- local installation/profile data;
- local identity state;
- optional display name;
- app/session identifiers needed to operate the service.
These identifiers help the app provide gameplay, Daily submissions, leaderboard features, streaks, support and abuse-prevention functionality.
Because app identity is anonymous, we may not be able to find backend game data using your email address. If you ask us to delete or anonymise backend game data, we may need information from the app, such as an in-app player/support ID, display name, Daily or Season participation details, device/build details, or a future support code if implemented.
9. Display names and leaderboard data
If you choose a display name or participate in leaderboard features, we may process and display information such as:
- display name;
- rank;
- score;
- streak;
- game mode;
- Daily or Season details;
- best word;
- longest word;
- result statistics;
- games played;
- other gameplay or leaderboard attributes.
Display names and leaderboard data may be visible to other players in app leaderboard, result or sharing surfaces.
Display names are not verified real identities. You should not use a display name that includes personal information you do not want other people to see.
We may moderate, remove, edit, replace or restrict display names and leaderboard entries to prevent abuse, offensive names, cheating, impersonation, technical manipulation or other misuse.
Some leaderboard service responses may include backend or player identifiers needed by the app to display, validate or manage leaderboard state. These identifiers are not intended to be real-world identities.
10. Daily submissions and gameplay/replay evidence
WordSeams may process Daily submissions and gameplay/replay evidence to validate results, support leaderboards, preserve fairness, resolve disputes, rebuild leaderboard state, prevent abuse and diagnose gameplay issues.
Daily submissions sent to the backend may include:
- backend player ID;
- run ID;
- Daily date;
- Daily content ID;
- board/config/rules/reference identifiers;
- board hash;
- dictionary or profanity/reference versions;
- exact committed words;
- tile/path coordinates;
- swap actions;
- turn history;
- scores and statistics;
- best word;
- longest word;
- turns used and turns total;
- completion timestamp;
- app version and build version;
- submission/validation status;
- leaderboard materialisation state;
- streak credits and streak summaries;
- result diagnostics/replay evidence.
This data is used by the first-party WordSeams backend. It is not intended to be sent to Sentry, PostHog, Better Stack or operational monitoring logs.
Public static health, config, reference and Daily payload endpoints contain game/static metadata, not player data.
Authenticated leaderboard endpoints may return display names, ranks, scores, performance data, player identifiers needed by the app, best words and longest words.
11. Local device data
WordSeams stores some data locally on your device. This may include:
- local save data and app preferences;
- anonymous/local installation profile data;
- anonymous auth/session data;
- backend player ID and display name where relevant;
- privacy acceptance state;
- Analytics consent preference;
- gameplay/session state;
- Daily state and results;
- scores, streaks and result data;
- pending/retry submission data;
- leaderboard responses or cache;
- generated share text, cards or images;
- support information copied by you.
Local-only data is controlled by your device. You can delete local data by deleting the app or clearing app data through your device settings. If an in-app reset local data control exists in your version of the app, you may also be able to use that control.
Deleting the app or clearing local data does not automatically delete backend leaderboard, Daily submission, support, privacy-request or launch-list records.
We cannot remotely delete data that exists only on your device.
12. Auth/session storage
In production mobile builds, WordSeams is designed to store mobile auth/session data using platform-backed secure storage where available:
- iOS uses Keychain-backed secure storage;
- Android uses Keystore-backed encrypted storage.
If secure storage is unavailable on a production mobile device, the app is designed not to persist the session in plaintext and may keep the session in memory only.
You should keep your device secure and use your device’s screen lock and security features.
13. Pending submissions and offline play
Some WordSeams features may work offline or during service outages.
If you complete a Daily challenge while offline or while backend services are unavailable, the app may store a pending submission locally and retry later.
Pending submissions may include the full submission payload needed to validate the result, including submitted words and turn/path data. They are stored locally until submitted, resolved, terminally failed, manually cleared, overwritten or removed by deleting app data.
A pending submission does not guarantee leaderboard acceptance. Submissions may be subject to validation rules and submission windows.
14. Crash and error diagnostics: Sentry
WordSeams uses Sentry in the Unity frontend for essential crash and error diagnostics where Sentry is configured and enabled for the relevant build or environment.
Sentry helps us understand crashes and errors so we can improve reliability and fix issues.
Sentry is separate from the optional Analytics consent toggle. Declining optional Analytics prevents PostHog product analytics sends, but does not necessarily disable essential crash/error diagnostics where they are enabled.
Sentry is configured so it should not receive:
- submitted words;
- boards or seeds;
- tile paths or turn histories;
- scores;
- leaderboard data;
- display names;
- player IDs;
- backend IDs;
- support IDs;
- email addresses;
- real names;
- screenshots;
- raw configuration files;
- tokens, keys or secrets;
- URLs with query strings.
Sentry user context/user.id is not used. Sentry log capture is disabled.
15. Optional product analytics: PostHog
WordSeams uses PostHog in the Unity frontend for optional product analytics only when all required gates allow it, including privacy acceptance, Analytics consent, feature/config gates and provider gates.
Declining Analytics prevents PostHog analytics sends.
PostHog is used to understand product usage at a high level and improve the game. It is not intended to receive raw gameplay submissions or replay evidence.
PostHog is configured for EU hosting.
PostHog is configured so that the following are disabled or not used:
- person profiles;
- identify calls;
- group calls;
- lifecycle autocapture;
- exception capture;
- session replay;
- feature-flag preload events;
- default person properties;
- log capture.
PostHog should not receive submitted words, raw boards, seeds, tile paths, turn histories, display names, player IDs, backend IDs, support IDs, emails, real names, screenshots, tokens, keys or raw configuration files.
Product analytics may include coarse app usage events, app/build information, feature usage status, consent status, coarse share status or similar product telemetry. Share telemetry is intended to record coarse status only, not raw share text, images or file paths.
16. Operational monitoring: Better Stack
WordSeams uses Better Stack for uptime, health and heartbeat monitoring.
Better Stack is used to monitor public health/static/config/reference endpoints and daily-generation heartbeat status. It should not receive player submissions, submitted words, boards, seeds, tile paths, turn histories, player IDs, display names or leaderboard content.
Operational monitoring helps us check whether services are available and whether scheduled or operational processes are working.
17. Native sharing and clipboard
WordSeams may allow you to create share text, result summaries or share-card images and share them through your device’s operating-system share sheet.
Sharing is user-initiated. You choose whether to share and which app or service to share with. Third-party apps or platforms you choose to share with are governed by their own terms and privacy policies.
Share content may include scores, streaks, best words, longest words, Daily/date/mode result copy and generated share-card images.
WordSeams telemetry is intended to record only coarse share status, not raw share text, share-card image content or destination app details.
The app may write support or share copy to your clipboard when you choose that action. The app is not intended to read clipboard text.
18. Data we do not currently collect in the app
Based on the current app implementation, WordSeams is not intended to collect:
- real names;
- email addresses in the app;
- phone numbers;
- postal addresses;
- precise location;
- approximate location;
- contacts;
- photos or videos from your library;
- camera images;
- microphone or audio recordings;
- voice or video chat;
- direct messages or chat content;
- profile photos;
- uploaded user media;
- payment card data;
- purchase data;
- health data;
- clipboard reads;
- advertising ID, IDFA or ATT data;
- native Apple or Google account identifiers;
- device unique IDs;
- social graph data;
- installed-app lists.
If this changes, we will update this Privacy Policy as appropriate.
19. Ads, Unity services, purchases and future features
No ads are currently active in WordSeams.
The current app is not intended to use an ad SDK, advertising ID, ad provider or ad tracking.
Unity submitAnalytics is disabled. Unity Analytics/services, Cloud Diagnostics, Ads, Purchasing and Crash Report API are disabled.
WordSeams may later add or expand features such as:
- online two-player features;
- telemetry or crash reporting changes;
- ads;
- app-store purchases or subscriptions;
- additional leaderboard or social features.
If these features introduce material new personal-data uses, we will update this Privacy Policy before or when those features are introduced.
20. App stores and platform providers
If you download WordSeams through Apple App Store, TestFlight, Google Play, Play Internal Testing or another app platform, that platform may process personal data under its own privacy policy and account terms.
We do not control how Apple, Google or other platform providers process data in connection with your app-store account, device, downloads, purchases, refunds, reviews, platform analytics or app-store privacy labels.
21. How we use personal data
We use personal data for the following purposes:
- to operate the website;
- to manage the launch list;
- to send launch, early access, product and release updates;
- to respond to support, privacy and feedback messages;
- to provide and operate app features;
- to create and manage anonymous player identity;
- to validate gameplay submissions;
- to calculate scores, streaks, results and leaderboard entries;
- to store and assess Daily submission/replay evidence;
- to moderate display names and prevent abuse;
- to detect cheating, bugs, exploits, duplicate submissions and service interference;
- to preserve leaderboard and gameplay integrity;
- to maintain security and service reliability;
- to diagnose and fix technical issues;
- to monitor uptime and health status;
- to understand app usage where optional analytics consent is given;
- to comply with legal obligations;
- to establish, exercise or defend legal claims;
- to improve WordSeams.
22. Lawful bases
Where UK GDPR or similar laws apply, we rely on one or more lawful bases depending on the context:
- Consent: for launch-list email updates, optional PostHog product analytics, and any non-essential cookies or similar technologies if introduced.
- Contract: to provide app and service features you request, such as gameplay, Daily submissions, display names, leaderboards, streaks, support and app functionality.
- Legitimate interests: to operate, secure, improve and support WordSeams, provide essential diagnostics, prevent cheating and abuse, maintain leaderboard integrity, respond to feedback, monitor uptime, and keep appropriate service records.
- Legal obligation: to handle privacy rights, compliance records, lawful requests and other legal obligations.
- Legal claims: where processing is needed to establish, exercise or defend legal claims.
You can withdraw launch-list consent by unsubscribing.
You can decline optional Analytics in the app where the Analytics consent control is available.
23. When we share personal data
We may share personal data with service providers and platforms that help us operate WordSeams, including:
- Supabase for backend services, anonymous authentication, Edge Functions, database functionality and related logs;
- Cloudflare for website hosting, DNS, CDN, security, delivery and request metadata;
- Better Stack for uptime, health and heartbeat monitoring;
- GitHub Actions/artifacts for scheduled staging generation, evidence and build artifacts;
- EmailOctopus for website launch-list email management only;
- Sentry for frontend crash/error diagnostics where enabled;
- PostHog for optional frontend product analytics where consent and configuration gates allow;
- Apple and Google for app distribution, testing and platform services;
- professional advisers, regulators, authorities or other parties where required for legal, compliance, security or dispute purposes.
We do not sell launch-list email addresses.
We do not add support or feedback contacts to unrelated marketing lists unless they separately sign up.
We do not use current app data for third-party targeted advertising.
24. International transfers
WordSeams is intended for users in the UK, US and other English-speaking/global markets.
Our service providers may process data in countries outside your country of residence. Where required, we take steps designed to protect personal data, such as using appropriate contractual safeguards, provider terms, data processing agreements or other lawful transfer mechanisms.
25. Retention
We keep personal data only for as long as reasonably needed for the purposes described in this Privacy Policy, unless a longer period is required for legal, security, abuse-prevention, operational or dispute reasons.
Final retention periods remain subject to owner/legal review. Our current retention approach is:
- Anonymous player/auth data: retained while the player is active. We currently treat a player as inactive after around 24 months with no backend activity. After that, we may delete or anonymise backend player/auth linkage where technically feasible.
- Device auth/session tokens: remain on the device until expiry, logout/reset, app deletion, clearing app data, or a future account/data deletion process.
- Display names: retained while the player participates in leaderboards. Historical display-name records may be retained as needed for moderation, abuse prevention and leaderboard integrity.
- Display-name moderation records: typically retained for around 24 months, or longer where needed for abuse prevention, disputes, safety or legal reasons.
- Daily submissions and replay evidence: retained for the life of the relevant Daily or Season leaderboard plus an archive period, currently expected to be around 24 months.
- Leaderboard entries: retained while the leaderboard or season is published or archived. Where appropriate, entries may be anonymised rather than deleted to preserve leaderboard integrity.
- Local device saves and cache: retained on your device until you delete the app, clear app data, use any available reset control, or the app overwrites or cleans old local data.
- Pending submissions: retained locally until submitted, resolved, terminally failed, manually cleared, overwritten or removed by deleting app data.
- Support correspondence: typically retained for around 24 months after resolution, unless longer retention is needed for unresolved issues, legal claims, abuse, fraud, safety or disputes.
- Data request records: typically retained for around 6 years, limited to what is needed to show how the request was handled.
- Launch-list contacts: retained while subscribed. If you unsubscribe, we retain suppression or do-not-contact information as needed to avoid emailing you again.
- Consent evidence: retained while subscribed and for a reasonable period after unsubscribe, currently expected to be around 24 months unless a longer or shorter period is legally appropriate.
- Standard application and website logs: typically retained for around 30-90 days.
- Security, audit, admin-action, deployment and incident logs: typically retained for around 12-24 months, or longer if needed for investigation, security, legal claims or abuse prevention.
- Provider logs and staging evidence artifacts: retained according to provider settings and operational needs. These are intended to avoid raw gameplay content and direct player data. Some operational logs or artifacts may not be individually removable where they do not contain raw gameplay content or direct player data.
These periods may be refined over time as WordSeams moves through beta, closed testing and public release.
26. Deletion and anonymisation
You may request deletion or anonymisation of backend game data by contacting [email protected].
Because WordSeams uses anonymous player identifiers rather than email/password accounts, we may need information from the app to locate relevant backend data. This may include:
- in-app player/support ID;
- display name;
- approximate Daily or Season participation details;
- device/app build details;
- support code, if implemented later.
There is no in-app self-service backend deletion flow at the time of writing. There is also no public self-service backend deletion API.
Deletion/anonymisation requests are currently handled through a support/admin process. We have tooling and runbooks to help identify affected backend records, but a reviewed destructive deletion/anonymisation execution path is not yet fully automated.
Where we can identify the relevant backend data, we may take steps such as:
- deleting or anonymising anonymous backend player data;
- removing or anonymising player profile/display-name data;
- revoking, disabling or deleting backend auth identity where feasible;
- removing the display name from public leaderboards;
- replacing the display name with neutral text such as “Deleted player”;
- removing direct player linkage from leaderboard entries;
- deleting or anonymising Daily submissions and replay evidence where feasible.
Where leaderboard records, Daily submissions or replay evidence need to be retained for fairness, anti-cheat, dispute handling, rebuild support or historical integrity, we may anonymise them rather than deleting the entire score, entry or submission record.
Deleting the app or clearing app data removes local device data but does not automatically remove backend leaderboard, Daily submission, support, privacy-request or launch-list records.
Launch-list email data is handled separately. You can unsubscribe using the unsubscribe link in an email or contact [email protected] to request deletion or erasure where applicable.
We may retain limited records of privacy/data requests to show that we handled them properly.
27. Your rights
Depending on where you live, you may have rights over your personal data, such as the right to:
- access your personal data;
- correct inaccurate personal data;
- request deletion;
- request restriction of processing;
- object to processing;
- withdraw consent;
- request data portability;
- complain to a data protection authority.
To exercise privacy rights, contact [email protected].
If you are in the UK, you may also have the right to complain to the Information Commissioner’s Office.
We may need to verify your request and may need additional information to locate anonymous app/backend data.
28. Children
WordSeams may be available to a general audience, but it is not directed at children.
No age gate is currently implemented.
The app is designed as a calm word puzzle game. It does not currently include chat, direct messaging, profile photos, voice/video, contacts/social graph features or user media uploads. The main user-facing public identifier is the optional display name used for leaderboard and result features.
We use display-name rules, moderation and prohibited-word controls to reduce the risk of inappropriate names appearing in leaderboards. No moderation system is perfect.
We do not knowingly ask children to provide more personal data than is needed for the relevant feature.
The launch list is intended for people who can lawfully consent to receive product updates in their country. If you are under that age, please ask a parent or guardian before signing up.
If you are a parent or guardian and believe a child has provided personal data that should be deleted, contact [email protected].
29. Security
We use reasonable technical and organisational measures designed to protect personal data. These may include provider security controls, access restrictions, separation of staging and production environments, secure mobile auth storage, deployment controls, backup and restore processes, monitoring, audit practices, secrets management and incident response procedures.
We also aim to avoid sending raw gameplay content, direct player data, tokens, keys or secrets to diagnostics, analytics or monitoring providers where they are not needed.
No online service is completely secure. You should keep your device secure and avoid sharing display names, screenshots or support information that reveal personal information you do not want to make public.
30. Automated rules and moderation
WordSeams may use automated rules to validate gameplay submissions, detect duplicate submissions, apply scoring rules, apply display-name restrictions, identify technical issues or support anti-cheat and moderation processes.
These processes are used to operate the game and protect fairness and service integrity.
If you believe a leaderboard entry, submission status or display-name decision is wrong, contact [email protected].
31. Third-party links and social platforms
The WordSeams website may link to third-party platforms such as Instagram, TikTok, YouTube and Bluesky.
If you follow those links or interact with WordSeams on those platforms, the platform’s own privacy policy and terms apply. We do not control those platforms.
32. Changes to this Privacy Policy
We may update this Privacy Policy from time to time.
We will update the “Last updated” date when we make changes.
If we introduce material new data uses, such as advertising, ad tracking, online multiplayer, new account features, payment features, new analytics, or new crash/diagnostic providers, we will update this Privacy Policy as appropriate.
33. Contact
For privacy questions or data-rights requests, contact:
For support or Terms questions, contact:
For app/game feedback, contact: