Back to pilot access

Intunement pilot

Privacy Notice

Intunement is local-first. Readable reflections, Archive history, Trace, and Conditions stay in this browser by default. In this lean pilot, only an explicitly chosen Guided Reflection sends reflection content to an external service.

Effective October 30, 2026 · Version 2026-10-30

The short version

  • Intunement does not sell personal information or use reflection content for advertising.
  • This pilot does not use PostHog or other product analytics.
  • Redis stores access-code records, limits, counters, and operational metadata—not reflection text.
  • Only Mirror Guided Reflection uses AI. It explains what will be sent before you choose it; Trace and Conditions do not use AI.
  • You can use Mirror without AI, export your local archive, delete local entries, and leave the pilot.

Who operates Intunement

Intunement, including the Mirror, Trace, and Conditions practices, is offered by Pragmatic Artistry Collective. The contact address at the bottom of this notice is the current path for privacy questions and requests.

What stays in your browser

By default, readable Mirror reflections, Guided Reflection transcripts, titles, tags, locally calculated patterns and constellations, Trace and Conditions views, preferences, and content-free AI consent receipts are stored in the browser you use. Anyone with access to that unlocked browser may be able to see them.

This information stays until you delete it, clear browser storage, or the browser removes it. It does not automatically follow you to another browser or device.

A local encrypted backup is a file created on your device. Intunement does not upload that file in this pilot. You control where it is stored and whether it is restored.

What Intunement processes for pilot access

When you enter a pilot code, Intunement processes a pseudonymous code identifier and label, a randomly generated browser access identifier, a signed access-session cookie, and ordinary request and security metadata. Your IP address may be used temporarily to limit repeated access attempts, but is not added to the successful-entry record described below.

  • The access session normally expires after 30 days.
  • Failed-attempt rate-limit records expire after 10 minutes.
  • Browser-redemption records expire after up to 180 days.
  • For an individual pilot code configured for access tracking, an accepted entry creates a record containing its pseudonymous identifier, a successful-entry count, and the first and most recent recorded acceptance times. Tracking does not reconstruct earlier code entries. The record expires 400 days after its most recent accepted entry.
  • A version, timestamp, and pseudonymous code identifier may be retained for up to 400 days as evidence of pilot-notice acknowledgement.

Successful-entry records do not contain the secret code, reflection content, name, email, IP address, browser identifier, or device details. The pilot team may separately know which invited tester received a code label.

No product analytics in this pilot

Intunement does not use PostHog, session replay, heatmaps, behavioral product analytics, or advertising trackers in this pilot. Vercel hosts the application and may process ordinary request, security, and operational information as part of providing that infrastructure. Intunement does not intentionally place reflection text or other private writing in hosting logs.

When material leaves the browser

  • Mirror Guided Reflection: What you deliberately submit, the recent turns needed to continue the conversation, and only the Earlier Context excerpts you select are sent to OpenAI after explicit consent. Intunement sends Responses API requests with store: false. OpenAI says API data is not used for model training by default, though abuse-monitoring data may be retained for up to 30 days.
  • Pilot access and limits: Access-code records, pseudonymous usage counters, acknowledgement records, and operational limit metadata are stored in the pilot’s isolated Redis database. Reflection text, titles, transcripts, and selected Earlier Context are not stored there.
  • Export and encrypted backup: These actions create files on your device. What happens to a downloaded file is under your control.

Deleting local content cannot retract material already processed in a completed AI request or a file you already downloaded.

Service providers

Intunement uses Vercel for hosting, Upstash Redis for pilot access and usage limits, and OpenAI only for deliberately chosen Mirror Guided Reflection requests. These providers operate under their own infrastructure, security, and legal obligations. Intunement limits the information sent to what the selected function needs.

This lean pilot does not use Supabase accounts or storage, Connected Archive cloud sync, Mirror With shared rooms, cloud backup, cloud feedback storage, PostHog, an application email or invitation service, or payment processing.

Retention and deletion

  • Browser-local material remains until you delete it or browser storage is cleared.
  • Downloaded exports and encrypted backups remain wherever you save them until you delete them.
  • Failed-attempt rate limits normally expire after 10 minutes, browser-redemption records after up to 180 days, and successful-entry and notice-acknowledgement records after up to 400 days as described above.
  • Daily and monthly AI counters expire with their applicable usage window.
  • Vercel, Upstash, and OpenAI retain operational information under their configured settings and legal obligations.

Contact the pilot team to ask about access, correction, or deletion of server-held pilot access and usage information. Clearing or deleting server-held records does not erase browser-local material; you control that material in the browser or downloaded files.

Your controls

  • Use Solo Reflection without AI.
  • Review what an AI action will send before choosing it.
  • Export an encrypted archive and delete individual local entries.
  • Clear Intunement’s local browser storage.
  • Decline Guided Reflection and use the browser-local practices without AI.
  • After entering Intunement, review detailed controls on the Privacy & Data page. If you do not want to accept the current terms, you may still contact the pilot team below to leave or request deletion of server-held access information.

Security and shared devices

Intunement uses signed pilot sessions, same-origin checks for sensitive changes, local encryption for downloaded backups, and restricted server access. No system is perfectly secure. Protect your access code, backup passphrase, device, browser profile, and downloaded files.

Adults and changes

The live pilot is for adults aged 18 and older. Intunement versions this notice. If a material change affects what information moves, why it is used, or who receives it, Intunement will present the updated notice before continued use.

Related terms

The Pilot Terms explain participation, individual access, and the experimental nature of the service.