<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Civitas</title>
    <subtitle>A clearer workspace for legislative work. Built for small teams doing serious public affairs work.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://www.civitas.ltd/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://www.civitas.ltd/"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-09-07T00:00:00+00:00</updated>
    <id>https://www.civitas.ltd/atom.xml</id>
    <entry xml:lang="en">
        <title>A better brief starts with three questions.</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/a-better-legislative-brief/"/>
        <id>https://www.civitas.ltd/blog/a-better-legislative-brief/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/a-better-legislative-brief/">&lt;h2 id=&quot;begin-with-the-reader&quot;&gt;Begin with the reader&lt;&#x2F;h2&gt;
&lt;p&gt;The person receiving a legislative update may not have followed every step that led to it. They need enough context to understand the significance without inheriting the full research process.&lt;&#x2F;p&gt;
&lt;p&gt;Before drafting, write down the decision or conversation the update is meant to support.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;what-changed&quot;&gt;What changed?&lt;&#x2F;h2&gt;
&lt;p&gt;Lead with the observable change. Identify the bill, jurisdiction, and source. Distinguish a new version of the text from a procedural action or a scheduled event.&lt;&#x2F;p&gt;
&lt;p&gt;Include the date relevant to the change. If you could not confirm something, say so. A reader should be able to tell the difference between the record and your interpretation.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;why-does-it-matter&quot;&gt;Why does it matter?&lt;&#x2F;h2&gt;
&lt;p&gt;Explain the connection to the team’s issue or the reader’s work. Avoid repeating the bill title in longer words. Ask what the reader would miss if they saw only the source record.&lt;&#x2F;p&gt;
&lt;p&gt;Keep this section proportional. Sometimes the useful interpretation is that a change needs review before a position can be settled.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;what-happens-next&quot;&gt;What happens next?&lt;&#x2F;h2&gt;
&lt;p&gt;End with a concrete next step. That might be another source check, a review of the text, or a discussion with the team. Identify who is responsible and when a follow-up would be useful.&lt;&#x2F;p&gt;
&lt;p&gt;Avoid creating a deadline that the source does not support. A team’s internal review date and an official hearing date are different things; label them accordingly.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;keep-the-evidence-close&quot;&gt;Keep the evidence close&lt;&#x2F;h2&gt;
&lt;p&gt;Link the original record and the relevant version. A colleague should be able to inspect the basis for the update without retracing your search history.&lt;&#x2F;p&gt;
&lt;p&gt;Software can help keep the material together. It cannot remove the need for careful review. That is why the relationship between record, context, and handoff is central to the &lt;a href=&quot;&#x2F;tour&#x2F;#brief&quot;&gt;Civitas workspace&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>A bill list is not a workflow.</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/a-bill-list-is-not-a-workflow/"/>
        <id>https://www.civitas.ltd/blog/a-bill-list-is-not-a-workflow/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/a-bill-list-is-not-a-workflow/">&lt;h2 id=&quot;start-after-the-bookmark&quot;&gt;Start after the bookmark&lt;&#x2F;h2&gt;
