# Privacy Policy Effective date: October 8, 2026. Revision: 2026-10-08.1. Updated: October 7, 2026. ## At a glance - Balushi Digital LLC runs Lizards. This policy explains how we handle personal information on the website, the Waitlist, the mobile Beta, support, and contributions. - The Waitlist collects your name and email, plus optional details, in a private Google Workspace Sheet. - The cloud Beta keeps your Account and Learner progress in AWS. Your email is not verified: anyone entering it can see, add to, move or delete your Account. - Cloud progress and recorded Allow/Decline choices are required service data, even when you decline optional analytics. Each new installation asks about tracking and Terms again. - Analytics and Session recordings are optional and identified, and they stay off unless you allow them. - When you agree to our legal terms, we keep a separate record of that agreement. - We don't sell Learner or Waitlist personal information, use it for advertising, or use identifiable Learner information to train AI. - Email info@trylizards.com to ask for access, correction, or deletion. Legal summaries, including "At a glance" and the "In short:" lines, are not part of this Privacy Policy. The full wording governs. ## Who we are and scope In short: Balushi Digital LLC runs Lizards, a study aid for adults. Reading this policy doesn't record agreement or turn on tracking. Balushi Digital LLC, a Delaware company in the United States, operates Lizards. Contact us at info@trylizards.com. Our mailing address is 8 The Green, STE B, Dover, DE 19901, United States. This is a mailing address, not a statement that it is an operating office. This policy covers the Lizards website, the Waitlist, the free, invitation-only mobile Beta, support communications, and editorial contributions. Reading it does not record agreement or enable optional tracking. Lizards is an independent supplementary study aid for university Courses, using Lesson Videos, Practice, and a progress Map. The service is intended for people aged 18 or older. The Waitlist accepts adults throughout the United States. Beta invitations are selective and availability is limited; joining does not guarantee access or an invitation date. ## Information we handle In short: Each type of information below is described in the same four parts: what it is, why we use it, who receives it, and how long it's kept. ### Waitlist details - What: your name and email (required), your university and Course interest (optional), an optional Beta request, and the signup date our server adds. - Why: to maintain the Waitlist, consider requests and invitations, understand Course interest, and send access-related communications. - Who receives it: our AWS-hosted handler, which sends signups to a private Google Workspace Sheet. - How long: while needed to manage interest and access-related communications. We then review it for removal, including matching duplicates on a valid request. The optional Beta request is separate from joining the Waitlist. Signup currently confirms on the page and does not automatically send a confirmation email. The Sheet remains the signup destination. A failed or uncertain response can require a manual retry and may create duplicate rows. A request to leave the Waitlist should identify the email addresses you used, so we can address matching entries. You may ask us to stop Waitlist or Beta invitation communications at info@trylizards.com. Necessary replies to your requests and legal or service notices are handled separately. ### Cloud Account and Learner progress - What: your supplied name and email, an Account id and creation time, and progress facts with unique fact ids, device occurrence times and Lizards' receipt times. Facts record completed Levels and whether they were perfect, Watched Lesson Videos, started Levels and their Topics, and chosen Courses. Lizards derives completed Levels, XP, the Streak, each Course's Remembered Topic and your last studied Course from these facts. Owner corrections add adjustment facts. - Why: to save and Restore Learner progress across devices, combine offline study when uploaded, maintain your Account, and handle requested corrections or deletion. A completion counts toward the Streak on the day Lizards receives it, using midnight-to-midnight days in New York time. The device shows an estimate while offline; Lizards' figures replace it after an upload. - Who receives it: Lizards' separate AWS DynamoDB Learner-data store in Northern Virginia, United States (us-east-1), accessed by the Learner-data service and the authorized company owner. The device also keeps a local copy and queues unsent facts for upload when connected. - How long: Account information and progress remain until you delete the Account; they are never deleted automatically for inactivity. Deletion, the purge, retained technical markers and backups are explained under "Retention". During the invitation-only Beta, your name and email are required. The email is trimmed and lower-cased and finds or creates your Account without a password, emailed code or verified sign-in. Entering it on another device or after reinstalling Restores Learner progress. The name entered replaces the Account's stored name. Because the email is not verified, anyone who enters your email can see, add to, move or delete your Account. Do not treat this Beta as a secure account or store sensitive information in it. Saving cloud progress is part of the service, not an optional analytics feature. Declining PostHog permission does not stop this storage. Every Allow and Decline is also recorded in the Account with the tracking notice version, the time of the choice, Lizards' receipt time and a random installation id, so the owner can see each installation's choices. Choices made offline upload when connected. This service record is independent of permission to send activity to PostHog; installations can have different choices. No tracking choice or Terms receipt is restored to a new installation. Each new installation asks for its own optional tracking choice and explicit Terms agreement. The Learner-data store is separate from the shared Course content backend, the legal-acceptance store and PostHog. The Course database does not store personal Learner profiles, progress, tracking choices or legal receipts. Optional analytics can send identified activity and a progress baseline to PostHog only after permission, as described below. The legal-acceptance flow sends the minimum identity and agreement evidence to its separate store even when tracking is declined. No existing device-only progress is uploaded or migrated to the first cloud build. That build clears old device progress and starts cloud progress from zero, while retaining saved Learner details, device settings, tracking choice and Terms receipts; a retained earlier receipt still cannot satisfy a required new Revision. Preferences such as theme and the unlock-all setting remain on the device and are not synced as Learner progress. ### Delivery and technical records - What: network and technical metadata from requests, which may include IP addresses, request identifiers, requested content, status, and timing. - Why: to deliver our website, handle signup and Account requests, save and Restore Learner progress, and provide Course information and Lesson Videos. - Who receives it: AWS, whose services provide that delivery. - How long: reviewed application and API log groups have a 14-day setting. That setting is not a retention promise for all AWS processing, provider operational records, Waitlist entries, or analytics. Necessary Course and video requests can occur before optional tracking consent and when it is declined. Reviewed Course-delivery application logs include request and content identifiers, including selected Level and Question identifiers. Caching a Lesson Video is different from retaining personal activity data. ### Optional analytics and Session recordings - What: identified product analytics and unmasked Session recordings from the mobile Beta, only if you allow them. - Why: to understand how people use the app and experience its Course content. - Who receives it: PostHog. - How long: provider-dependent, with no additional Beta-specific automatic expiry. The existing Session recording setting is 30 days. The mobile Beta offers one combined optional choice for identified product analytics and unmasked Session recordings with PostHog. You may decline and use the learning features after completing any required service agreement. Agreeing to Terms does not authorize tracking. Collection depends on your choice and on the platform and build's release gates; consent alone does not turn on a recording gate that is off. We do not initialize PostHog tracking or send product analytics before this optional permission. If you allow tracking, your supplied email is used as the PostHog identity and your supplied name is a profile property. Collection is identified, not anonymous. Shared or mistyped email addresses may associate activity incorrectly. Analytics can include: - app version and platform - session and occurrence identifiers - selected Courses and Levels, navigation, and timing - Practice answers and correctness, hints, progress, and XP - Lesson Video playback and watch activity - structured loading or playback failures An existing local progress baseline may be sent after opt-in, including completed and watched Levels. Earlier study history is not necessarily excluded from that baseline. When recording gates permit, Session recordings capture unmasked visible app screens and interactions. These may include your readable name and email on Profile, Practice answers, Lesson Video frames where supported, and touches. This is a recording of activity visible inside the app, not a camera or microphone recording feature. Don't place sensitive information on visible screens expecting it to be hidden from a consented recording. You can change Usage tracking in Profile. Confirming withdrawal stops new collection and recordings, although already captured, consented data in upload queues may finish uploading. Withdrawal does not delete previously collected analytics or recordings; request historical deletion separately at info@trylizards.com. Re-enabling tracking resumes observation and may send the applicable local progress baseline; it does not reconstruct activity that was never captured while tracking was off. PostHog's plan-based event query windows do not themselves guarantee physical deletion. The 30-day Session recording setting does not cover all analytics or downloaded or exported copies. ### Legal agreement records - What: a record of your agreement, with the details listed below. - Why: to establish the applicable wording and agreement, meet legal duties, and address claims. - Who receives it: the acceptance service, which stores it in separate company-controlled storage, independently of PostHog and marketing. - How long: only while necessary, reviewed as described under "Retention". Where required, the acceptance service records: - your supplied name and email - your affirmative agreement and any applicable eligibility confirmation - the agreement purpose - the exact document revision and checkbox-copy identifiers or hashes - the Privacy Policy revision shown - the server receipt time - relevant client or release context - a random submission or receipt identifier Mobile receipts can use a random profile or installation binding. Contributor records also identify the Source material covered. The service acknowledges only after durable company-controlled storage, with a minimal receipt cached on the mobile device where applicable. Identity remains self-reported. A receipt is evidence of the submitted act and wording, not identity authentication or proof that all claimed source rights exist. We do not collect IP addresses, Session recordings, or hardware fingerprints solely to add receipt evidence. ### Support and Contributor material - What: your sender details, message, and any attachments when you contact us; for Contributors, also supplied identity, material references, communications, Source material, and appropriate agreement evidence. - Why: to respond, handle privacy or content complaints, maintain appropriate follow-up records, evaluate and manage contributions, and prepare lessons. - Who receives it: email and communications providers; editorial AI providers, including OpenAI and Anthropic, for relevant Source material; and Fish Audio for narration and voice selections. - How long: we retain support and contribution correspondence while needed for the request, editorial work, permissions, or justified legal purposes. Agreement evidence is reviewed as described under "Retention". Please avoid sending unnecessary sensitive information. Contributors supply Source material through existing channels; this website is not a public upload library. Source material may contain third-party information. Contributors must have the required rights and remove confidential or unnecessary personal information. Course preparation uses editorial AI tools to help process Source material and prepare lessons, and narration and voice selections are sent to Fish Audio for voice generation. We remove unnecessary personal information before supplying material. These are editorial tools, not a Learner-facing AI chat service. Provider handling depends on the actual account, settings, and agreements; we make no universal promise of zero retention or that providers never use editorial inputs for training. Provider and voice-rights verification remains a release check. ## Website tracking In short: The website has no analytics, advertising, or tracking cookies, although hosting still processes your requests. This website uses locally hosted fonts and assets. It has no analytics or advertising SDK, tracking cookies, or browser-storage tracking. Hosting and network processing still occur to deliver the page and process submissions. We do not arrange for third parties to collect website visitors' activity across other websites for advertising through this site. Browser Do Not Track signals do not change this website's behavior, because it has no such tracking to switch off. Do Not Track is distinct from other privacy preference signals, and it does not replace the mobile app's optional tracking choice or rights that apply under law. ## Recipients and purposes In short: Service providers, our staff, and in some cases advisers or authorities receive information for the purposes described here. We don't sell Learner or Waitlist personal information or use it for advertising. These recipients receive information for these purposes: - AWS: hosting, delivery, technical processing, the separate Learner-data store, and the separate legal-record storage. - Google Workspace: the private signup Sheet and relevant communications tools. - PostHog: the optional identified analytics and eligible Session recordings described above. - Support and communications providers: correspondence. - Editorial AI and voice providers: relevant Source material or narration. Authorized company personnel and service providers access information for the stated work. Legal advisers and authorities may receive information when reasonably necessary for legal duties, rights, security, or claims. A business transfer may involve necessary information, subject to applicable law and appropriate notice and safeguards. We do not sell Learner or Waitlist personal information, use it for advertising, or use identifiable Learner information to train AI. This operating commitment is distinct from processing Source material through editorial AI tools under a Contributor's authorization. Information may be processed in places where providers operate. We do not promise that every provider stores all information only in the United States. ## Retention In short: Cloud progress stays until you delete the Account. Deletion stops access immediately; personal Account fields and facts are purged within 30 days. Backups may keep them for up to 35 more days. Legal records and PostHog deletion are separate. You can select "Delete my account and progress" in Profile while connected. It immediately stops access to that Account and frees its email for a new Account. Other devices clear their copies and discard unsent facts the next time they reach Lizards; deletion cannot remotely erase an offline device immediately. Entering the same email later starts a new Account from zero unless the earlier deletion has been undone on request. The daily purge removes the deleted Account's personal fields and all its progress and tracking-choice facts within 30 days. Purging becomes eligible 29 days after deletion. If deletion was a mistake or made by someone else, contact info@trylizards.com promptly to request undo before the purge; recovery is not guaranteed throughout day 30. Once purged, it cannot be undone through the normal Account procedure. A minimal technical marker, keyed by the old Account id and holding its deletion time, remains to reject stale devices and prevent cached progress from recreating that Account. AWS point-in-time backups can retain purged Account information for up to 35 more days. A backup restore must reconcile deletions and these markers before the restored information can be used. Account deletion does not delete Terms receipts, Waitlist entries, or PostHog analytics and Session recordings. Request those separately at info@trylizards.com; their own retention, verification and justified-preservation rules apply. Provider copies, backups, and operational data may have their own retention and deletion processes. We handle deletion requests through the relevant provider tools and address copies we control. Deletion can be asynchronous, and requesting or initiating deletion does not mean every copy disappears immediately. Limited agreement evidence may be retained separately from study or analytics data when necessary to establish the applicable wording and agreement, meet legal duties, or address claims. We review necessity based on: - the agreement's continuing relevance - applicable duties and claim periods - pending disputes or preservation requirements - whether the record can be reduced We limit access and securely dispose of records when they are no longer justified. We do not promise a single fixed period for every category, or keep personal evidence indefinitely merely because an archive exists. Public legal text archives contain wording, not personal receipts or Contributor descriptions. ## Security In short: We separate service records and restrict administrative access, but the Beta's email access is unverified. Anyone entering your email can act on your Account. We use safeguards appropriate to the information, including HTTPS, restricted administrative access and separation of Learner data and legal records from public Course content. These safeguards do not verify who enters an email in the Beta: anyone who knows it can access, change, move or delete the Account. The native-client request marker is not authentication. No transmission or storage system is perfectly secure, and local storage is not a secure vault. We do not claim that all provider security, backup, or deletion settings have been independently verified. ## Your choices and requests In short: Email info@trylizards.com to ask for access, correction, or deletion, or to leave the Waitlist. Turning off tracking or removing the app doesn't delete what we or our providers already hold. Email info@trylizards.com to ask to: - leave the Waitlist - stop invitation communications - correct information - access it - request deletion Tell us which service and supplied email addresses are involved, what you want changed, and enough context to locate the information. Do not send identity documents unless we explain why they are necessary. We use reasonable identity verification proportionate to the request and the risk; the app's self-reported email alone is not verified ownership. Depending on where you live and the law that applies, you may have additional access, correction, deletion, portability, objection, restriction, consent-withdrawal, appeal, or complaint rights. We consider requests under applicable law, explain limitations or justified retained records, and provide any applicable response or appeal information. This policy does not assert that all state laws apply or that the service is exempt from them. You may contact an appropriate regulator without contacting us first. What choices in the app do: - Turning off tracking stops future collection, subject to consented queues, rather than erasing history. - In the cloud Beta, logging out clears the device's profile, progress copy and local tracking/Terms binding; Lizards keeps the Account. The app tries to save queued progress first and warns if unsaved completions will be lost by logging out. - Changing your email while connected moves the same Account and its progress to the new email; it does not merge with or overwrite an Account already using that email. Changing name or email asks for tracking and Terms again without rewriting historical records. - "Delete my account and progress" replaces "Reset progress" in the cloud Beta. It deletes the cloud Account under the process in "Retention", while legal receipts and PostHog history remain separate. - Removing the app is not an Account deletion request. The cloud Account remains; device backups may contain local copies. Ask us separately about information held by the company or its providers. Restoring Learner progress does not establish a Terms receipt or tracking permission on a new installation. Builds without cloud progress retain their device-only progress and Reset progress controls until replaced; those controls do not delete company or provider records. ## Adults only In short: Lizards is for people 18 or older. Tell us if you think we hold information from someone younger. Lizards is intended for adults aged 18 or older. Do not join the Waitlist or submit information if you are under 18. If you believe we hold information from someone under 18, contact info@trylizards.com so we can investigate and take appropriate action, including deletion where required. An adult-only policy is not proof that every existing profile's age has been verified. ## Changes to this policy In short: We date every revision, keep the exact earlier wording, and give notice of material changes. We will label intentional revisions with their updated and effective dates, preserve the exact earlier text, and use appropriate in-service or email notice for material changes. We will obtain any permission required for a changed practice before carrying it out. A Privacy Policy notice is not an agreement checkbox or permission for optional analytics. ## Contact In short: Write to info@trylizards.com or to our mailing address. For privacy questions, requests, content complaints, or legal notices, contact Balushi Digital LLC at info@trylizards.com or by mail at 8 The Green, STE B, Dover, DE 19901, United States.