Skip to content
Platform / Privacy operations

Every request, incident and record, on time.

Run access and erasure requests, incidents, retention and processing records in one workspace, each with its own clock, owner and evidence.

Incident · Laptop lost
41 h leftto send the Commission notice
Customers
Has to be told
Notice
Drafted, not filed
Review the notice

Requests · incidents · retention · records

Each kind of privacy work runs on its own clock.

An incident is measured in hours, a request in weeks and retention in years. Asiri keeps each clock visible and tied to the record it belongs to.

  • Incidents
    Hours

    Assess severity, decide who has to be told and draft the Commission notice inside the 72-hour window.

  • Requests
    Weeks

    Check who is asking, search each system and record what you sent, or why you kept something.

  • Retention
    Years

    Give each kind of record a retention period and run deletions on a schedule, exceptions written down.

  • Processing records
    Whenever processing changes

    Revisit purposes, processors and transfers when a system, supplier or use of data changes.

The processing record

Every clock starts from one record.

A request search, an incident assessment and a deletion run all read from the same processing activity, so the answer to “what do we hold, and why?” is written once.

Processing activityCustomer ordersOwner · Ada Okafor
PurposeFulfil and support customer orders
Data categoriesName, address, order history
Lawful basisContract
ProcessorsKestrel Cloud, hosting
TransfersUnited Kingdom, under contract
RetentionSix years, then deleted

One incident

Laptop lost, hour by hour.

A Koru Commerce laptop holding unencrypted customer identity data is reported lost on a Monday morning.

Ada Okafor reviews the drafted notice, corrects the number of people affected and files it on Tuesday morning.

Fictional company example

72-hour notice window
Filed at hour 26
  1. Laptop reported lost

    Emeka Obi
  2. Severity assessed: identity data, unencrypted

    Has to be told
  3. Commission notice drafted from the incident record

  4. Notice reviewed and filed

    Ada OkaforFiled
  5. Customers told what happened, in plain words

The assessment, the notice and the customer message stay on one incident record.

Before you start

What privacy teams ask about daily operations.

Does Asiri work out our legal deadlines?

Asiri’s Nigerian rules support the relevant workflows, but a deadline depends on the facts you record. Where information is missing, Asiri shows it as missing rather than assuming a clear position.

Can we keep information after an erasure request?

Where another law requires it, yes. Record the reason against the system concerned, and explain it to the person in plain words in your response.

Does Asiri delete data in our systems?

Asiri records retention rules, schedules and the decisions behind them. Deletion in a connected system depends on that integration and the permissions you grant.

Run privacy as daily work, not a yearly scramble.

Asiri’s Nigerian rules support the relevant privacy workflow. Legal duties and deadlines require the applicable recorded facts; missing information is not treated as a clear position.

NextShow customers how you handle their data.Publish a Trust Centre that answers security and privacy questions from approved records.Explore the Trust Centre