How we handle your data and commitments
Fiscal Disobedience is built on principles of transparency, privacy, and user empowerment. We believe you have the right to know exactly how your data is collected, stored, and used.
When you commit to canceling subscriptions, we collect the following information:
Your data is used solely for:
All data is stored securely in Cloudflare D1, a serverless SQLite database. We use industry-standard security practices to protect your information.
You control how your data is shared through the sharing preference you select:
We retain your data as long as necessary to provide the service and maintain campaign statistics. If you have concerns about your data, please contact us.
We display estimated dollar impact (e.g., "Total Impact") based on the services people commit to canceling. We acknowledge that each service has multiple service levels, SKUs, and bundles that affect actual pricing.
Where possible, a reasonable service level was used for the calculations, such as the lowest ad-free plan tier, or monthly pricing rather than annual. Some outliers may exist; for example, Adobe Creative Cloud uses the standard monthly price in our estimates.
Services that users enter as "Other" (free text) do not receive individual pricing. "Other" entries receive a single token valuation of $5 for impact purposes. When a service is later added to the list of named options and matches what was previously entered as Other, it is then calculated at its listed rate and is no longer counted as part of the saved "Other" data. Services that are removed from the listed options still have their historical entries counted toward impact using the rates that were in effect when they were listed.
We implement several security measures to protect your data:
To detect platform abuse and keep commitment data reasonably accurate, we use a one-way SHA-256 hash of your IP address combined with a secret salt. The salt is unobtainable by anyone: it is stored in an encrypted form that even the Fiscal Disobedience team and Cloudflare cannot access. The salt is rotated on a schedule; when a new salt is put in use, the previous one is obliterated. The hashed identifiers we store are also obliterated regularly, so we do not retain them indefinitely.
This approach, together with Cloudflare Turnstile, lets us identify duplicate or abusive submissions and maintain confidence in the numbers you see, without ever storing your real IP or using cookies. We are able to avoid cookies (which would not be foolproof and can be cleared or blocked) because this hashed identifier gives us a privacy-preserving way to spot abuse and keep the data trustworthy.
← Back to Home