Privacy policy

Privacy & Data Handling

What stays in your browser, what reaches DECOMMISSION servers, and what records are stored.

Updated 23 October 2026 · DECOMMISSION

1. Who this policy covers

This policy describes data handling in the DECOMMISSION website, account service, replay service, and compiler. DECOMMISSION is the public-facing product name. The formal operator identity, registered address, data-controller details, applicable privacy-law disclosures, and international-transfer arrangements must be finalized before live sales.

2. Consent-based compatibility assessment

Selecting a Make.com blueprint does not itself upload the file. After you explicitly consent to compatibility assessment, the selected blueprint is sent to DECOMMISSION's private assessment service to check compatibility with the supported workflow subset. This assessment does not generate or deliver a paid ZIP. Some external font resources may be requested by your browser.

3. What is sent for replay and compilation

When you explicitly consent to compatibility assessment, the selected blueprint is sent transiently to our private engine. When you request replay or artifact preparation, the selected blueprint and supplied test cases are sent to DECOMMISSION's application and isolated compiler for processing. Replay uses mocked fixture data rather than calling the live third-party endpoints in your workflow. Compiled source archives are stored privately for subsequent authorized delivery and may contain constants, URLs, or other material copied from your blueprint. Avoid including real credentials or unnecessary sensitive information.

4. Account, order, and payment data

We store account email addresses, salted password verifiers, hashed or otherwise protected session records, artifact metadata, stored ZIP references, order amounts and statuses, entitlement records, agreed terms versions, and security/rate-limit records. Payment checkout is processed through Stripe when enabled; DECOMMISSION does not store full card numbers. Payment and refund event metadata may be retained for settlement, security, tax, accounting, and dispute handling.

5. Purposes and service providers

Data is processed to provide the requested assessments, compilation, verification, account access, secure delivery, payment processing, fraud prevention, incident response, and legal compliance. Cloudflare hosts application, database, compiler, and private artifact storage. Stripe processes payments when enabled. External fonts may be served by Google. We do not sell submitted workflow blueprints or use them in model training by this application.

6. Storage, security and retention

We use access controls and encrypted transport for supported server communications; no security control eliminates all risk. Submitted blueprint data needed only for an assessment or replay may be processed transiently, but generated ZIP archives, account records and order histories are persisted. There is currently no published fixed automatic deletion schedule for stored ZIPs or customer accounts. Retention may be required for ongoing delivery, fraud prevention, accounting, disputes or legal obligations. We will not claim immediate deletion unless it has actually occurred.

7. Your choices and requests

The compatibility assessment also uses the private server after your explicit consent. Do not submit blueprints containing credentials or personal data. If you prefer not to upload, do not use the assessment. For requests about access, correction, deletion, or other applicable privacy rights, write to legal@decommission.dev. We will review requests subject to lawful retention requirements and available account-verification procedures; account deletion is not currently a self-service control.

8. Contact and updates

Privacy enquiries: legal@decommission.dev. Security reports: security@decommission.dev. General support: support@decommission.dev. This policy may be revised as the service and operational controls change. Material changes affecting purchases should be communicated before asking users to accept revised terms.