Taplilt Privacy Policy

Taplilt Privacy and Data Handling

Implementation disclosure updated: 2026-10-20 App: Taplilt (com.servenzo.taplilt) Publisher/developer: Servenzo Privacy contact: [email protected] Public policy address: https://servenzo.com/apps/taplilt/privacy-policy

This disclosure describes the local Taplilt R1 source and the separate optional previous-demo platform controls. Cloud availability depends on the publisher’s configured deployment. A build without a backend URL works locally. No sign-in or upload is performed automatically.

Local information and use

Classic and practice rounds use a versioned app-local database for rules, a deterministic target seed and generator state, active target/presentation checkpoint, correct hits, wrong-tile taps, measured active time, interruption/recovery labels and completed result summaries. Device preferences include language, larger practice targets, interval, sound, haptics, countdown, motion and contrast. Legacy bestScore is retained as an unknown-rules summary, not manufactured into recorded rounds. Local recovery can retain malformed source and a last acknowledged checkpoint. Process recovery is covered and labelled recovered practice; time outside the process is not invented.

Core play is account-free and does not require a network connection. Optional Android feedback uses short generated sounds and system touch haptics with independent off-by-default controls; it does not record audio. Severe thermal callbacks request an immediate safe pause. Native behavior requires installed-device qualification.

An optional, explicit local performance capture records bounded Flutter frame durations and input-to-post-frame proxy timings for at most ten minutes. It does not record target positions, scores, raw touch coordinates, account identity or content, and it has no uploader. A capture summary is available for deliberate unencrypted export; it is not proof of physical input latency or representative-device performance. Content-free diagnostic support codes do not identify a player. Diagnostic collection defaults off and no product analytics uploader is included.

Optional account and snapshot sync

You may use the local demo without creating an account. If you choose sign-in, the configured identity provider processes authentication in your browser. The backend verifies a provider subject and app-specific access token, and stores a separate app account and workspace. Native session tokens use platform secure storage; the web session token is kept in memory. Connection drafts and revision metadata may be stored locally to preserve retries, without saving the access token in ordinary preferences.

Snapshot data eligible for your explicit upload: the previous demo bestScore field only. R1 typed rounds, checkpoints, settings, history, performance captures and recovery source never enter that compatibility snapshot. The scalar is not an authoritative competitive leaderboard.

You choose whether to upload the allowed local fields or replace them from cloud state. A conflict requires an explicit choice rather than silently overwriting newer work. Shared infrastructure does not give one app’s account access to another app’s private workspace. Operational requests necessarily reach the configured server/provider and can expose network information such as IP address and request timing to that infrastructure.

Other optional platform controls

Cloud file controls transfer only files you deliberately select, together with bounded filename/type/size, checksum and expiry metadata. These server-readable files are not end-to-end encrypted vault storage. Expiry and deletion block future authorized access before eventual physical cleanup; previously downloaded copies cannot be recalled.

Notification controls store the schedule, message and inbox record you submit. If push delivery is configured and you register a device, the service stores its app-scoped push token and sends the message through the configured push provider. Provider acceptance does not establish that the device displayed it. In-app inbox delivery and local phone reminder scheduling have different behavior.

Google Play billing controls, where configured, send the selected product and purchase token for server verification and store verification/entitlement status. Payment details are handled by Google Play rather than entered into this app. No paid entitlement is granted just because a device claims a purchase. Development adapters are identified as development features; they do not establish a paid purchase.

The app does not include advertising or product analytics in this implementation. Future ads, child profiles, additional SDK collection or other new processing need separate disclosure and review before being enabled.

Storage, retention and deletion

The versioned local database and previous demo preferences are not encrypted by an app-level data layer. Free JSON/CSV exports are also unencrypted. Active/recovery exports may reveal the deterministic future target sequence and private raw recovery source; the app asks you to acknowledge that before preparing them. Clipboard and document-provider copies have independent lifecycles. No R1 file import or encrypted-backup capability is claimed. Android automatic app backup is disabled to avoid restoring encrypted authentication tokens on another device; this also excludes other app-private data from that automatic backup mechanism. Device manufacturers or separately selected document providers can operate independent services.

