Privacy Policy

NTHSTR is operated by Simple, LLC, an Arizona limited liability company. This policy covers data handled by the authenticated NTHSTR application and its related web, PWA, shortcut, and supported native capture surfaces. The public beta waitlist has a narrower, separate Beta waitlist privacy notice.

1. The short version

• Your workspace content remains yours; we do not sell it.
• Core account, workspace, and private source data is handled through Supabase.
• Vercel hosts and executes the application and receives normal request metadata.
• External AI processing is default-off and, if activated, is limited to Anthropic.
• Optional push, feedback, native capture, and billing paths apply only under the conditions below.

2. Data you provide

• Account data. Email address, authentication records, account identifier, and beta entitlement or invitation state.
• Workspace content. Tasks, appointments, projects, goals, habits and logs, notes, item relationships, collaborators, comments, review state, and other records you create in a workspace.
• Preferences and memory. Account and workspace display preferences, selected lenses, saved view state, source links, proposals, revisions, synthesis records, and the evidence needed to preserve provenance and reversibility.
• Captures and sources. NTHSTR can receive text, a voice transcript, a shared link or text, a contact card, an imported note, or an uploaded source through supported web, shortcut, share, or native capture seams. Native capture is an input path, not a separate data processor: accepted content is handled by the same NTHSTR service and Supabase controls described in this policy. A captured URL is not fetched merely because you shared it. Uploaded source objects use private Supabase storage buckets. Scanner, extraction, retrieval, outbox, and purge paths may be code-present while remaining default-off until separately activated.
• Feedback. The note, category, and bounded page or component context you choose to submit. NTHSTR stores a local receipt before an enabled Pinpoint forwarding path is attempted. If that path is enabled, NTHSTR also forwards the trusted client IP as X-Forwarded-For for Pinpoint's abuse and security controls. Raw DOM selectors and your account email are not forwarded to Pinpoint.
• Conditional billing data. Stripe billing is unconfigured and fail-closed in the current release. If activated later, Stripe receives checkout and payment data directly; NTHSTR stores bounded customer, subscription, event, and entitlement identifiers.

3. Data collected during operation

• Request and security metadata. IP address, user agent, route, timing, error information, rate-limit state, and other bounded operational data needed to deliver, secure, and diagnose the Service.
• Session data. Cookies and tokens used for authentication, CSRF protection, beta claims, and secure application state. We do not describe these as advertising cookies.
• Push subscription data. If you grant notification permission, NTHSTR stores the browser or device endpoint, subscription keys, and a bounded user-agent value needed for Web Push. Removing the subscription stops future NTHSTR sends to that endpoint.
• Processing evidence. When an activated job runs, NTHSTR can store bounded status, attempt, receipt, digest, provenance, citation, and recovery records so results are attributable and failures can be handled without silently losing captured material.

4. How we use data

• Provide authentication, workspace features, sync, preferences, and requested captures.
• Store and serve private sources and preserve provenance, revisions, and user decisions.
• Run an optional AI, push, feedback, or billing path only under its disclosed gate.
• Protect accounts and workspaces, enforce rate limits, investigate errors, and recover safely.
• Comply with applicable legal obligations and respond to valid rights requests.

Code-present processing, AI, scanner, outbox, sync, retrieval, and billing paths are not proof of activation. Where a path is default-off or unconfigured, NTHSTR does not describe it as processing user data unless the required activation and user action have occurred.

5. AI-assisted features

The rebuild contains local or mock behavior for ordinary testing and separately gated Anthropic adapters for some capture, structuring, and cited-answer features. A code-present adapter is not proof that an external provider is active. Anthropic receives data only when the applicable provider and product gate are enabled and you invoke the feature. No other AI provider is represented as active for rebuild user data.

6. Services and conditional processing paths

The table distinguishes core runtime infrastructure from paths that require a feature gate, configuration, permission, or deliberate user action.

7. Disclosure and sharing

We disclose data to the services above only as needed for the described function and gate. We may also disclose data when legally required, to protect users or the Service, or as part of a merger, financing, acquisition, reorganization, or sale of assets subject to appropriate notice and applicable law. We do not sell personal data or share it for cross-context behavioral advertising.

8. Retention and deletion

Workspace records are retained while needed to provide your account and preserve the history you choose to keep. Individual deletion, source-purge, and account-level rights can be subject to authorization, provenance, recovery, legal-retention, and backup constraints. Automated processing or purge code that is default-off is not represented as an active deletion schedule. To request access, export, correction, or deletion, contact privacy@simplellc.com.

Operational logs and backups can retain residual copies for their normal security and recovery cycles. We may keep limited records required for fraud prevention, legal claims, or legal, tax, and accounting obligations. Beta waitlist entries follow the separate retention terms in the Beta waitlist privacy notice.

9. Your rights and choices

Depending on where you live, you may have rights to access, correct, export, delete, restrict, or object to processing, and a right not to be discriminated against for exercising applicable privacy rights. We may need to verify your identity and may retain data when an applicable exception or legal duty requires it. Send requests to privacy@simplellc.com; we will respond within the period required by applicable law.

Optional notification permission, push subscriptions, feedback submission, and externally processed AI actions remain choices. Disabling a future path stops new use but does not erase records already needed for provenance, security, or a valid retention obligation.

10. Security

NTHSTR uses transport encryption, authenticated routes, workspace-scoped database controls, row-level security, private storage buckets, bounded signed URLs, hashed abuse identifiers, secret-redaction boundaries, and fail-closed activation checks where implemented. No system is perfectly secure. If an incident affects personal data, we will investigate and provide notices required by applicable law.

11. International transfers

Simple, LLC is based in the United States, and the services listed above may process data in the United States or other countries. Where applicable law requires a transfer safeguard, we will use an appropriate mechanism.

12. Children

NTHSTR is not directed to children under 13, and we do not knowingly collect their personal data. If you believe a child has provided data, contact privacy@simplellc.com.

13. Changes to this policy

We may update this policy as the product and its activation state change. We will revise the “Last updated” date and provide additional notice for material changes when required.

14. Contact

Privacy and rights requests: privacy@simplellc.com. Legal notices: legal@simplellc.com. General questions: info@simplellc.com.

Simple, LLC, an Arizona limited liability company — 7042 E Portland St, Scottsdale, AZ 85257.