Data processing agreement

This document describes accurately how the platform behaves, but has not yet been reviewed by a lawyer. Have it reviewed before relying on it contractually.

Roles

For account data you are the controller and Preditoring is the processor. For telemetry, the question is largely academic — machine measurements are not personal data — but we process it under the same terms so there is no gap.

Scope of processing

We process only to provide the service, to support you when you ask, and to keep the audit trail. We do not process for our own purposes, do not profile, and do not train models on your data.

Sub-processors

• Infrastructure hosting for the managed offering (EU region).
• The AI model provider you configure, and only for advisor requests you make. Configure none and this sub-processor does not exist for your tenant.
• On-prem deployments have no sub-processor: nothing leaves your network.

Security measures

• A separate database per tenant, provisioned on signup.
• Role-based access re-checked server-side on every state-changing request.
• Bcrypt password hashing; per-server revocable agent tokens; encrypted equipment credentials never returned by the API.
• TLS in transit; a denormalized audit trail that survives deletion of the object it describes.

Transfers

The managed offering is hosted in the EU. Where you enable an AI provider outside the EU, that transfer is one you configure and can decline by leaving the feature off or pointing it at a local model.

Breach notification

We notify you without undue delay and in any case within 72 hours of becoming aware of a personal data breach affecting your tenant, with what we know at the time rather than after an internal review completes.

Deletion and return

On termination, an export of your tenant is made available for 30 days, after which the database is dropped. Backups age out on their own schedule, within 35 days.