# Data protection plan

RE360Muse Ltd. is in Kigali, so [Law Nº 058/2021](https://dpo.gov.rw/dpp-law/general-provisions) applies. The live records sit on AWS in Ireland, Cloudflare R2, and Payaza. The [Data Protection Office](https://dpo.gov.rw/) has to authorize that. This page is the working plan. It is not a certificate.

## Still a filing

Do these with the office. The product cannot submit them.

1. Name a data protection officer and publish their name and email on `/privacy`. Use the office’s designation guide.
2. Register as a [data controller](https://dpo.gov.rw/services/data-controller-certificate) for accounts, billing, and the marketing site.
3. Register as a [data processor](https://dpo.gov.rw/services/data-processor-certificate) for workspace content a company enters.
4. Apply for [authorization to store personal data outside Rwanda](https://dpo.gov.rw/services/authorization-to-store-outside-rwanda) for AWS RDS in Ireland and Cloudflare R2.
5. Apply for [authorization to transfer personal data outside Rwanda](https://dpo.gov.rw/services/authorization-to-transfer-outside-rwanda) for AWS, Cloudflare, and Payaza. Attach the office’s standard contractual clauses once those vendors sign them.
6. Keep the personal-data inventory next to those forms: account data, workspace content, billing references, identity documents, marketing subscribers, and server logs. Retention periods are the ones in `/privacy`.

Until the storage and transfer authorizations are granted, do not describe the product as compliant.

A Rwandan customer company is the controller for owners, tenants, and leads it types in. That company files its own registration and its own storage authorization. Company settings has a notice they can copy. Onboarding says the same thing in one line.

## Shipped in the product

| Gap | Where it lives |
|-----|----------------|
| Download the account we control | Account → Privacy, and Finance → Settings → Privacy |
| Erase the sign-in, profile, sessions, and identity documents | Same screen. Personal wallet balance and a sole-owner company with other members block it. Company records stay. |
| Correction, restriction, objection | Same screen. Restriction pauses marketing. Correction and a detailed objection stay open for staff. |
| Staff reply and email trail | `/admin/privacy`. Access and erasure close themselves and email the person. |
| Retention periods and the missing certificates | `/privacy` and the processing clause in `/terms` |
| Notice for people a company records | Company → Settings → People you record |

The privacy policy states that the certificates and overseas authorizations are not issued. Do not remove that sentence until the office grants them.

## Breach runbook

A personal-data breach is unlawful destruction, loss, alteration, or unauthorized disclosure of personal data.

1. The person who sees it tells the data protection officer, or `info@re360muse.com` until an officer is named.
2. That person decides whether it is a breach, writes what happened, whose data, and what was done to stop it.
3. Email [databreach@dpo.gov.rw](mailto:databreach@dpo.gov.rw) as soon as the facts are known. Use the office’s [report a breach](https://dpo.gov.rw/services/report-a-data-breach) page.
4. If the breach is likely to affect people, email those people. Say what happened and what they should do.
5. Keep the note with the privacy-request records. Do not put secrets or full card numbers in the note.

## Retention

| Record | How long |
|--------|----------|
| Account profile | While the account is open, then erased on request |
| Identity documents | Erased with the account |
| Privacy-request record | 2 years after it is closed |
| Billing and Payaza references | 5 years after the charge |
| Server logs | 90 days |
| Marketing address | Until unsubscribe, then kept suppressed |
| Company workspace content | While the company uses the product, then export or delete when that company asks |
