01
Claim boundary
No endpoint can certify legal compliance
Compliance depends on the actual connector behavior, provider contract, customer purposes, jurisdictions, roles, data lifecycle, and operations. A secure transport or deletion endpoint is only one control. DewEngine's LinkedIn path is decision-gated because the proposed non-official session access requires qualified legal review and provider or product authorization before implementation or sale. This guide is not legal advice or a certification claim.
- Assign legal and product owners for the decision
- Avoid labels such as compliant unless evidence supports a defined standard
02
Data map
Inventory every source, purpose, and recipient
Map account authorization, profiles, companies, relations, searches, messages, invitations, posts, jobs, raw observations, normalized projections, exports, logs, backups, and subprocessors. For each class, record controller or processor roles, lawful purpose, access groups, region, retention, correction, deletion, and onward use. An undocumented cache or analytics copy can defeat an otherwise careful primary store.
- Link every public field claim to the inventory
- Require a separate decision for model training or secondary enrichment
03
Security controls
Protect authorization and personal content differently
Provider session material needs managed-key envelope encryption, strict decryption identity, rotation, versioned associated data, and no exposure in logs or browsers. Professional content needs tenant isolation, least privilege, encrypted storage, bounded raw retention, and redacted support access. Secrets and messages should not share generic debug paths. Incident response must include account restriction, credential compromise, and unauthorized export.
- Audit privileged secret and content access
- Test ciphertext substitution across account boundaries
04
User rights
Make provenance, correction, export, and deletion executable
A subject or customer request cannot be handled if the system cannot find downstream copies. Retain source and transformation lineage, tenant ownership, and retention state. Correction should distinguish an inaccurate active value from a historically accurate observation. Disconnect stops future collection; deletion follows the documented scope across normalized rows, raw payloads, objects, caches, search indexes, exports, and backups.
- Verify deletion with evidence rather than a UI success toast
- Document lawful exceptions and expiry for retained audit facts
05
Operational policy
Enforce purpose and provider feedback at runtime
Static terms do not stop an unsafe command. Admission checks should combine account health, product entitlement, customer role, purpose, suppression, action budgets, and kill switches. Challenge, restriction, or authorization loss pauses work without evasive retries. Every provider-visible action has an accountable user and audit record, while read operations remain minimized to the approved workflow.
- Make policy refusal a stable machine-readable outcome
- Never use human-mimicry or anti-detection behavior
06
Approval dossier
Require dated evidence before changing release state
The dossier must include counsel's analysis of the exact access method and jurisdictions, provider or partner authorization where required, customer terms and disclosure, threat model, data-flow review, retention, tenant tests, consented conformance, deletion drill, incident exercise, action budgets, and product-risk acceptance. Evidence expires when contracts, methods, schemas, or controls change. Until approval is current, the public status stays decision-gated.
- Name an owner and date for every gate
- Automatically remove product claims unsupported by the manifest