Neestor

Privacy Policy

Effective date: 2026-09-09

This Privacy Policy describes how Neestor processes personal information in the closed beta. It reflects the current product and is not a substitute for legal counsel or final store declarations. Counsel review is required before any public store release.

Who we are

Neestor is a personal LifeOS assistant. You capture tasks, events, reminders, and routines in natural language by text or voice. Items you confirm on a Smart Card are scheduled and may trigger notifications.

Neestor separates an Application plane (operational state) from a Vault plane used for certain sensitive place data, such as addresses.

Information we process

Account and authentication: email address and authentication identifiers via Amazon Cognito, plus access tokens used to call the Neestor API.

Captures and interpretations: text you type; voice audio and/or a speech transcript; and proposed Structured Intents (subject, times, recurrence, and similar fields) before and after Smart Card confirmation.

Operational Application data after confirmation may include tasks, events, reminders, routines, schedule state, Expo push tokens, and non-sensitive place references (placeRef), not full address payloads.

This beta does not process payments, health records as a product category, document uploads, or third-party analytics SDKs beyond the services described below.

Application and Vault

Confirmed operational objects live in the Application account. Address, geo, and place labels for places you save are stored in the Vault, not in the Application database.

Vault access requires purpose and privacy-scope headers over a private network path (AWS PrivateLink).

Voice

The microphone is used only when you start voice capture. Audio or a transcript may leave the device and be sent to Neestor’s API for speech-to-text (STT) and interpretation.

Raw audio is not stored as memory. Transcription is ephemeral unless you confirm a Structured Intent into a domain object. We do not claim that voice remains entirely on-device.

How we use information

We use information to provide the service (interpret captures, confirm intents, schedule reminders, send notifications), to support safety and abuse prevention, to operate and debug with minimized telemetry, and to administer accounts.

We do not sell personal information. When AI interpretation is enabled, only a minimized context scope is sent to the model—not full memory dumps.

Third-party services and AI

Depending on configuration, data may be processed by Amazon Cognito (authentication), Amazon Web Services such as Lambda, DynamoDB, API Gateway, and PrivateLink (API, storage, networking), Expo Push (mobile notifications), and speech-to-text providers.

Optional natural-language interpretation may use AI interpretation providers configured for the environment, such as Amazon Bedrock. OpenAI or other providers may be added later if configured for that environment.

Notifications and telemetry

Push notifications are delivered via Expo Push with minimized title and body content. Content is screened by a Presentation Guard before delivery.

Diagnostics use operational logs and metrics. Sensitive payloads are omitted or redacted by default.

Retention and deletion

Rejecting an interpretation leaves no domain object. Unconfirmed interpretations are not persisted as domain objects.

Confirmed domain objects remain until you delete them in the app or otherwise request deletion. Deleting a domain object cancels related pending schedules. Vault place records follow Vault retention rules; the Application keeps only references.

Exact production retention periods will be finalized before a public store release.

Your controls

In this beta you can confirm or reject Smart Card interpretations, browse and delete domain objects, enable or deny notification and microphone permissions, and sign out (which unregisters push for the current device when implemented).

Export and full account deletion workflows will be completed before public release.

Children

Neestor closed beta is not directed at children under 13, or the age required in your jurisdiction. Do not use the beta if you are under that age.

International processing

Closed-beta infrastructure is hosted in AWS, currently in the us-east-1 region. If you use the beta from another country, your data may be processed in the United States.

Changes

We will update this policy when processing changes materially. The effective date above will change. Closed-beta users should review the in-app or website Privacy Policy before continuing with new builds.

Contact and legal notice

Privacy questions or requests: privacy@getneestor.com.

This document describes closed-beta behavior only. It is not legal advice. Independent counsel review is required before any App Store or Play Store release.