Within the app, selected-result deletion and clear history leave the active checkpoint, settings and purchased entitlements intact; history clear also removes the incomparable legacy best. Clear active affects only its checkpoint. Clear all local play data additionally removes local legacy/recovery/quarantine data while retaining preferences, setup draft and purchases. These controls do not erase external exports, provider backups or cloud records.

You can remove app-local data with Android Settings > Apps > Taplilt > Storage > Clear storage (labels vary). Clearing local data or uninstalling does not by itself delete an optional cloud account, cancel a Google Play subscription or erase a file you exported.

Cloud account export/deletion are separate account controls and require recent sign-in. Account deletion applies to this app’s account and workspace, rather than silently deleting all Servenzo app accounts. It ends access and initiates scoped cleanup; a queued or partially completed cleanup is not a claim of immediate forensic erasure. Identity-provider accounts, Google Play purchase records, mandatory provider retention and independent external copies have separate controls. See the operator and hosting section of this policy for the current deployment and retention settings.

Device access

The app does not request camera, microphone, contacts or location access. INTERNET allows an explicitly configured HTTPS service connection. Native browser sign-in returns through this app’s unique callback scheme.

Children and audience

The publisher intends this app for users aged 13 and older. The app does not ask for a date of birth or build an account-based age profile.

Contact

Contact [email protected] for privacy questions. Do not include private files, child information, habit details or financial records in an initial support message. Sending support email uses your chosen email provider and is separate from this app’s feature data. No support message is sent automatically.

Operator, hosting and internal testing

Servenzo operates this app and its optional cloud service. Contact [email protected] for privacy questions or requests. The app service is hosted on a Servenzo-operated VPS in the United Kingdom at https://apps-api.servenzo.com. The shared sign-in service is operated there using Keycloak; app accounts and access tokens remain scoped to their own app. Quizlilt child cloud accounts remain disabled.

Cloudflare provides DNS and the traffic proxy for the public website and API. It processes network addresses, request timing and security information through its global infrastructure. Choosing an online service sends the selected information over the network; core local features do not upload your records automatically. Google Play separately handles app distribution, tester accounts and any authorized store purchases.

Account and synchronized information is retained while you keep the app cloud account, subject to the app's export and deletion controls. Requesting account deletion blocks app access and queues scoped cleanup. The shared identity-provider profile has separate controls; contact [email protected] to request its removal, with identity verification where needed. Files expire at the time you select; expiry blocks access before background cleanup removes stored versions. Independent exports and copies are outside that cleanup.

API access logs contain network address, request path without query parameters, status and timing. They rotate daily with fourteen retained rotations; service diagnostic logs rotate by size. The internal-testing service has no automated off-server backup or guaranteed recovery. Keep independent copies of information you need. Optional cloud files use private encrypted storage that the server operator can read. This test deployment uses a locally held encryption key and is not end-to-end encrypted; a maintained key-management service is required before public cloud use.

Current local R2 increment — 20 October 2026

The local R2 play workspace keeps fixed twenty-opportunity Accuracy Sprint attempts, custom duration/grid/dwell practice snapshots, UTC-day challenge identities and seeds, comparable mode/rules result cohorts, gap-preserving private trend data, chosen goal windows and pause/deletion choices. Cosmetic progress never changes target timing or removes scores/modes. Practice and interrupted/assisted categories remain labelled, and local daily results are not globally verified rankings. No new analytics uploader or paid gameplay advantage is introduced.

The new feature state remains app-scoped and local. Explicit JSON/file/clipboard exports are independent private copies; recovery can contain active or captured unacknowledged inputs. Deleting local feature data does not erase exports, OS/provider originals, separate app accounts or another product. Provider, installed-device, signed-release and store/public-policy qualification are not inferred from local tests.