Beta policy. Ataleir is in free public beta. This policy describes the beta build and will be updated as the app changes — materially, when hint requests move to a paid AI tier. The “last updated” date above changes with it.
What Ataleir is
Ataleir is a Windows desktop overlay that gives spoiler-free hints for story and puzzle games. You select and lock one game window. When you press the hotkey, Ataleir screenshots only that window and asks an AI model for a single spoiler-safe nudge.
Nothing is captured between hotkey presses. There is no background recording, no timer, and no always-on capture. If you never press the hotkey, no image is ever taken.
What we collect, and why
Account and sign-in
- You sign in with Google through Supabase (OAuth, PKCE flow). Supabase stores your account record: email address and Google identity.
- Sign-in tokens and — for source builds — your own Gemini API key are stored locally in Windows Credential Manager. Not in files, and not on our servers.
Screenshots (transient — sent to the model, never stored)
- On hotkey press, Ataleir captures the locked game window only and sends the compressed image to the Google Gemini API to generate the hint.
- Ataleir does not store screenshots — not on disk, not in Supabase. Once the hint is generated, the image is gone from the app.
- The one exception is an opt-in QA diagnostic you enable yourself on your own machine (off by default, self-disables after 24 hours). It saves capture frames to a local folder so you can inspect exactly what the app sees. Those files stay on your PC and are never uploaded.
Beta AI processing terms — please read. During the beta, hints run on Google's free Gemini API tier. Under Google's free-tier terms, content you submit (including game screenshots and hint text) may be used by Google to improve its products, which can include human review. Do not trigger hints on anything you would not want reviewed. When the beta moves to Google's paid tier, that content use no longer applies and this policy will be updated.
Voice (optional, off by default)
- If you enable voice input, audio is transcribed locally on your machine by bundled whisper.cpp. Audio never leaves your machine.
- You review and confirm the transcript before anything is sent. Only the confirmed transcript text (max 500 characters) goes to the model as extra context.
Session memory
- To keep hints consistent within a play session, Ataleir stores compact text session memory (scene summary, recent hints, current objective) in the Supabase table
game_session_memory.
- Rows expire after 24 hours and are protected by row-level security, so only your account can read your rows. You can clear session memory anytime from the Control Panel.
Hint feedback (only if you rate a hint)
- If you press yes or no on a hint, Ataleir stores that rating in the Supabase table
hint_feedback, together with the game, the model's own confidence for that hint, the hint text, and the same compact scene summary already used for session memory.
- Nothing is recorded unless you press one of those buttons. No screenshot is stored, and there is no free-text field.
- These rows are kept (they are not on the 24-hour session-memory timer) so recurring failures can be found and fixed. They are protected by row-level security, and they are removed when you delete your account or request deletion.
Usage counts
- Ataleir records daily hint counts per account in the Supabase table
hint_usage, and keeps local call/token totals in a local file for display and limits.
- Hint requests are routed through a Supabase Edge Function proxy that holds the API key server-side. That proxy keeps a per-user daily usage ledger — user ID, date, call and token counts — for rate limiting. This ledger is personal data tied to your account and is covered by the retention and deletion sections below.
Local files on your PC
settings.json (preferences), usage.json (local usage totals), and redacted diagnostic logs under %APPDATA%\Ataleir. Logs are local-only and redact window titles, emails, tokens, transcripts, and screenshot data.
What we do NOT do
- We never capture your desktop, other monitors, or other apps. Capture works only on the game window you explicitly locked. Browsers, chat apps, and other private apps are blocked from selection, and if validation fails, capture fails closed rather than falling back to something broader.
- No remote telemetry or analytics. Diagnostics are redacted, local-only files on your PC.
- We do not sell or share your data for advertising.
- We do not store your screenshots or your voice audio.
Third parties
- Google Gemini API — receives the game-window screenshot, game context, session memory text, and (if used) your confirmed voice transcript, to generate hints. Google's API terms govern that processing; on the current free tier this includes Google's right to use submitted content for product improvement (see the beta note above).
- Supabase — hosts authentication (your Google-linked account), session memory, and usage counts.
- GitHub — beta updates are downloaded from public release assets on GitHub. Update checks contact GitHub.
Retention
- Session memory: expires after 24 hours (reads filter expired rows); expired rows are physically removed by periodic cleanup.
- Usage counts / usage ledger: retained for 90 days, then deleted or aggregated.
- Hint feedback (only if you rated a hint): retained until you delete your account or request deletion.
- Account record: kept until you ask us to delete it, or the beta ends.
- Local files and Credential Manager entries: stay on your PC until you uninstall and delete them.
Your choices and deletion
- Voice input is opt-in and off by default.
- You can clear session memory from the Control Panel at any time.
- To delete your data — local files, credentials, and everything server-side — see the deletion guide in the project repository, or contact us using the link below. We will delete your Supabase rows and your account. You can also request an export of the data we hold about you.
Contact
Privacy questions, data deletion, and export requests: open an issue titled “privacy request” on the project repository. Do not post account details in a public issue — a maintainer will move it to a private channel. A dedicated support address replaces this when the project domain goes live.
Changes
This is a beta policy and will change — in particular when hint requests move to a paid AI tier. Beta testers are notified of material changes through the in-app beta channel status message, and the “last updated” date above is bumped.