LAF · Privacy
A small profile. Clear controls.
How the Laf online edition handles account, game and purchase information.
Account and public profile
Laf uses Firebase Authentication for Apple and Google sign-in. Those providers may supply technical identifiers and email information needed to authenticate the account. The application does not ask for a legal first/last name. The public profile contains a unique username and an optional small avatar; provider names and photos are not copied into it.
Game and economic records
The game service processes language/league selection, table actions, match results, invitations, tournament registration and points. Server checks protect hidden hands and prevent duplicate charges or awards. Store transaction identifiers are used to verify purchases and prevent replay; full payment-card information is not collected by Laf.
Small images and retention
The avatar is re-encoded as a 64×64 WebP image, at most 32 KB. The large original is not retained. Replacing an image deletes the previous file. An avatar is removed after fifteen days without verified app activity; a scheduled worker checks the latest activity and image version before deleting it.
Notifications and services
Device notification tokens support invitations, table readiness and tournament reminders. You control notification permission in the device settings. The mobile game uses Firebase/Google Cloud; this public website is hosted on Beyondend’s Appwrite service and has no website account or checkout.
Deletion and contact
Account deletion removes the profile, images, device tokens and social links. Minimal purchase replay-prevention and economic correction records may remain separate from the public profile. Contact team@beyondend.dev for privacy requests.
Website preference
This website stores only your selected interface language in local browser storage. It does not use a location/IP lookup to choose your language. Hosting services necessarily process requests to serve the site.
Last updated: 2026-11-07