Privacy Policy

• Account info: email, name, role (CEO / COO / Lead / Member), company assignment.
• Content you author in-product: chat messages, task descriptions, decision dialogues, feedback, smoke-test notes.
• Behavior on the platform: which buttons you press, which messages you pin, which tasks you complete steps on. The record is append-only so we can reason over patterns, not just snapshots.

• Engagement signals (last meaningful action on a task, participation in topics, response patterns).
• Communication grades — when the Coach is on, every sent message gets a grade (productive / neutral / needs-guidance / withheld). This is the encouragement system; you see your own grades, and your leader sees aggregate patterns framed as "Requesting Collaboration", never as a verdict on you.
• Cross-conversation memory — the Coach reads patterns of what it's already coached you on so it doesn't repeat the same lesson. The memory window is 30 days.

• We do not infer your emotional state from typing patterns, late-night activity, or absence. The System reads what you show it. It does not read what it guesses about you.
• We do not sell your data. Ever. We don't share with advertising platforms or data brokers. If we did, we wouldn't be ELOSTATE.
• We do not surface a verdict labeled as your performance. The labels we ship to leaders are deliberately framed as invitations to help, never as ratings on the person.

• You can see everything attributed to you, including the same data that appears in admin digests about you.
• Other members of your companycan see shared content in topics they participate in and on tasks they're part of. Row-level security at the database layer prevents cross-topic / cross-company reads.
• Your company admins (CEO / COO / admin role) can see all topics and tasks within the company, plus the readout. They see the same underlying per-person data you see about yourself; nothing extra.
• We (ELOSTATE)can technically see everything via service-role access for support purposes. We don't routinely. In a future build we'll add audit-logged admin-access events so even our access is on the record.
• Nobody else sees your data. No third parties, no analytics platforms.

• Supabase— primary database and auth. Hosted in Supabase's data centers under their security posture.
• Vercel — application hosting and edge delivery.
• Anthropic Claude— the LLM behind the Coach. Your draft text passes through Anthropic's API to generate Coach analysis. Anthropic does not train on API content per their commercial terms. We do not send any data through Anthropic that you haven't already authored in the product.
• Web Push / VAPID for notifications — browser-native, no third party in the message path.

• We can REDACT your personal identifiers (email, name, user id) from past records. The structural events remain so the System's reasoning over time stays intact, but they no longer trace back to you personally.
• Aggregate counts that include your contributions stay as aggregates — they're not personally identifiable.
• For deletion that requires removing structural events (rare; usually a compliance obligation), contact us and we'll discuss what's legally required vs. what the system supports.

• Keep you signed in (Supabase auth session — a standard JWT).
• Preserve unsent drafts of Decision Dialogues so a browser refresh doesn't lose your work.
• Remember UI choices (theme, dismissed cards).

• See everything attributed to you, in-product.
• Export your own data — currently via product surfaces (My Feedback, task lists); a structured export endpoint is roadmapped.
• Request redaction of personal identifiers from historical records (see Retention section).
• Withdraw consent — close your account and request data redaction by emailing us.

Privacy questions go to johnsyramos@gmail.com. We answer real questions, especially uncomfortable ones.