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.
The optional LAYAI Browser Connect extension requests only local extension storage, a periodic timer, a browser sign-in redirect and access to https://layai.pro. It does not request tabs, browsing history, page content, search queries or access to other websites. We store a browser connection identifier, a hash of its credential, pause status and server-observed connection times. The credential itself stays in the extension's local storage. Google sign-in happens on the LAYAI website; the extension never sees your Google password or identity token.
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, browser connection time, daily check-ins and accepted tasks create distinct contribution point entries under the published rules. Browser connection time does not prove that a research task ran. Contribution points are participation records, not tokens or a guaranteed airdrop allocation.
If you join through an invitation link, we record which account invited you, when you joined and when you qualified. Your inviter sees aggregate invitation counts and points, not your name, Google address or wallet address. Invitation and accepted-task share entries are kept in the contribution ledger. Account closure removes active invitation links and retains pseudonymous historical point entries. A digest of a closed account's connected sign-in identity may be retained to prevent repeated invitation rewards.
The website counts approximate daily browser visits to understand whether people are finding the project. It stores a random identifier in this browser for the current UTC day and sends only that identifier, a broad page name and a page-view or visible-presence event to LAYAI. The server stores a day-specific hash, first and last observation times, and page-view count for up to 30 days. It does not store the visitor's IP address, user agent, URL query, account identity or activity on other websites in this analytics table. Do Not Track and Global Privacy Control disable this browser measurement. Clearing browser storage or using another browser can count as another visitor; these figures are estimates, not a count of people.
If you choose a Discord or 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. Browser sign-in sessions can last up to 30 days unless you sign out. Extension participation stops when Chrome is closed, you pause or disconnect it, sign out everywhere, or close the account. An ordinary website sign-out does not disconnect an extension you chose to keep running.
Browser extension: limited use of data
LAYAI Browser Connect's use of user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Extension connection identifiers, credentials, observed connection times and point summaries are used only to provide, maintain and secure the extension's account connection and participation features. We do not sell extension user data or use or transfer it for advertising. Transfers are limited to what is necessary for these features, security, applicable law, or a merger, acquisition or sale of assets. Human access is limited to specific user consent, security investigations, legal obligations, or aggregated and anonymized internal reporting.
Optional advertising measurement
On public marketing pages, Google Ads (Google Ireland Limited / Google LLC) loads only after you choose Allow. It uses advertising cookies and processes page visits, ad attribution and device/network information, including the IP address sent with a network request, to measure advertising performance. Google may process this information outside your country. We do not send account names, email addresses, wallet addresses, contribution records or device credentials. Advertising personalization and enhanced conversions are disabled. The tag is not included on account, sign-in, Android connection or desktop app pages. Your choice is stored in this browser for up to 180 days. Use Cookie preferences to withdraw consent; Do Not Track and Global Privacy Control disable this measurement. Declining does not restrict the service. See Google’s privacy policy and advertising information.
Reklam ölçümü yalnız izin verirseniz herkese açık tanıtım sayfalarında çalışır. Google ziyaret ve cihaz/ağ bilgilerini (IP adresi dahil) işler. Hesap, cüzdan ve katkı verileri gönderilmez. Kişiselleştirme kapalıdır. Tercihinizi Çerez tercihleri düğmesinden geri alabilirsiniz.
Contact
For account, data or participation 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. Katkı puanları token veya garanti airdrop hakkı değildir. Ayrıntılar bu sayfanın İngilizce bölümlerindedir.