Role and scope
Sansa Group AB (organisation number 559111-9507), operating Yieldline through its SansaVision division from Göteborg, Sweden, is controller for direct account, website, sales, and support relationships. SansaVision and Yieldline are operating brands of Sansa Group AB, not separate legal entities. Sansa Group AB generally acts as processor for end-user, ad-platform, commerce, and product data a customer connects to its workspace. The customer decides its purposes, lawful bases, notices, and platform routing. The Data Processing Agreement governs that processor activity.
Controller processing matrix
| Purpose | Data | Legal basis | Recipients | Retention |
|---|---|---|---|---|
| Create and secure an account | Identity, work email, role, session, security events | Contract; legitimate interests in security | Cloudflare; authorized workspace admins | Account life plus limited security and claim period |
| Provide and bill the service | Workspace, plan, usage, invoices, business contacts | Contract; legal obligation | Cloudflare; payment and accounting providers when used | Contract life plus statutory accounting period |
| Send service and incident messages | Email, workspace role, notification preferences, incident context | Contract; legitimate interests | Cloudflare Email Service | Message logs up to 12 months unless an incident hold applies |
| Respond to support and rights requests | Contact details, message, verification and request metadata | Contract; legal obligation; legitimate interests | Cloudflare; authorized support and legal personnel | Request record normally up to 3 years |
| Protect and improve Yieldline | Security telemetry, errors, feature interactions after consent where required | Legitimate interests; consent where required | Cloudflare; consented analytics provider if later listed | Security up to 12 months; analytics up to 13 months |
| Send marketing | Business contact, consent, campaign interaction | Consent or legitimate interests where permitted | Cloudflare Email Service; consented campaign provider if later listed | Until opt-out or 24 months of inactivity |
Customer-directed processor activity
| Activity | Customer data | Instruction and safeguard |
|---|---|---|
| Ingestion and reconciliation | Campaign, spend, payment, subscription, refund, and product events | Documented integration scopes, tenant isolation, pseudonymous identifiers |
| Economic calculation | Offers, costs, margins, cohort outcomes | Deterministic semantic layer with effective-dated assumptions |
| Recommendation and action | Aggregates, confidence, contract, target objects | Typed proposals, policy checks, approval, idempotency, emergency stop |
| Creative production | Brand rules, briefs, source assets, performance tags | Customer-enabled Plotmesh route, cost cap, rights and production receipt |
| Reporting and support | Metrics, findings, incidents, evidence references | Role-based access, expiring shares, minimum necessary disclosure |
| Deletion and export | Workspace data and object references | Authenticated instruction, tombstones, propagation and completion record |
Data-protection principles
Yieldline is designed for lawfulness, fairness, transparency, purpose limitation, minimization, accuracy, storage limitation, integrity, confidentiality, and accountability. Product features expose source, freshness, confidence, contract version, and action history so customers can audit data use.
Rights matrix
| Right | How Yieldline supports it | Important limits |
|---|---|---|
| Information | Layered notices, source stamps, subprocessor and cookie pages | Customer-provided notices control for customer end-users |
| Access | Authenticated export or verified request form | Rights and freedoms of others may limit disclosure |
| Correction | Account editing and verified correction request | Immutable receipts keep correction history where required for audit |
| Erasure | Deletion request, integration revocation, object deletion and tombstones | Legal holds, fraud, security, billing, and claims may require limited retention |
| Restriction | Workspace and subject-level processing lock where applicable | Storage and legal claims may continue |
| Portability | Common machine-readable export for provided and observed data | Derived models and third-party rights may be excluded |
| Objection | Marketing stop, legitimate-interest review, and processing lock where applicable | Compelling grounds or legal claims can override in limited cases |
| Automated decisions | Human approval, deterministic gates, action receipts, rollback, and emergency stop | Yieldline is not intended for significant decisions about natural persons |
Request handling
Submit an electronic request through Data rights. We verify identity proportionately and normally respond within one month. Complex or numerous requests may qualify for a lawful extension with notice. You may complain to your local supervisory authority.
Transfers, subprocessors, and incidents
International transfers use an available adequacy decision, standard contractual clauses, or another lawful mechanism, with supplementary controls where required. Subprocessors receive documented instructions and confidentiality duties. Security incidents follow assessment, containment, evidence preservation, customer notification, and regulatory notification duties.
Official resources
For authoritative law and rights information, consult the GDPR text and the European Commission rights guide.