Privacy policy | Civitas

CIVITAS PRIVACY POLICY

Original version 1.0 — Effective Date: January 1, 2025

Factual clarification: October 4, 2026. This clarification does not replace existing agreements or remove published rights. The current collection descriptions below distinguish the Marketing website from separate account software; they do not establish hosted configuration, completed consent or legal approval.

1. INTRODUCTION

Civitas LLC ("Civitas," "we," "us," or "our") respects your privacy and is committed to protecting your personal information. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform.

2. CURRENT COLLECTION AND BROWSER STORAGE

Marketing enquiries and contact drafts

The Marketing enquiry form sends your name, email, optional organization, role and jurisdictions, enquiry type and message to Civitas when you submit it. The endpoint stores the submitted enquiry, its source page, any supplied campaign attribution, and the collection notice shown on the form. The confirmation states whether storage succeeded and how many acknowledgement or founder-notification emails were queued. Queueing does not confirm email delivery. Lead retention is under review; no automatic deletion period is active. The collection notice is not an approved legal consent version.

The separate email-draft form uses your name, email, optional organization, topic and message and prepares an email draft in your browser. You choose whether to copy the text or send it through your email application. Preparing that draft does not submit it to Civitas. After you send, your email application and mail provider handle that message; their delivery and retention are outside this website's draft behavior.

Browser storage

The Marketing website keeps your light/dark theme preference in local storage. The reviewed Marketing source does not contain an analytics sender; this does not establish what hosting logs or injected services collect.

Separate account software includes an authentication handoff cookie and browser token storage. Some authentication data is readable by browser JavaScript. The Auth/App source also contains preference and per-tab entitlement storage and entrypoints that can request external font, library or payment resources. These source findings do not establish which entrypoints, cookies or external resources are currently served, or a verified list of vendors receiving data.

Account registration asks for email, password and password confirmation. Account and workspace features can process additional account or work data. This bounded notice is not a complete inventory of every feature or server-side record. Applicable consent and live vendor configuration remain under review.

3. PURPOSES AND PILOT SCOPE

The intended paid pilot supports legislative work and account/team workflows. Submitted enquiries are stored for handling by an authorized operator. Contact drafts help you prepare a question; theme storage remembers your reading preference. Authentication storage supports account sign-in and the handoff between separate account surfaces.

Earlier contribution-processing and contribution-reporting descriptions do not describe paid-pilot collection. This correction does not assert that the pilot collects citizenship, date-of-birth or FEC contribution fields, processes political contributions, or sends contribution reports to the FEC. Additional product, provider and hosting collection must be established against the actual offered and served service.

Submitted enquiries can create queued acknowledgement and founder-notification emails through the existing delivery system when routing is configured. This source behavior does not verify a monitored mailbox or hosted provider delivery. The prepared contact draft can pass to your chosen email application, mail provider or clipboard when you choose those actions. Account software can request external resources; the source inventory does not verify current vendor processing, contracts or settings. It also does not verify hosting/CDN logs, injected tracking or their retention.

The no-sale statement and sections 5–10 below are retained existing policy commitments. They are not a fresh verification of deployed security, retention, transfer or consent behavior. Contribution-record wording in retained section 7 concerns historical language and does not establish collection or a new retention rule for the paid pilot. Review of their application remains open.

We do not sell your personal information to third parties.

5. YOUR RIGHTS

Depending on your jurisdiction, you may have rights including:

GDPR (European Union):

Right to access, rectify, or erase your data
Right to data portability
Right to object to processing
Right to restrict processing
Right to withdraw consent

CCPA (California):

Right to know what personal information is collected
Right to delete personal information
Right to opt-out of sale of personal information
Right to non-discrimination

6. DATA SECURITY

We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.

7. DATA RETENTION

We retain your personal information for as long as necessary to fulfill the purposes outlined in this Privacy Policy, unless a longer retention period is required or permitted by law. FEC compliance requires us to maintain contribution records for at least 3 years.

8. CHILDREN'S PRIVACY

Our Service is not directed to individuals under 18 years of age. We do not knowingly collect personal information from children under 18.

9. INTERNATIONAL DATA TRANSFERS

Your information may be transferred to and processed in countries other than your country of residence. We ensure appropriate safeguards are in place for such transfers.

10. CHANGES TO THIS PRIVACY POLICY

We may update this Privacy Policy from time to time. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Effective Date."

11. CONTACT US

If you have questions about this Privacy Policy, please contact:

CIVITAS LLC

Existing privacy contact: [email protected]

You can also submit an enquiry or prepare an email draft. A submitted enquiry receives a server-confirmed storage receipt; a prepared email draft still requires you to send it. Mailbox monitoring, operator response and hosted delivery remain unverified; no response deadline or designated representative is asserted here.

12. SPECIFIC JURISDICTIONS

California Residents (CCPA):

Use the existing privacy contact in section 11. The rights described in section 5 remain subject to your jurisdiction; this source correction does not establish applicability or completed request handling.

EU/EEA Residents (GDPR):

No DPO or EU-representative identity has been verified for this correction. The original privacy contact above is retained without asserting a designated role.

You have the right to lodge a complaint with your local supervisory authority.

Original policy last updated: January 1, 2025. The factual clarification above is dated separately. A prospective replacement policy remains under review.