Perfect Cut

Data Portability and Switching Register

Effective

1. Scope and request

This register forms part of the Perfect Cut contract and sets out the switching terms, online register and infrastructure transparency required for a data processing service by Articles 25, 26 and 28 of Regulation (EU) 2023/2854. An authorised team administrator may export available datasets in Perfect Cut or request a complete exit package, transfer assistance, on-premises port or erasure at [email protected]. PurePortal verifies authority before releasing team data.

2. Exportable data and digital assets

  • Account profile and customer-controlled team details, memberships, roles, groups, domains, invitations and configuration, subject to the requesting administrator’s authority.
  • Pipes, variants, identifiers, saws, plates, plate variants, machines, groups, custom metadata definitions/values, starter data and linked external-catalog overrides.
  • Projects, cuts, plate parts, templates, imports, calculation inputs, material snapshots, results, placements, operations, work instructions and permitted calculation history.
  • Pricing policies, test cases, quote inputs, approved quote data and customer-created export configurations.
  • Customer-owned shared catalogs, items, variants, audiences, subscriptions, invitations and change history that the customer is authorised to receive.
  • Customer-supplied logos and user avatars, plus audit/security records that the customer is legally and contractually authorised to access.
  • Subscription and acceptance records held by PurePortal to the extent they are customer exportable; Link and Stripe receipts, invoices and payment records remain available through their transaction-management interfaces.

3. Excluded data

The following categories are not exportable because they cannot be used independently by Customer, belong to another party, or their disclosure would undermine security or PurePortal’s rights. The exclusion is applied narrowly and does not prevent export of Customer’s underlying data:

  • Passwords, password hashes, one-time tokens, session credentials, API-key secrets, encryption keys and provider credentials.
  • Another customer’s or user’s data, except data lawfully shared with and exportable by the requesting Customer.
  • PurePortal source code, optimisation algorithms, internal scoring, deployment configuration and trade secrets.
  • Internal fraud, threat, vulnerability and abuse indicators whose disclosure would impair security; relevant customer-facing audit events remain exportable where authorised.
  • Raw Stripe webhook payloads, Stripe reconciliation internals and third-party data that licensing or law does not permit PurePortal to transfer; customer-facing transaction fields remain exportable.
  • Third-party software, catalogs or digital assets for which Customer has no independent usage right.
  • Aggregated or irreversibly anonymised service metrics that no longer relate to Customer, and internal operational telemetry not generated directly by or relating directly to Customer.

4. Structures, formats and interfaces

4. Structures, formats and interfaces
DataFormat and structure
Configurable production datasetsCSV, JSON, XML or the fixed-width/text format configured by Customer; UTF-8 unless the saved configuration specifies an available encoding
Complete exit packageZIP archive containing UTF-8 JSON and/or CSV tables plus a manifest; ISO 8601 UTC timestamps, stable UUID references, decimal numbers and explicit unit/currency fields
ImagesCustomer-supplied avatar/logo binary or a service-normalised supported image format, referenced from the archive manifest
APIAvailable REST-style HTTPS endpoints with JSON; endpoint details and authorised API access are supplied where enabled for the customer
Provider documentsLink and Stripe invoice/receipt formats and exports supplied through their transaction-management interfaces

Known limitation: the in-product configurable export covers individual operational datasets rather than one complete relational archive. A complete switch therefore requires a support-assisted exit package. The package preserves identifiers and includes a schema/manifest so a destination provider can interpret relationships. Perfect Cut does not promise functional equivalence in a different application, whose data model and optimiser may differ.

5. Switching procedure and periods

  • Customer states whether it will switch to a named provider, port to on-premises infrastructure, or erase its exportable data, and supplies destination details and a secure transfer contact where needed.
  • The maximum notice period is the remaining current monthly subscription period and never more than two months. Customer and PurePortal may agree to start sooner.
  • After the notice period, PurePortal provides reasonable assistance, maintains the contracted service and security, identifies known continuity risks and completes the transition without undue delay, normally within the mandatory maximum 30-calendar-day transition period.
  • If that period is technically infeasible, PurePortal notifies Customer within 14 working days of the request, explains why and states an alternative period no longer than seven months. Customer may extend the transition once for a period it considers appropriate.
  • The contract terminates when the switch is successfully completed, when the retrieval period following a direct erasure request ends, or at another mutually agreed time if the switch cannot be completed. PurePortal notifies Customer of termination.
  • Exportable data remains available for secure retrieval for at least 30 calendar days after the transition. After that period or a later agreed date, and once the switch is complete, PurePortal erases exportable data and digital assets generated by or relating directly to Customer, subject to legal retention and protected backup expiry.

6. Assistance, continuity and security

PurePortal provides the information, export package, available open interfaces and reasonable technical coordination needed for Customer’s exit strategy. Customer and its destination provider must supply correct destination details, protect credentials, test imports and maintain their own continuity plan. Data is delivered through an access-controlled transfer method or another agreed secure channel. PurePortal does not access the destination environment unless separately authorised.

7. Fees

PurePortal charges no switching, data-egress or standard exit-assistance fee. Ordinary subscription fees remain due until contractual termination. There is no self-service early-termination penalty. Work expressly requested beyond the statutory switching obligations—such as custom transformation or destination implementation—requires a separate written offer and is optional.

8. Infrastructure jurisdiction and government access

Perfect Cut’s primary application and PostgreSQL database for customer content are hosted by Hetzner Online GmbH. The selected data-centre location and its jurisdiction are not evidenced by the deployment materials reviewed for this register and must be confirmed before production publication. Current recovery copies are local only. Cloudflare provides global DNS, reverse-proxy delivery, TLS and network security; connection/request data and transient traffic may therefore be processed under US and other relevant jurisdictions with the safeguards described in the Privacy Notice and DPA. Transactional email uses Zoho’s European service. Stripe and Sold through Link provide Managed Payments and billing infrastructure and do not host Perfect Cut team content.

Measures intended to prevent international governmental access to or transfer of non-personal data held in the EU where that would conflict with EU or German law include documented infrastructure selection, data minimisation, contractual confidentiality and data-protection duties, tenant and role controls, TLS, protected credentials, restricted administrative access, security logging and legal review of demands. PurePortal does not voluntarily provide third-country authorities access to customer data and, to the extent legally permitted, challenges or limits incompatible demands and informs the affected customer unless prohibited.

The PurePortal-operated Swetrix service is active only for consented analytics and does not record page content. Backblaze remote backups and OpenAI AI processing are not active infrastructure. This register, the Privacy Notice and the DPA/subprocessor list must be updated before a planned provider begins processing; any change affecting data location or governmental-access exposure will be stated there.

9. Register updates

PurePortal updates this register when export structures, formats, standards, interfaces or known limitations change materially. A request is fulfilled using the structures available for the relevant service version, and the delivered manifest documents the actual package.