Data governance

Privacy information

Information structure and data handling principles for HAKER.SI: what the enquiry form collects, why, retention, service providers, transfers and individual rights. Draft — legal copy incomplete, launch blocker.

01 / CONTROLLER DECLARATION

Website operator & controller

The technical surface and workflows accessible via HAKER.SI are engineered, directed, and operated under the professional authority of Marcin Białczyk.

Legal identity
Marcin Białczyk / HAKER.SI Industrial Intelligence Atelier — [ PENDING OWNER SPECIFICATION ]
Registration status
[ PENDING OWNER SPECIFICATION — jurisdiction to be stated ]
Registered address
[ AWAITING FORMAL RECORDING ]
Direct point of contact
[ PENDING OWNER CONFIRMATION ]
02 / INGESTION PIPELINE

Information collected via the enquiry form

Data collection on this platform is intended to be constrained to bilateral scoping requirements initiated through the /discuss-a-workflow/ submission pipeline. No passive telemetry or ambient extraction is intended.

Enquiry form telemetry fields
Telemetry fieldDatatypeOperational necessity
CONTACT_NAMEUTF-8 stringAttribution and bilateral correspondence.
WORK_EMAILEmail addressEncrypted transport destination for engineering replies.
COMPANY_ORGANISATIONUTF-8 stringInstitutional context & commercial eligibility checks.
PROCESS_DESCRIPTIONText blockHigh-level description of manual workflow friction.
OPERATIONAL_BOTTLENECKTaxonomy tagClassifying system domain (ETL, API, latency, OCR).
TRANSACTION_VOLUMEEnum rangeEstimated workload scale.
03 / PROCESSING SCOPE

Purpose of processing

All submitted payloads are intended to be quarantined to the singular engineering engagement lifecycle:

  • 01.

    Direct operational feasibility assessments

    evaluating technical scope, throughput feasibility, latency constraints, and tooling compatibility.

  • 02.

    Bilateral correspondence & scoping dialogues

    transmitting engineering assessments directly to the email address provided by the enquirer.

  • 03.

    Absolute exclusion of automated marketing networks

    submissions are never syndicated, sold, rented, or appended to CRM automated outbound newsletters or ad targeting lists.

04 / INFRASTRUCTURE TOPOLOGY

Technical service providers & infrastructure

Service providers and infrastructure are to be governed by standard European data processing contracts. The concrete providers are [ AWAITING SPEC ] and must be named before publication:

  • NODE: CLUSTER_EDGE

    hosting & compute within European geographical zones.

    [ AWAITING SPEC ]
  • NODE: INGEST_RELAY

    form transmission relay (forwarding webhook).

    [ AWAITING SPEC ]
  • NODE: SECURE_INBOX

    corporate mail server with SPF, DKIM, and DMARC enforcement.

    [ AWAITING SPEC ]
05 / RETENTION LIFECYCLE

Data retention & erasure principles

Retention periods below are draft values pending owner and legal confirmation:

Unengaged inquiry data
[ PROPOSED: purge after 90 days of inactivity — PENDING CONFIRMATION ]
Commissioned project logs
[ PROPOSED: statutory retention per accounting/legal code (one source draft says 5–10 years) — PENDING CONFIRMATION ]
Ephemeral edge access cache
[ PROPOSED: automatic cycle (14 days) — PENDING CONFIRMATION ]
06 / CLIENT TELEMETRY

Cookies, telemetry & local storage

Stated intent for this site (to be confirmed against the deployed build before publication):

  • No third-party advertising pixels: no integration with advertising or retargeting networks.
  • No ambient session recording: no third-party mouse-tracking or heat-mapping software.
  • Strict functional storage only: ephemeral browser state limited to stateless HTTP handshakes and system accessibility preferences. No consent banners are expected because no non-essential cookies are intended.
  • No fingerprinting: no canvas identification or device state hashing.
07 / SOVEREIGNTY BOUNDARIES

International transfers & safeguards

Edge servers and ingestion endpoints are intended to be positioned within European Economic Area (EEA) borders. Where external third-party infrastructure components (e.g. global DNS resolution or DDoS perimeter defences) route packets internationally, transfers are to be governed under the European Commission's Standard Contractual Clauses (SCCs). [ PENDING OWNER / LEGAL CONFIRMATION ]

08 / SUBJECT PREROGATIVES

Individual rights & data inquiries

Under GDPR Articles 15 through 22, verified natural persons retain rights regarding their records:

  • RIGHT OF ACCESS

    request verification and copy of stored records.

  • RIGHT TO RECTIFICATION

    correct inaccurate organisational records.

  • RIGHT TO ERASURE

    request purge of pre-scoping logs.

  • RIGHT TO RESTRICTION

    quarantine processing pending dispute resolution.

  • RIGHT TO DATA PORTABILITY / EXPORT

    (merged from the mobile export)

09 / AUDIT TRAIL

Policy updates & revision cadence

Modifications reflecting architecture changes, newly provisioned infrastructure nodes, or formal enterprise onboarding will be recorded here with a real revision date. No revision history is published yet (previous export version tags removed as unverified).

Revision history
RevisionChange
—[ PENDING OWNER SPECIFICATION ]

Limitations & scope

  • LEGAL COPY INCOMPLETE — LAUNCH BLOCKER. Controller registration, registered address, service providers and retention periods are pending owner specification and must be confirmed before publication.
  • Statements about the absence of tracking describe intent for this static site; they require owner/technical confirmation before publication.
  • No response-time commitments are made for rights requests.

Have a workflow where errors are expensive?

Discuss the workflow, constraints and control points directly with Marcin Białczyk.

Discuss a workflow