Privacy policy

Last updated: October 8, 2026

This policy describes how Motion for Change (“we,” “us”) handles information when you use this service to submit motions and support requests related to your elected representatives. It covers both the petitioning site and the separate ID check service we operate, which runs on its own domain and is referred to below as the ID service. We keep data practices narrow and aim to be easy to read.

Information we collect

Your account holds:

Separately, and with no link to any account, we store the counted participations described below. While a verification is in progress we also hold short-lived state for it, which does connect your account to the participation being created; that state is deleted as soon as the participation is stored, and in any case when the issue ends.

Identity verification

Joining an issue requires an ID check, which runs on the ID service. Your phone’s wallet presents your state driver’s license or ID, and the ID service checks the issuing state’s signature on it and that it was presented from the device it was issued to.

The check asks your wallet for the credential’s expiry date, your city and state, your street address and ZIP code, a yes-or-no answer to whether you are over 18, and your ID number. It does not ask for your name, your photo, or your date of birth. The street address and ZIP are used once, to work out which congressional district you are in, and are then discarded.

The ID service keeps none of these details. Your ID number in particular is never stored: what is stored is a short keyed fingerprint computed from it, specific to the single issue you are joining, which cannot be reversed or matched up across issues without a secret only the ID service holds. Its only purpose is to refuse a second signature for the same person on the same issue. Those records carry no timestamp and expire on their own when the issue ends.

What reaches the petitioning site is your congressional district, your city and state, and confirmation that you are over 18 and hold a valid credential. The verified city and state must match what is already on your account or the check fails, rather than quietly reassigning it. Your district is saved to your account; the rest is checked and discarded, and the ID service’s response itself is not stored anywhere.

How participation is counted

When you join an issue, the petitioning site picks a random value, hides it behind a second random factor it keeps to itself, and sends only the hidden version to the ID service to be signed. The ID service signs it without ever seeing the value itself. The site then removes the hiding factor and stores the value and its signature as the counted participation. The point of working this way is that the ID check never hands the site a per-person identifier that could sit in its records afterward.

Counted participations are stored with no link to any account, no timestamp, and in an order that does not reflect when they arrived.

One link does exist while an issue is open. Your account records which issues you have joined and, until the issue ends, a pointer to your counted participation. That pointer is what lets you take an issue off your dashboard and put it back without verifying again. When the issue’s accumulation period ends, the pointer is removed and the random reference the issue’s participations were counted under is deleted, leaving a count that cannot be traced back to the people who made it. Your account still records that you joined.

Cookies

We set login cookies so you can stay signed in while using the service, and a short-lived cookie that carries the state of a verification in progress. These are used only for authentication and for completing a verification, not for advertising or cross-site tracking. We do not use analytics or advertising cookies on this site.

How we use your information

All data we retain is used strictly to enable you to use the service and for us to manage and follow through with your requests—that is, to operate Motion for Change. This includes emailing you about next steps, letting you log in to manage your submissions, and using your district to decide which issues you see.

Sharing

We do not sell user data, and we do not share it with third parties for their own purposes. We do rely on service providers to run the service—web hosting, the infrastructure the ID service runs on, and email delivery—which necessarily process data on our behalf.

Technical logs

Like most web services, hosting infrastructure may automatically generate technical logs when pages are requested (for example timestamps, IP addresses, and requested URLs). We do not combine those logs with analytics products, and we do not use them to build individual visitor profiles beyond what is needed to operate the service.

One consequence of how the ID check works is worth stating plainly. Your wallet will only release a credential to the site your browser is actually visiting, so the ID check has to happen on the ID service’s own domain. That means the ID service, and the infrastructure provider running it, see your IP address each time you verify. The measures described above keep the ID check from learning which issues you joined; they do not hide your network address from it, and no rearrangement of the parties involved would.

Changes

We may update this policy from time to time. The “Last updated” date at the top will change when we do.

Contact

Questions about this policy: [email protected]