Nalairos Privacy Policy
Nalairos LLC | Nalairos | Nalairos Labs
Last updated: September 30, 2026
REVIEW DRAFT — PUBLICATION CHECKS REMAIN. HomeKeep and ReturnRadar have notices for the audited Android releases identified in Section 12. StormLine includes static Android release findings, with runtime behavior and remaining storage and deletion details still pending verification. The website notice reflects the reported Squarespace settings and visible contact-form fields. Confirm where form submissions are sent or stored and whether the website uses embedded services, custom code or additional analytics before publishing this draft as the policy for all listed services. Bracketed review notes are instructions for Nalairos, not final policy language. Use the actual publication date when adopting the policy.
1. About this Policy
Nalairos LLC ("Nalairos," "we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information in connection with the Nalairos business website and the applications identified below that link to this policy.
Nalairos and Nalairos Labs are names used by Nalairos LLC. Nalairos Labs is our developer and publishing name; it is not a separate company for purposes of this policy.
This policy is structured to cover our website, inquiries and support communications, and HomeKeep, ReturnRadar, and StormLine. The application-specific notices in Section 12 form part of the policy and describe each app's particular practices. A feature described for one app does not mean that every app includes that feature or handles the same information.
Other businesses, products, or services operated by Nalairos LLC are not automatically covered merely because they share our company or brand name. We will identify additional covered services here or provide a separate policy for them.
Our services are currently intended for users in the United States. This statement does not mean that all service providers process information only in the United States.
Business location: Largo, FL 33770, United States
Privacy and support contact: support@nalairos.com
2. Interpretation and Definitions
Personal information or personal data means information that identifies, relates to, or can reasonably be linked to an individual. We use these terms interchangeably unless applicable law requires a different meaning.
Services means the website, applications, and related support activities expressly covered by this policy. Service providers are companies that handle information to help us operate those services. You means a visitor, user, or person who contacts us.
3. Collecting and Using Your Personal Information
Information you provide to us
Our contact form asks for a first name, email address and message. First name, email address and message are required; last name is optional. When you submit the form or email us, we receive the information you choose to provide, including any additional details you put in your message. We may also keep our responses and related correspondence.
Please provide only information needed for your inquiry. Do not send passwords, full payment-card information, government identification numbers, or unrelated sensitive information through the contact form or ordinary support email.
The website currently provides business information and a contact form. It does not currently offer visitor accounts, newsletter subscriptions, or online checkout. Submitting a contact form does not subscribe you to marketing messages.
Website technical information
Our website is hosted by Squarespace. When you visit, Squarespace receives technical information used to deliver, maintain, and protect the website and its platform. This can include your IP address, browser, network and device information, referring pages, pages visited, and information about your interactions with the website, such as timestamps or loading errors.
Squarespace processes contact-form information as our service provider. It also processes certain automatically collected visitor information for its own purposes, including platform security, as described in its Privacy Policy. These activities can occur even when we have not added a separate tracking service.
Cookies and similar technologies
Our website uses Squarespace cookies and similar technologies for website functions, security and visitor analytics. Non-essential analytics and performance cookies are currently permitted by our site settings. These cookies identify visitors and sessions to generate statistics about traffic sources and how people use the site. The Squarespace cookie banner is disabled, so the site is configured to permit these cookies without first offering an accept-or-decline choice through that banner. Browser settings or other privacy controls may affect whether cookies are stored.
Squarespace's Activity Log is enabled and makes individual page-visit information available to us in Analytics. Entries can include the page visited, visit date and time, IP address, approximate location inferred from that address, browser version, operating system and referring page. This helps show how visitors find and browse the website. The log displays visits from the past seven days; this display window does not establish that all related analytics or provider-held information is deleted after seven days.
You can block or delete cookies through your browser settings. Blocking cookies may affect website functions. Our current Squarespace configuration does not provide cookie choices through a banner. Browser cookie controls do not prevent all technical information from being received by Squarespace when you visit the website.
For more information, see the Squarespace Privacy Policy and the cookies Squarespace uses.
Information handled by our applications
The specific information each application accesses, stores, or transmits is described in Section 12. Information stored only on a device is different from information sent to Nalairos or another company. A local-storage feature does not, by itself, establish that an app or its included third-party code collects no information.
Contacting us about an app is covered by the contact and support provisions above, even when the app itself does not transmit that same information.
4. How We Use Personal Information
We use information received through our website and support channels to respond to inquiries, troubleshoot reported issues, communicate about a request, and keep necessary records of the request and our response. We also use information as needed to operate and secure the website, prevent misuse, comply with legal obligations, and address disputes.
Additional uses of information within a particular app must be identified in that app's notice in Section 12. This policy does not authorize undisclosed collection or unrelated uses of information simply because a future product might include new features.
We do not use contact-form submissions or support correspondence to enroll people in newsletters or promotional text-message campaigns. We do not sell that correspondence or provide it to advertisers for their own marketing.
5. How We Disclose Personal Information
Service providers
Information is handled by providers needed to operate our website and communications, including Squarespace and our business email provider. These providers process information for functions such as website hosting, form storage and delivery, email delivery, and security.
For information handled on our behalf, we use provider arrangements intended to limit handling to the relevant services and protect the information. Where a provider separately determines how it uses certain information, as Squarespace does for some technical visitor information, its own privacy notice also explains that processing. App-specific recipients and their purposes must be identified in Section 12.
Legal requirements and protection
We may disclose information when required by law or a valid legal process, or when reasonably necessary to investigate misuse, address security incidents, protect rights and safety, or establish, exercise, or defend legal claims.
At your direction
We may disclose information when you request that we do so or give valid consent to a specifically explained disclosure. We do not treat visiting the website or reading this policy as blanket consent to unrelated sharing.
Nalairos does not sell personal information. Operational disclosures to providers described in this policy are not a promise that information is never handled by another company.
6. Retention of Your Personal Information
We keep contact-form submissions and support correspondence while addressing an inquiry or issue. After resolution, we delete information that is no longer needed or retain relevant portions where reasonably necessary to document our response, handle follow-up questions or disputes, or meet legal recordkeeping obligations.
Retention depends on the purpose of the record, whether the matter is resolved, the need for follow-up, and applicable legal requirements. We do not retain correspondence indefinitely merely because it could be useful someday, or for sale to third parties.
We review retained records and delete them when those reasons no longer apply. Provider-held copies, including copies in backup systems, may remain for the provider's applicable retention or deletion cycle. Deletion from one inbox does not necessarily remove copies stored with the contact-form provider.
Retention and deletion of app-specific information are described separately in Section 12. We do not apply an assumed fixed two-year retention period to every category of information.
7. Your Choices and Deletion Requests
You may choose not to submit personal information through the contact form or email, although we may be unable to respond without a way to contact you and sufficient details about the issue.
To ask about, access, correct, or request deletion of personal information we hold about you, email support@nalairos.com. Identify the relevant website or app and describe your request. We may request information reasonably needed to locate the records and verify that you are entitled to make the request. Do not send identity documents unless we explain why they are necessary and provide an appropriate method.
We handle requests in accordance with applicable law. Certain information may need to be retained for legal obligations, security, or legitimate dispute-related purposes; where applicable, we will explain relevant limitations. Where processing depends on consent, you may withdraw that consent by contacting us. Withdrawal does not undo processing that lawfully occurred before withdrawal.
Depending on the laws that apply to you and our business, additional rights may include obtaining a portable copy, objecting to or limiting certain processing, using an authorized agent, or appealing a decision. You may contact the same email address to exercise applicable rights or request review of a decision. We will not unlawfully discriminate against you for exercising privacy rights.
For information stored only on your device, we cannot remotely remove a copy that we do not hold. Each app's notice must explain its actual deletion controls and any separate account, cloud, or backup deletion process. Uninstalling an app should not be assumed to delete server-held information or device backups.
8. Security and Processing Locations
We take reasonable steps to protect personal information against unauthorized access, loss, misuse, or disclosure. These steps must be appropriate to the information and services involved. No method of internet transmission or electronic storage is completely secure, and we cannot guarantee absolute security.
Information may be processed where we or our service providers operate, which can include locations outside your state or the United States. Any applicable legal requirements for such processing must be observed. We do not represent that United States-only availability means United States-only hosting or storage.
9. Children's and Minors' Privacy
Our services are not specifically directed to children under 13. HomeKeep and ReturnRadar are intended for adults. StormLine is not specifically designed for children under 13; its store content rating and target-audience declarations are separate from this privacy statement.
We do not knowingly collect personal information from children under 13 in violation of applicable law. If you believe that a child under 13 has provided personal information through our services, contact support@nalairos.com. When we learn that such information has been collected without required authorization, we will take appropriate steps to delete it or otherwise handle it as required by law.
10. Links to Other Websites and Platforms
Our website or applications may link to services operated by other companies. Their handling of information through their own sites or platforms is explained in their privacy notices. A link does not make their service part of Nalairos.
Where an app is distributed through Google Play or Apple's App Store, the platform's own privacy terms govern its platform activities. This does not replace our responsibility to disclose information handled by the app itself, its included code, or providers acting for us.
11. Changes to this Privacy Policy
We may update this policy when our services, practices, or legal obligations change. We will post the revised policy and update the date at the top. For material changes, we will provide additional notice and obtain consent where required before applying the changed practice.
New products or features will be covered by updated, specific disclosures rather than an assumption that this policy already describes every future activity of Nalairos LLC.
12. Application-Specific Privacy Notices
REVIEW STATUS: The RecordKeep: Home and ReturnRadar notices describe the audited Android releases identified below. StormLine reflects a static review of the identified Android bundle; runtime testing and the remaining storage and deletion checks are pending. These findings do not establish the practices of other versions or platforms. Resolve the remaining website and StormLine review instructions before publishing this draft as a finished policy for all listed services.
RecordKeep: Home
Operator: Nalairos LLC, including the developer names Nalairos and Nalairos Labs.
Intended audience: Adults.
Release covered: RecordKeep: Home for Android, version 1.1.0, build 10038 (com.nalairoslabs.recordkeephome). This notice covers that Android candidate. The iOS build has not yet been signed or distributed; these Android findings do not establish iOS permission, storage, backup or platform behavior.
Local use and accounts. RecordKeep: Home uses information you enter or select to organize your home, maintain records and history, search saved information, and provide reminders. It has no app account or sign-in system, bank connection, household-data server or automatic household cloud synchronization. No advertising integration, product-usage analytics service or app-configured remote crash-reporting service was found in the reviewed application code. This version includes Google Play Billing and related Google libraries. Store and platform processing, and the external actions described below, mean that local household storage is not a claim that no information ever leaves the device.
Information you save. RecordKeep: Home stores home names and types, ownership type, systems and notes; appliance details, including model and serial numbers, purchase amounts, retailers and warranties; maintenance schedules, completion dates, costs and notes; and bills, amounts, due dates and paid dates. It also stores service-provider names, phone numbers, email addresses, websites and notes. These contact details come from information you enter, rather than access to your device contacts.
Attachments and preferences. The app keeps copies of the photos and documents you select, together with their original filenames, labels, types, sizes and checksums used to identify file contents. It also keeps appearance and reminder preferences and a hash used to prevent duplicate reminders. Records are held in a private local database, attachments in private app files, and preferences in local app storage. RecordKeep: Home does not add application-level encryption to its database or files; protection also depends on your device. Saved records have no general automatic expiration period.
Permissions and reminders. RecordKeep: Home requests notification permission to show reminders and declares permission to reschedule them after a restart. Its background-work and included libraries also declare permissions for wake locks, network status and foreground services; an app-specific permission protects internal receiver communication. The final Android manifest includes Internet and Google Play Billing permissions. It does not request location, contacts, microphone, camera, broad photo or storage, or advertising-ID permission. Reminder notifications give Android a count and generic wording, without bill amounts or record titles, and use generic lock-screen text. You can dismiss or disable notifications.
Optional Pro purchases. Where configured and available, the one-time Pro unlock uses Google Play and your Google Play account. RecordKeep: Home requests product information and purchase status and sends purchase acknowledgements using a purchase token. Google handles checkout and payment through its store services. The app does not collect your Google password or payment-card details, and the app's billing calls do not include your household records, bill contents, attachments or saved provider contacts. There is no Nalairos purchase-validation server in this implementation. Google may process account, transaction, app, device and service-interaction information under its own terms and privacy practices. See Google's Privacy Policy (https://policies.google.com/privacy) and retention explanation (https://policies.google.com/technologies/retention).
Local purchase records and deletion. The Android app verifies Google's signed purchase response and stores that response and signature in private local preferences to support offline Pro access. These records include the purchase token, product/package identifiers, purchase status and other purchase metadata supplied in the signed response. The cache is updated when purchases are verified, cleared after a successful store query confirms no matching purchase, or removed with local app storage. It is not part of household backups or record exports. Restoring purchases recovers eligible Pro access, not your home records. Clearing app storage or uninstalling does not refund the purchase or erase Google's transaction records; Google controls retention and deletion of its copies. Purchase availability requires store configuration; build 10038 has not completed that setup.
Finding a provider. When you use Find a provider, RecordKeep: Home sends a generic trade query, such as "plumber near me," to a maps app, or to Google Search in a browser if the maps handoff is unavailable. The task title is classified locally. The outgoing query does not include the original title, notes or saved contact details. The maps or search service controls its own handling, retention and deletion of that query.
Selecting, taking and opening files. Android photo and document pickers supply files you choose, and taking a photo opens a separate camera app. RecordKeep: Home does not request account credentials for these actions. When you open an attachment, the chosen viewer receives read access to that file and can read its contents. Imported files are copied without stripping embedded photo or document metadata. Camera apps, file providers and viewers may have their own accounts, cloud services or uploads. RecordKeep: Home cannot control copies or later uploads made by those applications.
Backups and exports you create. RecordKeep: Home writes backups and exports to the location or provider you choose through the Android file picker. A cloud destination receives the exported contents. Full backups include records and attachment contents; JSON exports include records and attachment metadata; CSV exports include maintenance history, including costs, provider names and notes. Optional Pro PDF item/service reports contain the displayed item details and the history and additional fields you select. Serial numbers, costs, notes and provider details are excluded by default; reports do not include attachment contents or bills. Review the preview before exporting or sharing. RecordKeep: Home does not encrypt these outputs. They remain at the destination until deleted separately, and provider trash or version history may retain additional copies. Importing a backup creates a copy in this app; it does not delete the source backup or data held by a previous installation.
Removing attachments and temporary files. Remove file deletes the attachment database entry and attempts to delete RecordKeep: Home's private copy. A failed file deletion can leave that copy behind. The original file and copies held by viewers or in exports are unaffected. RecordKeep: Home does not enforce a 24-hour retention limit for orphaned attachments or camera files. Temporary backup and restore files normally have cleanup paths, but an interrupted process can leave them behind, with no confirmed automatic startup cleanup.
Deleting other records. Deleting a provider removes the saved contact, but past maintenance completions retain historical contact details, including phone numbers, email addresses, websites and notes. Archiving items or disabling tasks retains their data. This release has no general in-app Delete all data control and no individual deletion control for bills or completion history. Use Android's Clear storage control or uninstall the app to remove its local app storage. Original files, exports, external backups and copies held by other apps require separate deletion. These actions are not a guarantee of secure forensic erasure.
Android backups and transfers. RecordKeep: Home disables Android app backup. Some device manufacturers may still allow device-to-device transfers, and this release has no explicit device-transfer exclusion rules. The backup setting therefore does not establish that a device or external tool can never make another copy.
Fonts, store libraries and diagnostics. An enabled AndroidX emoji component can request an emoji font from a system-installed provider, potentially Google Play services. Its actual network activity, transmitted metadata and retention on a particular device have not been verified. The Android build includes Google Play Billing 9.1.0 and related Google libraries, including DataTransport components. Inclusion of a library or a permission does not establish which diagnostic information it actually sends. Background-work logging and Android diagnostic and profile-installation components are also present. No application-level logging of private household records or app-configured remote crash-reporting uploader was found in the targeted review. Actual SDK traffic, system-log contents, retention, and Google Play, Android or device-manufacturer crash and usage reporting have not been measured for this candidate. These services and the external apps described above can have their own network, retention and deletion behavior.
[RECORDKEEP: HOME PUBLICATION CHECKS: Confirm the final distributed binary, Google Play Billing and included SDK data handling, purchase configuration and store privacy disclosures. Do not reuse the previous release's claims of no Internet permission or no billing integration. Complete a separate iOS release privacy review before treating this Android notice as coverage of the iOS app. This revision does not establish runtime zero collection or transmission.]
ReturnRadar
Operator: Nalairos LLC, including the developer names Nalairos and Nalairos Labs.
Intended audience: Adults.
Release covered: ReturnRadar for Android, version 1.0.0, build 212894532 (com.nalairos.returnradar). This notice describes that Android release. An iOS release and its device behavior, including backup handling, have not been verified; these Android findings do not establish iOS practices.
Local use and accounts. ReturnRadar uses information you enter or select to track purchases, return deadlines and refunds. The release review found no account or sign-in system, advertising or analytics SDK, remote crash-reporting service, cloud synchronization, or application network endpoint. No application-controlled remote collection was found in this Android release. Receipt text recognition (OCR) is not enabled. Camera apps, photo providers and platform services may independently handle information as described below.
Purchase and refund information. A local SQLite database stores product and store names, prices and currencies, purchase and deadline dates, status, free-text notes, refund amounts, dates and status, and generated record identifiers and timestamps. Records have no automatic expiration period and persist until deleted or local app storage is removed. ReturnRadar does not add application-level encryption to this database; protection also depends on your device.
Receipt and product photos. Images you select are copied into ReturnRadar's private app storage. The database records which purchase an attachment belongs to, its type, file identifier, order, size and timestamps. Personal information visible on a receipt remains in the image. ReturnRadar copies image contents without its own metadata-removal step, so saved images may retain embedded metadata, such as EXIF data, even though the picker is configured not to request full metadata.
Permissions and photo providers. The release requests notifications, boot completion and vibration permissions, plus an app-specific permission protecting internal receivers. It does not request Internet, camera, microphone, location, contacts, account access, or broad photo or storage access. Taking a photo uses a separate camera app; selecting an existing image uses a system picker. The release includes support for Google Play services to provide the Android Photo Picker on older devices. That configuration is not evidence of uploading purchase data. Camera apps and cloud-backed photo providers may use their own accounts or network services, whose recipients and retention have not been verified through this app audit.
Reminders. ReturnRadar reads the device timezone and notification permission state, and stores reminder preferences, schedules and purchase identifiers locally. Global reminders are off by default. When reminders are enabled, Android's notification system receives schedules and a purchase-identifier payload. Visible notification text is generic and excludes merchant names, product names and prices. Schedules are updated when preferences or purchases change. You can control reminders in the app and through Android notification settings.
Backups and transfers. This Android release disables app backup and explicitly excludes app files, databases and preferences from its configured cloud-backup and device-transfer paths. ReturnRadar has no app-operated cloud storage implementation. These settings do not verify the behavior of every device manufacturer or external backup tool, or establish that no platform-managed copy can exist.
Deleting purchases and attachments. Deleting a purchase removes its purchase, refund and attachment database rows, queues cleanup of the associated image files, and updates notification schedules. You can also remove individual attachments. Failed file deletion can leave image contents behind; recovery retries cleanup, but there is no guaranteed completion deadline. Original photos outside ReturnRadar are not deleted. This release has no in-app Delete all data control.
Temporary copies and broader removal. The image-picker component creates separate cache copies that can retain original filenames and outlive attachment deletion. ReturnRadar's attachment cleanup does not purge that picker cache, and the app enforces no deadline for its removal. Android's Clear cache control can remove cache files more broadly; Clear storage removes local app data, and uninstalling removes the app's local storage. These controls do not delete original photos or external backups and copies. Database and file deletion are logical removal, not verified secure erasure of database or filesystem remnants.
Diagnostics and platform behavior. No app-configured remote diagnostic uploader was found. Native components can write local error logs, including image-picker file references and notification scheduling errors. Log retention and inclusion in device or manufacturer diagnostics are outside the inspected app controls. Google Play, Android and device manufacturers may independently perform crash or usage reporting. The audit did not include device traffic capture or Play Console inspection and did not establish the recipients, retention or deletion practices of these platforms or the external camera and photo-provider services.
StormLine
Operator: Nalairos LLC, including the developer names Nalairos and Nalairos Labs.
Intended audience: Not specifically directed to children under 13; store ratings and target-audience declarations remain separate decisions.
Release reviewed: The Android release bundle named StormLine-0.1.0.aab. The review covered this local release artifact, its dependencies, relevant app code and Unity project settings. It did not include a runtime traffic test on a device and does not establish the behavior of a future Play-distributed build or an iOS release.
Gameplay and local information. StormLine handles gameplay state locally and has no account or cloud-save feature in the reviewed app code. Installed release files also contain build identifiers. The review found no evidence that these build identifiers leave the device. The precise saved gameplay fields, storage locations and retention controls still require confirmation, as noted below.
Network access. The reviewed Android release does not declare Internet permission, and no app-authored networking calls were found in its gameplay scripts. No runtime transmission to a third party was confirmed, and no recipient or transmission purpose was established. These findings do not prove that all transfers through engine, native-code or Android system channels are impossible. Network behavior during launch, gameplay and background or resume activity has not been tested.
Unity services and included libraries. Unity Analytics, Ads, in-app purchasing, Cloud Diagnostics and Insights are disabled in the reviewed project settings, and the project is not linked to Unity Cloud. The release dependency review found no Google Play services, Firebase, advertising or measurement libraries. The game includes Unity and AndroidX components. The presence of analytics or networking module names in Unity engine files does not establish that those services are active or that information is transmitted.
Hardware statistics and diagnostics. A Unity build setting permits hardware or device-statistics reporting at the configuration level, although the reviewed analytics and diagnostic services are disabled and the project is not linked to Unity Cloud. The actual runtime device-statistics flag was not read from this bundle, and possible native-code network attempts were not tested. The review did not establish that StormLine sends hardware statistics, diagnostics or identifiers to Unity or another recipient. It therefore does not establish a recipient's retention or deletion practices for such data.
Deletion. The reviewed app has no in-app deletion control. Uninstalling clears the app's local sandbox. This does not establish removal of copies outside that sandbox or verified secure erasure. Saved gameplay details, retention periods and backup or device-transfer behavior remain to be verified before this notice is finalized.
[STORMLINE VERIFICATION PENDING: Static release-artifact review is complete for the supplied scope. Test the reviewed release during launch, gameplay and background/resume; verify the runtime device-statistics setting; confirm all saved data, purposes, storage locations, permissions, retention, deletion and backup/transfer behavior; and verify that the distributed release matches the reviewed artifact. Do not turn unconfirmed transmission into a claim of zero collection or transmission. Review any iOS release separately. The proposed hardware-reporting setting change has not been made or verified.]
13. Contact Us
For questions about this policy or requests concerning your personal information:
Nalairos LLC
Developer and publishing names: Nalairos and Nalairos Labs
Business location: Largo, FL 33770, United States
Email: support@nalairos.com
