Data protection plan
RE360Muse Ltd. is in Kigali, so Law Nº 058/2021 applies. The live records sit on AWS in Ireland, Cloudflare R2, and Payaza. The Data Protection Office 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.
- Name a data protection officer and publish their name and email on
/privacy. Use the office’s designation guide. - Register as a data controller for accounts, billing, and the marketing site.
- Register as a data processor for workspace content a company enters.
- Apply for authorization to store personal data outside Rwanda for AWS RDS in Ireland and Cloudflare R2.
- Apply for authorization to transfer personal data outside Rwanda for AWS, Cloudflare, and Payaza. Attach the office’s standard contractual clauses once those vendors sign them.
- 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.
- The person who sees it tells the data protection officer, or
info@re360muse.comuntil an officer is named. - That person decides whether it is a breach, writes what happened, whose data, and what was done to stop it.
- Email databreach@dpo.gov.rw as soon as the facts are known. Use the office’s report a breach page.
- If the breach is likely to affect people, email those people. Say what happened and what they should do.
- 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 |