Legal
Terms of Service, Privacy Policy and Acceptable Use Policy for ChangeFreeze, written to be read. Last updated 1 November 2026.
Terms of Service
1. The agreement
These terms are a contract between you (or the organization you represent) and ChangeFreeze ("we", "us") covering use of changefreeze.io, its API and related services (the "Service"). By creating an account or calling the API you accept them. If you accept on behalf of an organization, you confirm you have authority to bind it. Enterprise customers with a signed agreement are governed by that agreement where it conflicts with these terms.
2. Accounts and organizations
You are responsible for activity under your account and API keys, for keeping credentials secret, and for the people you invite into your organization. Tell us promptly at support@changefreeze.io if you believe a key or account is compromised; revoke keys yourself immediately from the app.
3. The Service and your responsibility
ChangeFreeze records freeze windows and answers whether a change is permitted. It is advisory infrastructure: your systems decide what to do with the answer. You remain responsible for your deployments, for configuring freezes, scopes and fail-open or fail-closed behaviour correctly, and for complying with your own change-management obligations. We do not access your infrastructure.
4. Plans, payment and changes
Paid plans are billed in advance, monthly or yearly, through Stripe. Prices exclude taxes. You can upgrade, downgrade or cancel at any time; cancellation takes effect at the end of the paid period and your organization returns to the Free plan with its data intact, subject to that plan's limits and retention. We may change prices with at least 30 days' notice; changes apply from your next renewal.
5. Your data
You own the data you submit (service names, freeze definitions, check metadata, exception justifications). You grant us the rights needed to store, process and display it to provide the Service. Data on a public status page is, by your choice, public. We retain check and audit history for the period your plan specifies and may delete older records.
6. Availability and support
We aim for high availability but, except where an Enterprise agreement states an SLA, the Service is provided "as is" without an uptime guarantee. Support is by email; Business and Enterprise plans receive priority handling.
7. Termination
You may delete your organization at any time from Settings. We may suspend or terminate accounts that breach these terms or the Acceptable Use Policy, or that are unpaid after notice. On termination we delete your data within 30 days, except where retention is required by law or for backups that expire on their normal schedule.
8. Disclaimers and limitation of liability
To the fullest extent permitted by law, we disclaim implied warranties, and our total liability arising from the Service in any twelve-month period is limited to the fees you paid us in that period. We are not liable for indirect, consequential or special damages, including losses caused by a change that was or was not deployed on the basis of an API response.
9. General
These terms are governed by the laws of England and Wales, with disputes heard in the courts of England. If a provision is unenforceable the rest remains in effect. We may update these terms; material changes will be announced in the app or by email at least 14 days before they take effect.
Privacy Policy
What we collect
- Account data: name, email address and authentication identifiers from our identity provider (Auth0), organization name, time zone and role.
- Service data: services, environments, freezes, exceptions (including justifications and approver identities), API key metadata (never the key itself; we store a hash), notification channel configuration and recipients.
- Check and audit logs: for each API check the target, actor, source, ref and metadata you send, the decision, the API key used, the client IP address and user agent, and a timestamp. Audit entries record who changed what and from which IP.
- Billing data: handled by Stripe. We store your Stripe customer and subscription identifiers and plan status; we never see full card numbers.
- Technical data: request logs for security and debugging, retained for up to 30 days.
How we use it
To operate the Service, enforce plan limits, send the notifications you configure (freeze, exception and blocked-check events), send transactional email (invitations, approvals, receipts), respond to support requests, prevent abuse and improve reliability. We do not sell personal data and we do not use your data to train models or for advertising.
Sub-processors
Cloudflare (hosting, storage and email delivery), Auth0 (authentication) and Stripe (payments). Notifications you configure are sent to the Slack, Microsoft, Discord or webhook endpoints you provide. We will update this list before adding a sub-processor that handles personal data.
Retention and deletion
Check and audit history is kept for your plan's retention period (30 days to 7 years) and then deleted. Account data is kept while your account exists. Deleting your organization removes its data within 30 days. You can request export or deletion of your personal data at privacy@changefreeze.io.
Your rights
Depending on where you live you may have rights to access, correct, export, restrict or delete your personal data, and to complain to a supervisory authority. Email us and we will respond within 30 days. For GDPR purposes, we act as a processor for the Service data your organization submits and as a controller for account and billing data.
Cookies
We use a session cookie to keep you signed in and a local-storage preference for the colour theme. No advertising or cross-site tracking cookies are set on changefreeze.io.
Acceptable Use Policy
Keep it boring. You agree not to:
- Use the Service to break the law, infringe others' rights or circumvent your own organization's controls (for example, forging exception approvals).
- Probe, scan or attack the Service, or attempt to access another organization's data, keys or status pages.
- Share API keys publicly, resell access, or build a competing service by systematically extracting data.
- Send abusive, deceptive or unlawful content through notification channels, status page messages or any text field.
- Exceed rate limits by rotating keys or accounts, or create automation that polls the API far beyond what your plan allows; use the public
status.jsonfor high-frequency polling. - Use a public status page to impersonate another organization.
We may suspend accounts that breach this policy and will contact you first where it is reasonable to do so. Report abuse or security issues to security@changefreeze.io; we welcome responsible disclosure and will not pursue good-faith researchers.