&lt;p&gt;Saving a bill is easy. Knowing what happens after you save it is the harder part.&lt;&#x2F;p&gt;
&lt;p&gt;A long list can look reassuring. It says the team has found a lot. It does not necessarily say which records matter, what needs a closer read, or who is preparing the update.&lt;&#x2F;p&gt;
&lt;p&gt;Before adding another column, ask what decision the list is supposed to support.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;give-the-list-a-job&quot;&gt;Give the list a job&lt;&#x2F;h2&gt;
&lt;p&gt;A useful working docket might support a weekly member update, a client briefing, or a small team’s review of hearing changes. Those are different jobs, with different thresholds for attention.&lt;&#x2F;p&gt;
&lt;p&gt;Write that job at the top of the process. Then keep the information that helps someone do it: the bill identifier, jurisdiction, source, relevant status, the person reviewing it, and the next action.&lt;&#x2F;p&gt;
&lt;p&gt;This is a working method, not a demand that every tool expose the same set of fields. The important part is that the team agrees on how the handoff works.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;make-the-next-action-concrete&quot;&gt;Make the next action concrete&lt;&#x2F;h2&gt;
&lt;p&gt;“Monitor” is a useful category but a vague instruction. “Check the committee agenda before the Monday update” gives someone a task they can finish.&lt;&#x2F;p&gt;
&lt;p&gt;Similarly, “important” tells you less than “review the latest amendment for the member briefing.” Keep the reason for attention close to the record.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;leave-room-for-uncertainty&quot;&gt;Leave room for uncertainty&lt;&#x2F;h2&gt;
&lt;p&gt;A source may be unavailable. A hearing may be tentative. Two versions of a document may need comparison. Do not turn an unknown into an apparently settled answer just to complete the row.&lt;&#x2F;p&gt;
&lt;p&gt;Name what still needs checking, and make that check part of the next action.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;end-with-the-handoff&quot;&gt;End with the handoff&lt;&#x2F;h2&gt;
&lt;p&gt;At the end of a review, another person should be able to answer three questions: what is this, why are we following it, and what happens next?&lt;&#x2F;p&gt;
&lt;p&gt;That is the difference between a collection of links and a working docket. &lt;a href=&quot;&#x2F;tour&#x2F;#track&quot;&gt;See how the Civitas interface approaches it.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Sometimes the useful answer is “nothing yet.”</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/honest-empty-states/"/>
        <id>https://www.civitas.ltd/blog/honest-empty-states/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/honest-empty-states/">&lt;h2 id=&quot;an-empty-screen-is-still-a-message&quot;&gt;An empty screen is still a message&lt;&#x2F;h2&gt;
&lt;p&gt;A blank notification queue can mean several things. Nothing happened. Nothing matched the rule. The source could not be checked. Delivery is still pending. Or no one has configured the workflow yet.&lt;&#x2F;p&gt;
&lt;p&gt;To the person using the product, those differences matter more than the color of the empty-state illustration.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;do-not-make-people-infer-the-system&quot;&gt;Do not make people infer the system&lt;&#x2F;h2&gt;
&lt;p&gt;A team should not have to work backward from an empty card to guess whether the software is working. The interface needs to explain what it knows and where that knowledge stops.&lt;&#x2F;p&gt;
&lt;p&gt;This is particularly important for legislative work. “No changes” can sound like permission to move on. “Source unavailable” asks for a different response.&lt;&#x2F;p&gt;
&lt;p&gt;A clear label will not repair an unavailable source. But it can prevent a person from mistaking a limitation for an answer.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;show-the-actual-state&quot;&gt;Show the actual state&lt;&#x2F;h2&gt;
&lt;p&gt;Our public tour includes an empty notification inbox and a search capture where ranked search is unavailable. Those screens are real development captures with example data.&lt;&#x2F;p&gt;
&lt;p&gt;They are included because those states are part of the product. A useful tour should show how a tool communicates limits, as well as how it presents a populated docket.&lt;&#x2F;p&gt;
&lt;p&gt;The screenshots are not evidence of live alert reliability or national coverage. Those require a different kind of verification, described on our &lt;a href=&quot;&#x2F;coverage&#x2F;&quot;&gt;coverage page&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;clarity-is-a-feature&quot;&gt;Clarity is a feature&lt;&#x2F;h2&gt;
&lt;p&gt;The standard is simple to say and demanding to meet: show what is known, what is missing, and what someone can do next.&lt;&#x2F;p&gt;
&lt;p&gt;That means an empty queue can be a good answer. So can a clearly explained error. What is not useful is a confident-looking screen that makes the person do the guessing.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;a href=&quot;&#x2F;tour&#x2F;#alerts&quot;&gt;Look at the notification workspace.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Less chasing. More doing.</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/less-chasing-more-doing/"/>
        <id>https://www.civitas.ltd/blog/less-chasing-more-doing/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/less-chasing-more-doing/">&lt;h2 id=&quot;the-tax-on-attention&quot;&gt;The tax on attention&lt;&#x2F;h2&gt;
