Privacy Policy

1. What We Collect

When you use Our Block, we collect:

• •Account information — email address, name, and account identifiers (via Clerk authentication).
• •Submissions — resident questions, concerns, and answers you write or approve on the platform.
• •Activity logs — records of actions taken (approvals, publishing, status changes) with timestamps.
• •Postal or zip code — if you enter one at onboarding to find the project for your area. It is used for that lookup only and is not stored.
• •Invitations — when a consultant invites a colleague to a project team, the email address they enter is kept on the invitation record, shown to that project's consultants, and noted in the activity log, until the invitation is used, expires, or is revoked.

2. Account Data: Clerk Authentication

Our Block uses Clerk for authentication. Your email, name, and unique Clerk user ID are stored by Clerk and referenced in Our Block's database. Clerk is a third-party identity provider. For details about how Clerk handles your data, see the Clerk Privacy Policy.

3. Resident Submission Data

When you submit a concern or question on Our Block, the text is stored in the platform database (Neon PostgreSQL) and associated with your account. By default, submissions are private and visible only to you and the consultant team. If a consultant publishes your thread to the community, other registered residents can then read it.

4. AI Processing: Embeddings and Drafting

When drafts are generated or instant answers are enabled:

• •Embeddings (Voyage AI) — Resident concern text is sent to Voyage to generate a vector embedding for similarity matching. Voyage processes your text to produce a mathematical representation.
• •Drafting and verification (Anthropic Claude) — When a consultant generates a draft answer, the resident's question and project knowledge-base excerpts are sent to Anthropic's API (using the Claude model) to generate suggested text. When instant answers are enabled for a project and a resident's new question closely matches a previously approved answer, the question and that approved answer are also sent to Anthropic automatically, to check whether the approved answer actually addresses the question; only a "yes" allows the approved text to be shown. Anthropic may log usage for system monitoring and abuse prevention (see the Anthropic Privacy Policy).

These calls are made only when:

• -A consultant explicitly clicks "Generate draft".
• -Instant answers are enabled for the project and a resident submits a new concern (embedding on every submission; the Anthropic verification check only when a close match is found).

You should be aware that your concern text is shared with these external services when these features are used. Consult the privacy policies of Voyage AI and Anthropic for details on how they handle your data.

5. Email Notifications

Our Block uses Resend (an email service provider) to send notifications to consultants and residents. Email notifications include:

• •The concern or answer title.
• •A link to the platform.

The full concern text is never included in an email to protect privacy. Invitation emails to people a consultant invites carry the project's name and a one-time link to join its team. Resend processes email addresses and delivery information. See the Resend Privacy Policy for details.

6. Audit Logging

Our Block records audit events for every state change: approvals, publishing, status transitions, and membership changes. Each audit event includes:

• •Who took the action (consultant or resident).
• •What changed (before and after values).
• •When the action occurred.

These records are retained indefinitely to ensure accountability and transparency. Audit logs are not deleted even if the related concern or answer is removed.

7. Data Retention and Deletion

Your account data and submissions are retained for the life of the project. There is currently no self-service deletion; requests should go to Mandate support, and audit records and published threads may be retained for legal or regulatory reasons.

8. Access and Control

You can access your own submission history by logging in. Residents cannot see other residents' submissions unless the consultant chooses to publish them. Consultants can see all submissions in their project and control whether a thread is published to the registered community; a published thread can be made private again. Submitted text itself is not edited or deleted by consultants.

9. Security

Our Block is hosted on Vercel and uses industry-standard encryption for data in transit (HTTPS). The database is encrypted and access is restricted to authorized personnel and application code. However, no system is completely secure, and we cannot guarantee absolute protection against unauthorized access.

10. Changes to This Policy

This privacy policy may be updated. Continued use of Our Block after changes indicates your acceptance of the updated policy.

11. Contact

If you have questions about this privacy policy or how your data is handled, contact the consultant team or Mandate support.