Privacy

Private formation deserves more than vague promises.

This page is a product draft describing the privacy direction Heeded intends to follow. It should be reviewed by qualified counsel and aligned with final production behavior before public launch.

Information Heeded may handle

Heeded may handle account information, profile information, product preferences, Life Areas, seasons, goals, projects, commitments, rhythms, Journey progress, Fellowship progress, Journal content, Vault content, Group content, messages, Community activity, support communications, device information, security logs, and billing-related records when those features are used.

Why information is used

Information may be used to provide and secure the service, preserve progress, personalize the experience, operate Community and Groups, deliver messages, process support requests, prevent abuse, improve product quality, and meet legal obligations.

Journal and Vault

Personal writing should be treated as private product data. Heeded should not repurpose Journal or Vault content for advertising. Any feature that allows AI to read private writing should make that behavior clear and remain off until you choose it.

Public, shared, and private

Public profile information, shared Community content, private Journal material, private messages, Group content, and Vault material should not be treated as one permission class. Private by default. Shared by intention.

Your choices

Members should be able to update profile information, manage product preferences, control communication settings, and request account deletion subject to legal, security, fraud-prevention, billing, and operational requirements.

This page is a product draft. Final legal language should be reviewed by qualified counsel before public launch.