&lt;p&gt;Open the legislature’s website. Find the bill. Check the action history. Look for the hearing. Copy the link. Find last week’s spreadsheet. Ask whether someone already sent the update.&lt;&#x2F;p&gt;
&lt;p&gt;Each step is small. Together, they can swallow the morning.&lt;&#x2F;p&gt;
&lt;p&gt;The real cost is not the clicking. It is rebuilding context. Every time the work changes hands, someone has to reconstruct what the team already knew. The useful question gets buried under the search for the latest version.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;a-better-starting-point&quot;&gt;A better starting point&lt;&#x2F;h2&gt;
&lt;p&gt;We want Civitas to make that context easier to carry. The bill record should sit near the working docket. The next action should be easy to find. A colleague should be able to pick up the thread without scheduling a meeting to ask where it went.&lt;&#x2F;p&gt;
&lt;p&gt;This is a modest ambition in one sense. It will not replace judgment, relationships, or the careful reading of legislation. It should make more room for them.&lt;&#x2F;p&gt;
&lt;p&gt;That distinction matters. Public affairs is not a contest to produce the largest stack of reports. It is the work of understanding what is happening and helping people respond.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;design-for-the-handoff&quot;&gt;Design for the handoff&lt;&#x2F;h2&gt;
&lt;p&gt;A useful way to judge a tool is to look at the moment work passes to someone else. Can they find the source? Can they see what changed? Do they understand the next step?&lt;&#x2F;p&gt;
&lt;p&gt;If the answer is no, another dashboard is unlikely to fix it.&lt;&#x2F;p&gt;
&lt;p&gt;Our first focus is the legislative workspace: the everyday relationship between records, a docket, and the team working through it. You can see the actual interface in our &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;useful-is-the-point&quot;&gt;Useful is the point&lt;&#x2F;h2&gt;
&lt;p&gt;We are not building toward a longer feature list for its own sake. We are building toward the moment a person closes the software because they have what they need.&lt;&#x2F;p&gt;
&lt;p&gt;Less chasing. More doing. That is a standard worth coming back to.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Show the product. Explain the limits.</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/show-the-product/"/>
        <id>https://www.civitas.ltd/blog/show-the-product/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/show-the-product/">&lt;h2 id=&quot;a-screenshot-should-answer-a-question&quot;&gt;A screenshot should answer a question&lt;&#x2F;h2&gt;
&lt;p&gt;What will I actually work with? Where does the bill list live? How does the workspace look when there are no notifications?&lt;&#x2F;p&gt;
&lt;p&gt;Those are reasonable questions to ask before a sales conversation. A product website should help answer them.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;real-screens-visible-context&quot;&gt;Real screens, visible context&lt;&#x2F;h2&gt;
&lt;p&gt;The Civitas tour uses unaltered browser captures from our September 2026 interface work. They show the actual application rendered with example data. They are not illustrations of an imagined future interface, and they are not live customer accounts.&lt;&#x2F;p&gt;
&lt;p&gt;We preserve the screen’s context, including source-status labels and empty states. Each image can be opened at full size so the interface can be inspected rather than treated as decoration.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;a-capture-is-not-a-coverage-report&quot;&gt;A capture is not a coverage report&lt;&#x2F;h2&gt;
&lt;p&gt;The presence of a bill in a screenshot does not verify a production data pipeline. A freshness number in example data does not establish how recently a live source was checked.&lt;&#x2F;p&gt;
&lt;p&gt;Likewise, a product area visible in the sidebar does not mean it is included in the planned legislative subscription.&lt;&#x2F;p&gt;
&lt;p&gt;These distinctions are explained next to the tour and on the pricing and coverage pages. They should not require a footnote hunt.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;let-people-decide&quot;&gt;Let people decide&lt;&#x2F;h2&gt;
&lt;p&gt;A good marketing page makes the product easier to understand. It gives someone enough information to decide whether a closer look is worth their time.&lt;&#x2F;p&gt;
&lt;p&gt;For us, that means real screens, a clearly stated planned price, a description of current limits, and a straightforward way to ask about a workflow.&lt;&#x2F;p&gt;
&lt;p&gt;&lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;Take a look inside Civitas.&lt;&#x2F;a&gt;&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>The small-team test.</title>
        <published>2026-09-07T00:00:00+00:00</published>
        <updated>2026-09-07T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/the-small-team-test/"/>
        <id>https://www.civitas.ltd/blog/the-small-team-test/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/the-small-team-test/">&lt;h2 id=&quot;one-person-several-jobs&quot;&gt;One person, several jobs&lt;&#x2F;h2&gt;
