Raven Operational Decision Runtime

Privacy

Raven Systems Privacy Notice

Current notice for the static public briefing surface and controlled B2B pilot readiness.

Controller And Scope

ControllerIndustrial Tools Sp. z o.o. operates Raven Systems. Controlled pilot and billing details are confirmed during agreement review.

ScopeThis notice covers website briefing, pilot intake, billing readiness, support, operational decision packets, provider webhook fulfillment and the personal data boundary for approved B2B processing.

Current public surfaceThe current public layer is static and intentionally does not collect customer login data, live network data or payment card data.

Website analyticsCloudflare Web Analytics may measure page views, visits, referrers, basic device/browser class and public page performance signals. Raven uses this only to understand public content quality and does not use it for customer operational data, live collector data, payment data or private pilot evidence.

Data Classes

Business contactName, business email, company, role, country and communication history where provided by the business user.

Pilot contextOperational environment, incident class, approved data boundary, evidence references and decision owner details.

Billing eventsStripe event identifiers, product and price identifiers, payment status, tax identifiers where needed and reconciliation state.

Provider eventsProvider event identifiers, event type, signature state, idempotency state, payload-hash state, audit reference and human review state where needed for billing or mail recovery.

Decision auditDecision packets, approval traces, assumptions, unknowns, confidence boundaries and outcome review records.

Worker location future gateGPS/GSM technician data is not active. It requires a separate transparency, lawful-basis, retention and worker-notice gate.

Security And Retention

sensitive credentialsAPI keys, passwords and webhook signing sensitive credentials are not stored in the public site, repository, chat transcript, ordinary email, plain environment files or customer-visible pages. Public documents may reference only sensitive credential identifiers, owner, rotation, revoke and audit records.

Tenant isolationCustomer data must be isolated by organization, role and approved scope before production activation.

RetentionRetention periods must be tied to pilot scope, legal obligation, audit need and customer agreement.

Deletion and exportExport, deletion, legal hold and audit retention require identity, authority and conflict checks.

Sources And Operating Basis

GDPREUR-Lex Regulation (EU) 2016/679, especially transparency, rights, security and processor/control boundaries.

ePrivacyEUR-Lex Directive 2002/58/EC for electronic communications and tracking boundaries.

StripeStripe documentation for hosted payment surfaces, events and payment fulfillment boundaries.

CloudflareCloudflare documentation for DNS, edge security, static asset delivery and privacy-first Web Analytics on the public website.

Raven contractsInternal privacy, sensitive credentials, payment and ledger gates.

Back to briefing Terms