Effective date: .
Current service disclosures reviewed .
Account age and local use
Personal and organization-managed PearaByte accounts require age 13 or older, or a higher applicable product or regional minimum. Personal guardian enrollment and school-managed under-13 accounts are unavailable at initial launch. School approval, a purchase or platform app approval cannot override this restriction.
Neural Notes and PearStead allow basic local use without an account where platform rules permit. Local content and mandatory platform verification or parental-permission requirements still apply. Do not create an adult account for a child or upload a child's information through another account to bypass the restriction.
The initial school offering focuses on eligible high school and college students. School/work identities remain separate from personal identities and use age bands rather than exact DOB by default. School-created under-13 profiles and school-hosted sync are future options, not current services.
An entered birth date is self-declared; a platform age range can also be declared or parent-provided. School SSO, an email domain or a payment does not establish verified age or educational authority. School use requires current organization terms, privacy acknowledgment, data-processing terms and education-use requirements.
Contact support@pearabyte.com about a child's information, review, deletion or stopping further collection. No paid plan or account is required. We verify identity or authority before disclosing another person's information. Do not send identity documents or unnecessary sensitive child information with your initial request.
Who operates the service
PearaByte LLC is a North Carolina limited liability company.
Business mailing address: 510 Central St #180, Hudson, NC 28638, United States.
For support, privacy requests or legal questions, contact support@pearabyte.com or write to the address above. Do not send passwords or recovery keys.
Organization setup requests
Authorized adult representatives can request organization setup from Account Details. We record the organization name, sign-in name, type, country/state, requesting account and review history. A reviewed request can provision a separate managed owner identity. It does not convert the representative's personal account, grant product seats or authorize children. Setup credentials expire after 24 hours and are single-use.
Terms and privacy confirmation
Sign-up presents required documents with separate checkboxes. We record the document version, action and confirmation time. Terms are accepted; privacy notices are acknowledged. A privacy acknowledgment is not consent to optional processing. Account profiles do not ask you to repeat these sign-up confirmations; security, billing, recovery and privacy help remain available.
Recent sign-ins
Your overview shows the creation time of your most recent recorded account session. For new sign-ins, we retain a coarse browser/operating-system description derived from the client's User-Agent; we do not retain the raw User-Agent for this summary. This description is self-reported, not proof of device trust. A device or approximate security location may be unavailable. When configured, a local IP lookup derives approximate sign-in city, state/region and country for account security. VPNs and mobile networks can affect this estimate. The recorder retains coarse client and location details for up to 30 days; authentication session state follows its own expiry. It does not retain raw IP addresses, full User-Agent strings or coordinates, request GPS, or send IP addresses to an external location service. Declared residence is never silently changed from a sign-in location. Verified email accounts receive notices for subsequent successful sign-ins, limited to one per hour. Refreshes do not send notices. Accounts without email can review sign-in history in the account overview. This release does not add GPS collection or an external IP-location lookup.
Shared account information
The PearaByte account layer processes identity and authentication information such as email, display name, password hash where applicable, linked identity providers, sessions, security settings, and the list of PearaByte products connected to the account.
Account review and corrections
Account Details shows your personal date of birth, declared country and state/region. You can submit an accurate correction; saving a correction revokes existing sign-ins and rechecks cloud eligibility. DOB is self-declared unless a separate applicable verification process establishes otherwise. Product apps cannot retrieve your DOB from the account-view API. Managed users see their age band and organization residence and ask their administrator for corrections.
Date of birth, age classification and residence
Personal PearaByte accounts require a date of birth and declared country or region of residence. Where subnational requirements matter, we also ask for a structured state or region. We use these fields to calculate age/content eligibility and determine which product or jurisdiction requirements apply. Product apps receive the resulting eligibility decision or applicable minimum age; they do not receive your stored date of birth.
When age or platform signals conflict with account eligibility, PearaByte may record a bounded review case with the account/product, signal source, outcome and timestamps. Product apps do not submit raw birth dates, identity documents or full provider responses to that review queue. An explicit platform verification or revoked-approval result can stop cloud connection even when account information would otherwise be eligible.
Organization-managed school/work accounts are separate identities. Their organization completes the applicable organization-level jurisdiction, privacy and data-processing requirements, and managed users ordinarily provide only the minimum age classification needed for policy (currently 13–15, 16–17 or 18+) rather than an exact birth date. School-managed accounts require age 13 or older at initial launch. Verified educational authority cannot enable under-13 enrollment.
We do not sell date of birth, age classification or declared residence information. They are not used for advertising. Declared residence or organization jurisdiction is policy information and is not treated as proof of current physical location.
U.S. signup declaration
When you explicitly confirm U.S. residency to create a new account, we record the accepted declaration with its policy version, signup method and server receipt time, linked to your account. A browser-provider signup temporarily binds the declaration to its sign-in request. We use it to administer launch eligibility; it is not geolocation, proof of residence, age verification, parental consent or agreement to terms.
We do not invent declarations for existing accounts. The accepted record remains with the shared account and is removed from active account records on full account deletion; deleting only one product’s cloud data keeps it. Contact us to request access, correction or deletion. Recovery copies follow the separate backup practices described below.
Product boundaries
Each PearaByte app or game owns its product-specific data and may store that data in the shared infrastructure or in a separate product service. The central account view receives bounded account summaries rather than unrestricted product content. Review the product-specific privacy notice for details about that product’s content and retention.
Two-factor authentication
If you enable two-factor authentication, PearaByte stores an encrypted authenticator secret and one-way hashes of recovery codes. The same factor protects PearaByte account sign-in across products. Two-factor authentication is optional for ordinary accounts and required while administrator authorization is active.
Account sign-in recovery is separate from a product's encrypted-content recovery. Neural Notes uses a separate Secure passphrase, emergency codes and enrolled-device approval as described in its privacy notice. An account password reset or account two-factor recovery code does not reconstruct those Secure keys.
How we use account information
We use account information to create and authenticate your account, verify email addresses, recover access, calculate age/content eligibility, apply applicable product and regional requirements, connect your chosen products, deliver service messages, provide support, and protect accounts against misuse. Connected-product and purchase information supports the access you have purchased or received.
Providers and operations
OVHcloud provides hosting and Resend delivers transactional email. When enabled and selected, Google or Apple handles its sign-in flow and supplies identity information used to connect that provider to your account. Stripe, Google Play or Apple handles purchases through the applicable payment channel; product notices explain those channels. Payment-card details are handled by the payment provider.
Security and operational logs may include request times, network information, app versions and error information. A U.S.-only launch does not mean all data is stored or processed only in the United States; providers may process information in other countries.
Website cookies, preferences and analytics
Website sign-in uses a Secure, HttpOnly, SameSite session cookie. Authentication credentials are not stored in browser local storage. “Remember me” on sign-in makes the cookie persistent until its server expiry; leave it off to use a browser-session cookie. Browsers may restore session cookies when reopening windows. Sign-out, revocation or server expiry ends access either way. Your cookie choices are recorded in local storage for six months without a visitor identifier. The required host-only pearabyte_language cookie remembers an explicitly selected interface language for 180 days, containing only a supported language or System. Signed-in language preferences are saved separately to your account; signing out restores the anonymous browser choice. Language never determines residence, eligibility or consent. The website does not remember your last product page or use it to change your Home destination. Optional performance analytics counts public product page views and download/store clicks by day. It sends only a fixed public page label and event type to our own backend, without sign-in cookies, visitor IDs, account details, notes, referrers or session recordings. Daily aggregate counters are retained for 180 days; technical network/security logs remain separate. Optional features remain off until you choose them. You can accept, reject or customize from the banner and reopen Cookie settings in any footer. Global Privacy Control and Do Not Track disable optional analytics and future marketing/social collection. Counts describe opted-in events rather than unique people or completed purchases. We do not currently use advertising or social media trackers or sell personal information for advertising. Those categories are shown as not in use. Adding a provider or purpose requires updated disclosures and a fresh privacy choice before loading it. Cookie preferences do not opt you into marketing emails. Optional checkout loads Stripe payment components, which may use cookies or identifiers for payments and fraud prevention. Those components are not loaded merely to read these policies.
Automatic service reports
Website, administration and backend failures generate technical reports automatically so we can investigate problems. Reports contain a reference code, operation category or registered server route template, software build, response status, random request reference, occurrence times and count. They can also contain a coarse operating-system/browser category and a partial trace of known application modules. These categories do not identify a particular device; traces contain only reviewed static module identifiers. They exclude account identities, page and request contents, passwords, notes, raw error messages and raw stacks. Repeated reports are grouped, expire after 30 days and are removed by bounded cleanup. Authorized platform administrators can review them. This is separate from the optional reports you choose to send from Neural Notes and PearStead.
Retention and deletion
Active account information is kept to provide your account services. Product-only cloud deletion preserves the shared identity and purchases. Full PearaByte account deletion removes the active identity and owned product cloud data, subject to the limits explained on that page and in product notices. It cannot remotely erase local exports or copies held by other people.
Hashed deletion proof and sign-in identifiers that block delayed sign-ins expire after 24 hours and are removed by scheduled cleanup. Normal terminal account-mail and action history is pruned after seven days; account deletion removes account-linked records sooner.
Ordinary administrative action and content-access records are eligible for scheduled cleanup 90 days after creation. Billing audit records are eligible for scheduled cleanup two years after creation. Cleanup runs in bounded batches, so removal can occur after these periods. These periods concern PearaByte's audit records, not every account, payment-provider or infrastructure record.
Operational database recovery backups exist separately from active account data. Their retention is currently operator-managed. Deleting active account records does not immediately remove every recovery copy. Operational logs are rotated according to infrastructure limits; the retention interval varies with activity. Records already held by infrastructure, payment, identity or email providers follow their applicable retention practices. Contact us with a privacy request concerning these records.
Your choices
You can manage sign-in and security from the account page. Product-specific data controls remain available from each product. See the data and subscription controls for deletion, local exports, cancellation and privacy requests. Local use of Neural Notes and PearStead does not require an account.
Privacy requests
Email support@pearabyte.com with the subject Privacy request. Tell us which product is involved and whether you want access or a copy, a correction, deletion, or help exercising another applicable privacy right. Include an account email if relevant and a way to contact you. You do not need a PearaByte account to raise a request, including about your information in another person's household or shared content.
A parent or guardian can contact us about a child's information, including review, deletion or stopping further collection. A household invitation alone does not establish parental authority. We may need to verify your identity or authority before disclosing or changing information. Do not send passwords, authentication codes, recovery keys, identity documents or private note, health or household contents with your initial request. If additional information is needed, we will explain what is necessary. Local exports do not include every server-held account or billing record.
The rights, exceptions and response deadlines that apply depend on the request and applicable law. If you disagree with our response, reply to request a review or an appeal where applicable. Contacting us does not waive your right to contact a regulator or use other legal remedies.
Changes to this notice
We will update the effective date when this notice changes. Material changes will be identified here or communicated through an appropriate account or product channel. Where applicable law requires notice or consent before a change takes effect, that requirement still applies.
Product privacy notices
Use the notice for the product whose data you want to understand or manage.
Contact
For account or privacy questions, contact support@pearabyte.com.
Regional requirements and privacy choices
Account and cloud availability, age requirements, required residence information and parent or school authority depend on the product and applicable country/state rules. An available country selector is not an announcement that account services or purchases have launched there. Our stated launch offering remains in effect until we announce an additional region.
Terms acceptance establishes the applicable service agreement. A privacy acknowledgment confirms that the notice was presented; it is not blanket consent for optional processing or permission to collect a child's data. Where processing requires a separate consent, that choice must concern the stated purpose and can be withdrawn. Purchasing Pro, store parental permission or school sign-in does not provide that separate authority.
You can contact support@pearabyte.com about applicable access, correction, deletion, objection, restriction, portability or consent-withdrawal rights and help with a privacy complaint. This includes Mexico's applicable access, rectification, cancellation and opposition (ARCO) rights. Rights and response requirements depend on the applicable law. We verify identity or authority before disclosing another person's information; privacy help does not require Pro, a new purchase or acceptance of revised terms.
Organization authority applies only to its separate managed identity and approved service. School authority must cover the educational purpose and applicable jurisdiction; it does not authorize unrelated commercial use or access to a separate personal account. Published notices do not themselves establish a school's authority, an international transfer arrangement or age verification.