&lt;p&gt;On a small team, the person who checks a bill might also answer the member inquiry and write the afternoon update. There may be no separate operations person to keep the software organized.&lt;&#x2F;p&gt;
&lt;p&gt;That is not an edge case. It is a useful design constraint.&lt;&#x2F;p&gt;
&lt;p&gt;Every setup step, duplicate field, and unnecessary handoff asks for time that already has a job. The tool should earn that time back.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;test-the-ordinary-day&quot;&gt;Test the ordinary day&lt;&#x2F;h2&gt;
&lt;p&gt;It is tempting to evaluate software through its most elaborate demonstration. A better test is often the ordinary one: find the thing you were working on yesterday, understand where it stands, and do the next useful task.&lt;&#x2F;p&gt;
&lt;p&gt;Then try it as a colleague. Can you follow the work without asking the original person to explain the entire history?&lt;&#x2F;p&gt;
&lt;p&gt;That second test reveals a lot. A product can feel fast for its expert user and still make everyone else dependent on that person.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;make-room-for-the-team&quot;&gt;Make room for the team&lt;&#x2F;h2&gt;
&lt;p&gt;Our planned legislative offer includes ten seats in the organization subscription. The intention is to make shared context practical for a small staff, rather than leave the tool in the hands of the one person with access.&lt;&#x2F;p&gt;
&lt;p&gt;The price and scope are explained on the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;pricing page&lt;&#x2F;a&gt;. Availability follows launch verification.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;let-the-work-set-the-scale&quot;&gt;Let the work set the scale&lt;&#x2F;h2&gt;
&lt;p&gt;Small teams do not need less serious software. They need software that is serious about their constraints.&lt;&#x2F;p&gt;
&lt;p&gt;That means clear navigation, understandable limits, and a working surface that helps a person get back to the subject they care about. It means giving the team a useful place to start tomorrow, without making today’s work a configuration project.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Refund &amp; Cancellation Policy</title>
        <published>2026-07-12T00:00:00+00:00</published>
        <updated>2026-07-12T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/legal/refund-policy/"/>
        <id>https://www.civitas.ltd/legal/refund-policy/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/legal/refund-policy/">&lt;h1 id=&quot;civitas-refund-cancellation-policy&quot;&gt;CIVITAS REFUND &amp;amp; CANCELLATION POLICY&lt;&#x2F;h1&gt;
