Rights Manager

One place to receive, resolve, and prove every data subject request.

Rights Manager centralizes requests, verifies the data subject's identity, and keeps the evidence you need to demonstrate compliance under Law 21.719.

GDPR CompliantISO 27001ISO 27701
  • Centralize every request
  • Verify identity
  • Track deadlines
  • Keep auditable evidence
  • Centralize every request
  • Verify identity
  • Track deadlines
  • Keep auditable evidence

Trusted by privacy leaders at:

ProVida AFPCoopeuchCaja Los AndesFamily ShopSBPayConsorcio
RedSaludSpinAlemana SegurosCruz VerdeEsencial
MetLifeMaicaoSalcobrandRipleyNeat
The problem

Answering on time depends on three things that tend to fail at once.

Legal receives the request, technology carries it out, marketing updates the databases. None of those teams sees the whole process end to end.

Example: an access request

Legal deadlineDay 14192930 of 30
  1. Day 4

    Re: Access request

    To continue, please send us a photo of both sides of your ID card.

    carnet.jpgUnverified
    Assumed, or an ID copy requested by email

    Who is asking

    Unverified identity

    Few organizations have a reliable way to confirm that the person asking is the data subject. Handing data to the wrong person is worse than not answering.

  2. Day 19
    • CRM
    • App
    • Call center
    • Legacy systems
    • Spreadsheets
    • Vendors

    3 of 6 systems checked

    Searched by hand, one system at a time

    Where the data is

    Fragmented data

    A data subject's information lives in the CRM, the call center, the app, legacy systems, and spreadsheets. Without an organized record of processing activities, finding all of it within the legal deadline isn't realistic.

  3. Day 29

    Response record

    • What was requestedNot recorded
    • What was deliveredNot recorded
    • How long it tookNot recorded
    • Which channelNot recorded
    The answer is pieced together afterward

    What was recorded

    Lost evidence

    The request gets answered, but nothing records what was asked, what was delivered, how long it took, or through which channel. When the regulator comes asking, there is nothing to show.

If any one of the three fails, the response won't hold up to whoever reviews it.

Rights Manager

Every request becomes a case with an owner, a deadline, and auditable evidence.

What used to be coordinated over email is documented in one place, with a record of every action and every response.

  • A portal inside your privacy center

    The request form and status lookup are embedded on your site, in public or signed-in mode, with your brand's look and feel.

    Read the docs (in Spanish)
  • Configurable identity verification

    Government database checks, document reading, or a liveness test, depending on the level your organization sets.

    Read the docs (in Spanish)
  • Deadlines and due-date alerts

    Each case is assigned to a person, with its status and time remaining. Cases close to their deadline are flagged and grouped in their own view.

    Read the docs (in Spanish)
  • Configurable workflows

    Waits, notifications, calls to other systems, and human approval steps within the same flow.

    Read the docs (in Spanish)
  • Auditable evidence

    Every request, every response, and the files attached at resolution are recorded with date and author, in a format that holds up during an inspection.

    Read the docs (in Spanish)
  • Law 21.719 and REDEC rights

    The same flow covers the six data subject rights and requests under Chile's Consolidated Debt Registry.

    Read the docs (in Spanish)
How it works

How Rights Manager works

