Last updated: October 19, 2026
Nalana uses account information and operational records to provide the application, protect accounts and diagnose failures. Optional website analytics, visitor identification and in-app usage measurement have separate choices. See our Cookie Policy for website storage and controls.
We process your email address, account profile, authentication and verification state, account entitlements and service requests. Passwords are checked against a protected password hash. Verification messages are sent through our email provider, Resend. Queued, provider accepted, delivered and bounced are distinct delivery states; delivery does not prove that you read a message.
To provide requested AI features, Nalana sends the instructions and context needed for that request to the backend and its configured AI providers. Optional funnel measurement does not include prompts, generated code, scene contents, file paths, passwords, email addresses or verification tokens. Diagnostics have a separate setting and are not enabled by granting usage permission.
Operational records describe account creation, sign-in outcomes, verification, authorized cloud operations, delivery and installer transfer attempts. For direct downloads, an internal request notification contains the requested platform and time, without your identity, IP address or browser details. It does not confirm a completed download, installation or unique person. The direct file transfer itself is unobserved. When transfer tracking is enabled, a download start means the transfer server accepted a nonempty response-body write. It does not establish a completed file, installation, application launch or a unique person.
When transfer tracking is enabled, a first-party random download cookie helps suppress repeated transfer notifications within 24 hours. Direct request notifications are not deduplicated. The cookie is not used to fingerprint you or shared as a Google Analytics or RB2B identity. Deleting cookies or using another browser can create another identity.
We count public page views, successful download requests and newly created website accounts by day, source and campaign, including when optional analytics is declined. These counters contain campaign labels and totals, without visitor IDs, account IDs, email addresses, IP addresses, browser details or individual event histories. Campaign tags may travel through public website links and signup requests, without cookies or browser storage for these counters. They are aggregated immediately and are not joined to customer files. Missing or stripped sources remain unknown. A download request does not prove a completed download, and these totals do not identify unique people.
Reports cover up to 90 days at a time and exclude campaign buckets older than 365 days. Older buckets are removed during counter maintenance. Optional vendor analytics and identification still require the choices below.
Optional vendor analytics and app usage measurement are default off until you choose to allow them. With permission, pseudonymous usage records can describe current app readiness, observed result presentation, intentional revisions and explicit saves. An optional account association or short-lived download pairing code can connect permitted activity across surfaces. We do not match people by IP address, email address or nearby timestamps to invent a funnel link. Without permission or a valid explicit link, coverage remains unknown or unlinked.
Google Analytics and Vercel Web Analytics use the optional usage analytics choice. Vercel Web Analytics runs only on our production website, with URL queries and fragments removed. RB2B visitor identification requires its own separate choice. RB2B is an identification service and its data must not be described as anonymous. Account, sign-in, recovery, verification, pairing and operator pages do not load these vendors. Change your choices using . In-app usage permission is controlled separately in Nalana Settings.
These limits describe acquisition and usage measurement. Account, billing, support and security records may have different retention needs. We retain minimal operational or security evidence where needed to prevent abuse, resolve disputes or meet applicable obligations.
You may revoke optional usage permission at any time. Revocation stops new optional collection and clears pending uploads; it does not erase all historical business records. You can request deletion of optional measurement records with proof of account or enrollment ownership. Requests are completed within 30 days, subject to disclosed security and operational exceptions. Contact clarence@nalana.io for access, deletion or help with your choices.
Our hosting, database, email, payment and configured AI providers process information needed for the requested service. Optional website vendors run only under the applicable choice. We use access controls, encrypted transport and restricted credentials; no system can promise absolute security. Funnel events exclude raw IP addresses, raw user agents and sensitive URL queries; service security logs have a separate operational purpose.
Nalana is not directed at children under 13. We update this policy as practices change. Related documents: Terms, EULA, Refund Policy and Cookie Policy.