&lt;p&gt;Version 1.0 — Effective July 12, 2026&lt;&#x2F;p&gt;
&lt;p&gt;This Refund &amp;amp; Cancellation Policy explains how billing, cancellations, and
refunds work for paid Civitas subscriptions. It supplements, and should be read
together with, our &lt;a href=&quot;&#x2F;legal&#x2F;terms-of-service&#x2F;&quot;&gt;Terms of Service&lt;&#x2F;a&gt;. Payments are
processed securely by Stripe.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;1-subscriptions-and-billing&quot;&gt;1. Subscriptions and Billing&lt;&#x2F;h2&gt;
&lt;p&gt;Civitas paid plans (Pro and Enterprise) are billed in advance on a recurring
basis — monthly or annually, as selected at checkout. Your subscription renews
automatically at the end of each billing period unless you cancel.&lt;&#x2F;p&gt;
&lt;p&gt;The Free plan is not billed and requires no payment method.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;2-cancellation&quot;&gt;2. Cancellation&lt;&#x2F;h2&gt;
&lt;p&gt;You may cancel your subscription at any time from &lt;strong&gt;Billing → Manage Billing&lt;&#x2F;strong&gt;
inside your workspace (the Stripe customer portal), or by contacting
&lt;a href=&quot;mailto:billing@civitas.ltd&quot;&gt;billing@civitas.ltd&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
&lt;p&gt;When you cancel:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Your plan remains active through the end of the current paid billing period.&lt;&#x2F;li&gt;
&lt;li&gt;You will not be charged for the following period.&lt;&#x2F;li&gt;
&lt;li&gt;At the end of the period your workspace reverts to the Free plan; your data is
retained per our &lt;a href=&quot;&#x2F;legal&#x2F;privacy-policy&#x2F;&quot;&gt;Privacy Policy&lt;&#x2F;a&gt; and remains available
should you resubscribe.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;3-refunds&quot;&gt;3. Refunds&lt;&#x2F;h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;14-day satisfaction guarantee.&lt;&#x2F;strong&gt; For a first-time monthly or annual
subscription, if you are not satisfied you may request a full refund within
fourteen (14) days of the initial charge.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Annual plans.&lt;&#x2F;strong&gt; Outside the 14-day window, annual subscriptions may be
cancelled at any time; unused, prepaid full months may be refunded on a
pro-rata basis at our discretion.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Monthly plans.&lt;&#x2F;strong&gt; Outside the 14-day window, monthly charges already incurred
are non-refundable, but you may cancel to prevent future charges.&lt;&#x2F;li&gt;
&lt;li&gt;&lt;strong&gt;Enterprise agreements.&lt;&#x2F;strong&gt; Refund and cancellation terms for Enterprise
customers are governed by the applicable order form or master services
agreement, which controls in the event of any conflict with this policy.&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;Refunds are issued to the original payment method via Stripe and typically post
within 5–10 business days.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;4-failed-payments&quot;&gt;4. Failed Payments&lt;&#x2F;h2&gt;
&lt;p&gt;If a renewal payment fails, we will retry the charge and notify you. If payment
is not resolved, your workspace may be downgraded to the Free plan until billing
is restored. Your data is retained during this period.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;5-requesting-a-refund-or-help&quot;&gt;5. Requesting a Refund or Help&lt;&#x2F;h2&gt;
&lt;p&gt;To request a refund or ask a billing question, contact
&lt;a href=&quot;mailto:billing@civitas.ltd&quot;&gt;billing@civitas.ltd&lt;&#x2F;a&gt; with your account email. We
aim to respond within two (2) business days.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;6-changes-to-this-policy&quot;&gt;6. Changes to This Policy&lt;&#x2F;h2&gt;
&lt;p&gt;We may update this policy from time to time. Material changes will be posted on
this page with an updated effective date and, where appropriate, communicated to
active subscribers.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Privacy policy</title>
        <published>2025-01-31T00:00:00+00:00</published>
        <updated>2025-01-31T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/legal/privacy-policy/"/>
        <id>https://www.civitas.ltd/legal/privacy-policy/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/legal/privacy-policy/">&lt;h1 id=&quot;civitas-privacy-policy&quot;&gt;CIVITAS PRIVACY POLICY&lt;&#x2F;h1&gt;
