Polycode · Privacy & Data

Polycode privacy & data

Read from Polycode's own page on 2026-11-10. 10 statements quoted word for word; anything the page does not say is shown as unstated, never guessed. APIs.io verifies none of it.

Role

value: controller
the operator is Polycode Limited (UK), reachable at antony@polycode.co.uk
Read from Polycode's own page on 2026-11-10

Data categories

category: identifying
Visitors are pseudonymous (a browser session UUID and, optionally, a persistent browser visitor UUID)
Read from Polycode's own page on 2026-11-10
category: contact
Real contact data — email, phone, financial, government-ID — is still blocked at ingest
Read from Polycode's own page on 2026-11-10
category: behavioral
When a visitor's message is ingested into the shared memory tree, it passes through: Bedrock Guardrail PII policies
Read from Polycode's own page on 2026-11-10

Purposes

purpose: Recognise returning contributor
so the graph can recognise a returning contributor
Read from Polycode's own page on 2026-11-10
purpose: Operator safety and cost controls
Per-session cap carve-out, synth cap carve-out, ingest cap carve-out — protects the daily heartbeat and PII redaction from a hot session.
Read from Polycode's own page on 2026-11-10

Retention

scope: Shared memory tree contributionsperiod: indefinitely
we keep contributions indefinitely as part of the shared memory tree, but always in summary form once they're past the per-session window
Read from Polycode's own page on 2026-11-10

Residency

The page states nothing on this.

International transfers

The page states nothing on this.

Subprocessors

Data processing agreement

Deletion

route: Email operator with session UUID; admin CLI memory-purge
Erasure flow for a session: the admin CLI runs memory-purge on the relevant leaf + descendants and writes an audit# row.
Read from Polycode's own page on 2026-11-10

Data subject rights

right: Access, rectification, erasure
UK GDPR rights of access, rectification, and erasure apply.
Read from Polycode's own page on 2026-11-10

Sale or sharing

stance: prohibited
No selling of visitor data.
Read from Polycode's own page on 2026-11-10

Document

Download YAML · schema: API Commons Privacy & Data 0.1.0 · transcribed by claude-haiku-5-5, checked verbatim against the fetched page