What happens today when a customer asks for their data? Here is the full journey, from the form the data subject fills out to the documented response.

  1. 1Public form

    The data subject chooses which right to exercise, with the explanation right beside it

    Rights explained in the moment. Access, rectification, erasure, objection, and portability, each with an example of when it applies.

    Restriction when it applies. When objecting, rectifying, or requesting erasure, the data subject can ask for processing to be paused while the case is resolved. The law doesn't allow requesting it on its own.

    Public or signed in. The same component works on your public site or inside a signed-in session, with your brand's look and feel.

    Read the docs (in Spanish)
  2. 2Verification

    Identity verification is what clears the request for processing

    Three checks you can combine. Government registry lookup, document reading with data extraction, and a liveness test, at the level your organization sets.

    Optional or required. By default, the data subject can submit the request and verify later, and your organization can require verification to complete submission.

    Status visible on both sides. The case waits for verification, and the data subject receives a code to follow its progress.

    Read the docs (in Spanish)
  3. 3Case management

    Every case has an owner, a status, and a deadline in plain sight

    Internal assignment. The request goes to the right person on the team, and the change is logged in the history.

    Deadlines in plain sight. Views separate active, due soon, overdue, and resolved cases, and each right shows whether it's on time, due soon, or critical.

    Documented resolution. Each case is accepted, partially accepted, or rejected, with the response to the data subject, the files that go with it, and the internal reason on record.

    Operational metrics. Request volume, cases in progress, resolved cases, and average response time.

    Read the docs (in Spanish)
  4. 4Automation

    Automation moves the case forward; the decision stays human

    Flows that wait, notify, and query. A workflow can start when the data subject is verified, wait for a set period, alert the team, query another system, or close a case that never moved forward.

    Approvals with a human in the loop. Steps that need judgment are resolved in a form sent to the person responsible.

    Tested before publishing. Every flow starts as a draft, is tested against an existing request, and only runs automatically once published.

    Read the docs (in Spanish)

The clock starts before your team has the answer.

Book a demo

What changes with Rights Manager

Area Email and spreadsheets With Soyio
IntakeRequests spread across inboxesA single intake channel
IdentityAssumed or requested by emailVerified before processing
DeadlinesTracked by handDue-date alerts per case
OwnershipDepends on who's availableExplicit assignment per case
CoordinationEmail threads between teamsWorkflows with defined steps
EvidencePieced together afterwardA history of every action
Book a demo

The rights portal lives where users already manage their consents.

The privacy center is the component your organization embeds on its site. From there, users submit rights requests, check the status of each one and, if your organization uses the Consent module, manage their consents without leaving the portal.

One component to install. Identity verification is built in, with no separate integration.

Public and signed-in modes. It works on your public site or inside a signed-in session.

Data subjects check their own case. With the code they receive by email, they can see the status of their request without calling or writing to the call center.

Frequently asked questions

Law 21.719 grounds the exercise of rights in the principle of transparency: data subjects must be able to understand what happens with their request. These are the questions that come up before implementing the module. If yours isn't here, write to us.

It's the module where requests people make about their personal data are received, handled, and resolved. Data subjects see a form and status tracking inside the privacy center embedded on your site; your internal team sees the full case in the dashboard. It's used by the teams responsible for responding: privacy, compliance, legal and, in many cases, customer service.

A channel for receiving requests, a response within the legal deadline, and the ability to prove how each case was resolved. The recognized rights are access, rectification, erasure, objection, and portability, plus temporary restriction of processing while a request is being resolved. Restriction has a shorter response deadline than the others.

Soyio operates under ISO 27001 and ISO 27701 certification. In the dashboard, permissions let a person manage cases without seeing the associated personal data, so day-to-day work doesn't expose information that role doesn't need.

It depends on where the form is published and whether your organization wants identity verification. An implementation with the public portal and the dashboard takes weeks. Automated flows into internal systems are added later, as your team defines its process.

Not to receive and respond to requests. To build workflows that query other systems, it helps to have someone who knows your internal architecture. The Soyio team works with you on flow design during the first weeks.

The portal is embedded on your site with the Soyio Web SDK, and identity verification is built into that same component. Toward internal systems, the module connects through APIs and webhooks, and workflows can call an external service or ask a person for approval by email. The case stays centralized in Soyio, even when part of the work happens in other tools.

Have more questions? Continue in our documentation
START TODAY

Get intake in order before the first request arrives.

Rights Manager receives the request, verifies who is making it, and keeps a record of how it was resolved.

Book a demo

Subscribe to our newsletter

Privacy is making headlines

A weekly roundup of privacy, regulation, and technology news that could affect your business.

Subscribe (LinkedIn, opens in a new tab)