&lt;p&gt;Version 1.0&lt;&#x2F;p&gt;
&lt;p&gt;Effective Date: January 1, 2025&lt;&#x2F;p&gt;
&lt;h2 id=&quot;1-introduction&quot;&gt;1. INTRODUCTION&lt;&#x2F;h2&gt;
&lt;p&gt;Civitas LLC (&quot;Civitas,&quot; &quot;we,&quot; &quot;us,&quot; or &quot;our&quot;) 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.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;2-information-we-collect&quot;&gt;2. INFORMATION WE COLLECT&lt;&#x2F;h2&gt;
&lt;p&gt;We collect information that you provide directly to us, including:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Name, email address, phone number&lt;&#x2F;li&gt;
&lt;li&gt;Mailing address&lt;&#x2F;li&gt;
&lt;li&gt;Date of birth&lt;&#x2F;li&gt;
&lt;li&gt;Citizenship status&lt;&#x2F;li&gt;
&lt;li&gt;Payment information&lt;&#x2F;li&gt;
&lt;li&gt;Political contribution information&lt;&#x2F;li&gt;
&lt;li&gt;Employer and occupation (for FEC compliance)&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;We also automatically collect:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Device information and IP address&lt;&#x2F;li&gt;
&lt;li&gt;Usage data and analytics&lt;&#x2F;li&gt;
&lt;li&gt;Cookies and similar technologies&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;3-how-we-use-your-information&quot;&gt;3. HOW WE USE YOUR INFORMATION&lt;&#x2F;h2&gt;
&lt;p&gt;We use your information to:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Provide and maintain our Service&lt;&#x2F;li&gt;
&lt;li&gt;Process political contributions and ensure FEC compliance&lt;&#x2F;li&gt;
&lt;li&gt;Communicate with you about your account&lt;&#x2F;li&gt;
&lt;li&gt;Improve our Service and user experience&lt;&#x2F;li&gt;
&lt;li&gt;Comply with legal obligations&lt;&#x2F;li&gt;
&lt;li&gt;Detect and prevent fraud&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;4-information-sharing&quot;&gt;4. INFORMATION SHARING&lt;&#x2F;h2&gt;
&lt;p&gt;We may share your information with:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Campaign committees and political organizations (as required by law)&lt;&#x2F;li&gt;
&lt;li&gt;Federal Election Commission (for contributions over $200)&lt;&#x2F;li&gt;
&lt;li&gt;Service providers and business partners&lt;&#x2F;li&gt;
&lt;li&gt;Law enforcement when required by law&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;We do not sell your personal information to third parties.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;5-your-rights&quot;&gt;5. YOUR RIGHTS&lt;&#x2F;h2&gt;
&lt;p&gt;Depending on your jurisdiction, you may have rights including:&lt;&#x2F;p&gt;
&lt;p&gt;GDPR (European Union):&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Right to access, rectify, or erase your data&lt;&#x2F;li&gt;
&lt;li&gt;Right to data portability&lt;&#x2F;li&gt;
&lt;li&gt;Right to object to processing&lt;&#x2F;li&gt;
&lt;li&gt;Right to restrict processing&lt;&#x2F;li&gt;
&lt;li&gt;Right to withdraw consent&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;p&gt;CCPA (California):&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;Right to know what personal information is collected&lt;&#x2F;li&gt;
&lt;li&gt;Right to delete personal information&lt;&#x2F;li&gt;
&lt;li&gt;Right to opt-out of sale of personal information&lt;&#x2F;li&gt;
&lt;li&gt;Right to non-discrimination&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;6-data-security&quot;&gt;6. DATA SECURITY&lt;&#x2F;h2&gt;
&lt;p&gt;We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;7-data-retention&quot;&gt;7. DATA RETENTION&lt;&#x2F;h2&gt;
&lt;p&gt;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.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;8-children-s-privacy&quot;&gt;8. CHILDREN&#x27;S PRIVACY&lt;&#x2F;h2&gt;
&lt;p&gt;Our Service is not directed to individuals under 18 years of age. We do not knowingly collect personal information from children under 18.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;9-international-data-transfers&quot;&gt;9. INTERNATIONAL DATA TRANSFERS&lt;&#x2F;h2&gt;
&lt;p&gt;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.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;10-changes-to-this-privacy-policy&quot;&gt;10. CHANGES TO THIS PRIVACY POLICY&lt;&#x2F;h2&gt;
&lt;p&gt;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 &quot;Effective Date.&quot;&lt;&#x2F;p&gt;
&lt;h2 id=&quot;11-contact-us&quot;&gt;11. CONTACT US&lt;&#x2F;h2&gt;
&lt;p&gt;If you have questions about this Privacy Policy, please contact:&lt;&#x2F;p&gt;
&lt;p&gt;CIVITAS LLC&lt;&#x2F;p&gt;
&lt;p&gt;Privacy Team&lt;&#x2F;p&gt;
&lt;p&gt;Email: privacy@civitas.ltd&lt;&#x2F;p&gt;
&lt;p&gt;For EU&#x2F;EEA residents, our Data Protection Officer can be reached at:&lt;&#x2F;p&gt;
&lt;p&gt;Email: dpo@civitas.ltd&lt;&#x2F;p&gt;
&lt;h2 id=&quot;12-specific-jurisdictions&quot;&gt;12. SPECIFIC JURISDICTIONS&lt;&#x2F;h2&gt;
&lt;p&gt;California Residents (CCPA):&lt;&#x2F;p&gt;
&lt;p&gt;To exercise your rights under CCPA, please contact privacy@civitas.ltd or call 1-800-XXX-XXXX.&lt;&#x2F;p&gt;
&lt;p&gt;EU&#x2F;EEA Residents (GDPR):&lt;&#x2F;p&gt;
&lt;p&gt;Our EU representative can be reached at eu-representative@civitas.ltd&lt;&#x2F;p&gt;
&lt;p&gt;You have the right to lodge a complaint with your local supervisory authority.&lt;&#x2F;p&gt;
&lt;p&gt;Last Updated: January 1, 2025&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Terms of Service</title>
        <published>2025-01-31T00:00:00+00:00</published>
        <updated>2025-01-31T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/legal/terms-of-service/"/>
        <id>https://www.civitas.ltd/legal/terms-of-service/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/legal/terms-of-service/">&lt;h1 id=&quot;civitas-terms-of-service&quot;&gt;CIVITAS TERMS OF SERVICE&lt;&#x2F;h1&gt;
