LAYAIWhat LAYAI records
We store a LAYAI account identifier, account name, password hash if you create a password account, and linked Google or EVM wallet identifiers if you choose those sign-in methods. Google sign-in stores the verified Google account ID (sub) and a generic label. The Google identity token is checked for sign-in and is not kept as an account record. We do not request Gmail, Drive, contacts, Google passwords or wallet keys.
When you connect a computer or phone, the service stores a device identifier and credential hash, device name, connection and pause status, coarse device-reported resource readings, supported task capabilities, task outcomes, and contribution entries. We do not request personal files, keyboard content or precise location. The researcher may see accepted research results; device-reported timing and hardware readings are not proof that work was performed.
How records are used
Account identifiers let you sign in and see the same history on your devices. Device credentials connect the app to approved work. Server-observed readiness, daily check-ins and accepted tasks create contribution point entries under the published caps. Contribution points are participation records, not tokens or a guaranteed airdrop allocation.
If you choose a Discord or private-pilot X mission, read-only verification checks the linked provider account and stores a stable identity reference to prevent duplicate one-time claims. Provider access tokens remain in server memory and expire; they are not placed in the app package or point ledger. X follow rewards are disabled in the prepared public service while their compatibility with X's developer policy remains unresolved.
What is shared
Your account page shows your own history. The public research page shows only aggregate contribution counts, such as members, online computers, accepted tasks and total recorded points. The operator can review tasks and eligible community claims from a private console. Google, Discord and X receive only the information involved in an account connection you start; LAYAI does not post, follow or join on your behalf.
Your controls and retention
The account page lets you download an account record, sign out every session, disconnect a device and close the account after typing a confirmation phrase. Closing an account revokes its credentials and removes directly linked sign-in, device and social review records from the active service. Historical point entries and accepted research results remain under a random closed-account identifier so aggregate results and the ledger are preserved. A minimal hashed social identity marker remains to prevent a repeat one-time reward. These records are pseudonymous and may still be identifiable. A closed account cannot recover its old contribution points.
The active service keeps records until account closure or operator removal. Scheduled database backups are encrypted and expire after 30 days. Migration and recovery copies are tracked separately and must be retired within 30 days after the migration is accepted. Account closure does not immediately erase older encrypted backups. Before a restored backup returns to service, closure requests made after that snapshot must be reapplied. The current off-server recovery copy is held in the operator’s protected local profile; automatic off-server replication is not yet configured. Browser sessions can last up to 30 days unless you sign out. Device participation stops when you pause, stop, revoke the device or close the account.
Contact
For account, data or pilot questions, contact layaiprotocol@gmail.com. Do not email passwords, recovery phrases or private keys.
Türkçe özet
LAYAI Connect, hesabı, bağlanan cihazları, doğrulanan katkıları ve isteğe bağlı sosyal görevleri kaydeder. Google girişinde doğrulanmış hesap kimliği saklanır; Google parolanız, Gmail veya Drive verileriniz istenmez. Hesap ekranından verinizi indirebilir, tüm oturumları kapatabilir ve hesabınızı kapatabilirsiniz. Hesap kapanınca doğrudan kimlik ve cihaz kayıtları kaldırılır; puan defteri ve kabul edilen araştırma sonuçları takma kimlikle korunur. Pilot puanları token veya garanti airdrop hakkı değildir. Ayrıntılar bu sayfanın İngilizce bölümlerindedir.