&lt;p&gt;Version 1.0&lt;&#x2F;p&gt;
&lt;p&gt;Effective Date: January 1, 2025&lt;&#x2F;p&gt;
&lt;h2 id=&quot;1-acceptance-of-terms&quot;&gt;1. ACCEPTANCE OF TERMS&lt;&#x2F;h2&gt;
&lt;p&gt;By accessing or using the Civitas platform (&quot;Service&quot;), you agree to be bound by these Terms of Service (&quot;Terms&quot;). If you do not agree to these Terms, do not use the Service.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;2-use-of-service&quot;&gt;2. USE OF SERVICE&lt;&#x2F;h2&gt;
&lt;p&gt;You agree to use the Service only for lawful purposes and in accordance with these Terms. You are responsible for maintaining the confidentiality of your account and password.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;3-political-contributions&quot;&gt;3. POLITICAL CONTRIBUTIONS&lt;&#x2F;h2&gt;
&lt;p&gt;All political contributions made through the Service are subject to Federal Election Commission (FEC) regulations. By making a contribution, you certify that:&lt;&#x2F;p&gt;
&lt;ul&gt;
&lt;li&gt;You are a U.S. citizen or lawfully admitted permanent resident&lt;&#x2F;li&gt;
&lt;li&gt;You are at least 18 years old&lt;&#x2F;li&gt;
&lt;li&gt;The contribution is made from your own funds and not from funds provided by another person&lt;&#x2F;li&gt;
&lt;li&gt;You are not a federal contractor&lt;&#x2F;li&gt;
&lt;li&gt;You are not a foreign national&lt;&#x2F;li&gt;
&lt;&#x2F;ul&gt;
&lt;h2 id=&quot;4-privacy&quot;&gt;4. PRIVACY&lt;&#x2F;h2&gt;
&lt;p&gt;Your use of the Service is subject to our Privacy Policy, which is incorporated into these Terms by reference.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;5-intellectual-property&quot;&gt;5. INTELLECTUAL PROPERTY&lt;&#x2F;h2&gt;
&lt;p&gt;All content, trademarks, and intellectual property on the Service are the property of Civitas LLC or its licensors.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;6-limitation-of-liability&quot;&gt;6. LIMITATION OF LIABILITY&lt;&#x2F;h2&gt;
&lt;p&gt;TO THE MAXIMUM EXTENT PERMITTED BY LAW, CIVITAS LLC SHALL NOT BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES ARISING OUT OF OR RELATED TO YOUR USE OF THE SERVICE.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;7-changes-to-terms&quot;&gt;7. CHANGES TO TERMS&lt;&#x2F;h2&gt;
&lt;p&gt;We reserve the right to modify these Terms at any time. Continued use of the Service after such modifications constitutes acceptance of the updated Terms.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;8-governing-law&quot;&gt;8. GOVERNING LAW&lt;&#x2F;h2&gt;
&lt;p&gt;These Terms are governed by the laws of the State of Indiana, United States of America.&lt;&#x2F;p&gt;
&lt;h2 id=&quot;9-contact-information&quot;&gt;9. CONTACT INFORMATION&lt;&#x2F;h2&gt;
&lt;p&gt;For questions about these Terms, please contact:&lt;&#x2F;p&gt;
&lt;p&gt;CIVITAS LLC&lt;&#x2F;p&gt;
&lt;p&gt;Legal Department&lt;&#x2F;p&gt;
&lt;p&gt;Email: legal@civitas.ltd&lt;&#x2F;p&gt;
&lt;p&gt;Last Updated: January 1, 2025&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Why Modern Campaigns Are Abandoning Legacy Political Technology</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/abandoning-legacy-political-technology/"/>
        <id>https://www.civitas.ltd/blog/abandoning-legacy-political-technology/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/abandoning-legacy-political-technology/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>5 Campaign Technology Trends That Will Define the 2024 Election Cycle</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/campaign-technology-trends-2024/"/>
        <id>https://www.civitas.ltd/blog/campaign-technology-trends-2024/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/campaign-technology-trends-2024/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>The Complete Guide to FEC Compliance for Campaign Treasurers</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/fec-compliance-guide/"/>
        <id>https://www.civitas.ltd/blog/fec-compliance-guide/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/fec-compliance-guide/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>10 Field Operations Best Practices From Winning Campaigns</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/field-operations-best-practices/"/>
        <id>https://www.civitas.ltd/blog/field-operations-best-practices/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/field-operations-best-practices/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Introducing LegiTrack: The Future of Legislative Monitoring</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/introducing-legitrack/"/>
        <id>https://www.civitas.ltd/blog/introducing-legitrack/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/introducing-legitrack/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Building a Sustainable Donor Pipeline: 7 Strategies That Work</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/blog/sustainable-donor-pipeline/"/>
        <id>https://www.civitas.ltd/blog/sustainable-donor-pipeline/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/blog/sustainable-donor-pipeline/">&lt;h2 id=&quot;this-article-has-been-retired&quot;&gt;This article has been retired&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier article described a previous product direction. We have retired its content so it does not present outdated product or availability claims.&lt;&#x2F;p&gt;
&lt;p&gt;For current information, read the &lt;a href=&quot;&#x2F;blog&#x2F;&quot;&gt;journal&lt;&#x2F;a&gt;, inspect the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;product tour&lt;&#x2F;a&gt;, or check the &lt;a href=&quot;&#x2F;pricing&#x2F;&quot;&gt;planned subscription&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>A note about earlier case studies</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/case-studies/advocacy-legislative-tracking/"/>
        <id>https://www.civitas.ltd/case-studies/advocacy-legislative-tracking/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/case-studies/advocacy-legislative-tracking/">&lt;h2 id=&quot;current-product-information&quot;&gt;Current product information&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier page is retained for existing links. It is not a verified customer outcome. For the current product, see the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;real interface tour&lt;&#x2F;a&gt; and &lt;a href=&quot;&#x2F;coverage&#x2F;&quot;&gt;coverage notes&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>A note about earlier case studies</title>
        <published>2024-01-01T00:00:00+00:00</published>
        <updated>2024-01-01T00:00:00+00:00</updated>
        
        <author>
          <name>
            
              Unknown
            
          </name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://www.civitas.ltd/case-studies/state-senate-consolidation/"/>
        <id>https://www.civitas.ltd/case-studies/state-senate-consolidation/</id>
        
        <content type="html" xml:base="https://www.civitas.ltd/case-studies/state-senate-consolidation/">&lt;h2 id=&quot;current-product-information&quot;&gt;Current product information&lt;&#x2F;h2&gt;
&lt;p&gt;This earlier page is retained for existing links. It is not a verified customer outcome. For the current product, see the &lt;a href=&quot;&#x2F;tour&#x2F;&quot;&gt;real interface tour&lt;&#x2F;a&gt; and &lt;a href=&quot;&#x2F;coverage&#x2F;&quot;&gt;coverage notes&lt;&#x2F;a&gt;.&lt;&#x2F;p&gt;
</content>
        
    </entry>
</feed>
