Contents
Summary in plain language
This summary helps you read the Policy. It is not part of it.
- 1IRAGE is responsible for the personal data you give the platform. Institutions that use the platform are responsible for their own collection data.
- 2We collect what we need to run your account, your contributions, your courses, your orders and your payments, and to keep the platform secure.
- 3We do not sell your personal data and we do not use advertising or third-party tracking cookies.
- 4Card and mobile money details are entered with our payment provider. We do not store your card number.
- 5We do not send your personal data to external AI services, and AI suggestions are always reviewed by a person.
- 6Heritage records that identify living people are handled under both this Policy and the Rights Policy.
- 7You can ask to see, correct, export or delete your data, or object to how we use it. We reply within 30 days.
- 8You can complain to us, or to Rwanda's data protection authority.
Document details
- Data controller
- IRAGE Corporation LLC, Kigali, Republic of Rwanda
- Version
- 1.0, read together with the DHP Terms and Conditions v3.0 (clause 13) and the Rights Policy v3.0
- Applies to
- The DHP websites and applications, the Digital Repository, DRaaS, e-learning and the Marketplace
- Governing law
- Law No 058/2021 of 13/10/2021 relating to the protection of personal data and privacy, and other laws of the Republic of Rwanda
About this Policy
This Policy explains what personal data IRAGE Corporation LLC ("IRAGE", "we") collects when you use the Digital Heritage Platform ("DHP" or "the Platform"), why we use it, who we share it with, how long we keep it and what rights you have.
It completes clause 13 of the DHP Terms and Conditions. Words defined in the Terms have the same meaning here. Where this Policy and the Terms differ on personal data, this Policy applies.
1. Who is responsible for your data
1.1 IRAGE as controller. IRAGE is the controller of the personal data processed to run the Platform: accounts, contributions to the Digital Repository, e-learning, the Marketplace, payments, messages, support and security.
1.2 Institutions using DRaaS. When an institution uses DRaaS to manage its collections, the institution is the controller of the personal data in its collections and workspace, and IRAGE processes that data on its behalf under a Data Processing Agreement. Requests about that data are best sent to the institution. If you send them to us, we pass them on and help the institution answer.
1.3 Contact. Write to legal@irage.rw about anything in this Policy or to exercise your rights.
2. Personal data we collect
What we hold depends on the services you use. We do not ask for more than the service needs.
| Category | What it includes |
|---|---|
| Account | Full name, first and last name, username, email address, phone number if you give it, profile picture, preferred language and sign-in method. Your password is stored only as a one-way hash. |
| Google sign-in | If you sign in with Google: the name, email address and profile picture that Google shares with your permission. We never receive your Google password. |
| Verification and security | One-time email verification codes, sign-in session tokens and records of failed or refused access. |
| Applications | Information in contributor, instructor and seller applications, such as your organisation, experience, areas of interest, the reasons you give and any documents you attach. |
| Contributions and heritage records | Content you upload or describe, its metadata, attribution, provenance history, consent records, community names and the people a record names, speaks with or depicts. |
| Learning | Courses you enrol in, your progress, comments, reviews and the instructor profiles you view. |
| Marketplace | Your shop details, listings, cart and saved items, orders, delivery addresses, product requests and reviews. |
| Payments | Amount, currency, payment method (mobile money or card), status and transaction references. Only the phone number you pay with is shared with the payment provider to process the payment. |
| Messages and community | Conversations, messages and reactions, article comments and claps, the authors you follow, notifications and reports you file. |
| Institutions | Your memberships, roles, invitations and access requests, and an audit trail of actions in institutional workspaces. |
| Legal records | Which version of the Terms and the Rights Policy you accepted, and when. |
| Technical data | IP address, browser and device type (user agent), pages and features requested, error logs and timestamps. |
3. Where your data comes from
- From you, when you create an account, fill in a form, upload content, enrol, buy, sell, send a message or contact us.
- Automatically, from your browser and our servers when you use the Platform (technical data and security logs).
- From Google, if you choose to sign in with Google.
- From our payment provider, which confirms whether a payment succeeded.
- From an institution or organisation that invites you to its workspace.
- From other contributors, when a heritage record they document names, quotes or depicts you.
4. Why we use your data and on what legal basis
We use personal data only for the purposes below, each on a lawful basis recognised by Law No 058/2021.
| Purpose | Legal basis |
|---|---|
| Create and run your account, sign you in and verify your email | Performance of our agreement with you (the Terms) |
| Provide the services you ask for: hosting and displaying contributions, courses, orders, shops, messages and institutional workspaces | Performance of our agreement with you |
| Process payments and keep transaction records | Performance of our agreement, and legal obligations under tax and accounting law |
| Review applications from contributors, instructors and sellers | Steps you ask us to take before entering into an agreement |
| Record consent and provenance for heritage records | Consent of the people concerned, and our legitimate interest in preserving accurate and accountable records |
| Send service emails, such as verification codes, receipts, decisions and notices of changes | Performance of our agreement, and legal obligations |
| Keep the Platform secure, prevent fraud and misuse, and investigate reports | Our legitimate interests and those of other users and communities |
| Record your acceptance of the Terms and the Rights Policy | Legal obligations and our legitimate interest in proving acceptance |
| Comply with the law, court orders and lawful requests from authorities | Legal obligations |
Where we rely on consent, you can withdraw it at any time. Withdrawal does not affect processing that took place before it.
We do not use your personal data for advertising, and we do not sell it.
5. Heritage records about people
5.1 People in records. Oral histories, photographs, films, interviews and other heritage records often identify living people. Contributors must have the consent of the people a record identifies, or another lawful ground, before uploading it, and must record that consent where the Platform asks.
5.2 Sensitive data. Heritage records can reveal sensitive personal data, such as ethnic or social origin, religious or spiritual beliefs, health, or family and clan relationships. We process such data only with explicit consent or another ground the law allows, and we restrict access to it in line with the Rights Policy.
5.3 Balancing preservation and privacy. If you are identified in a record and ask us to correct, restrict or remove it, we review the request with the contributor and, where relevant, the community or institution concerned. We may restrict access rather than delete where the law allows the record to be kept for archiving, research or historical purposes in the public interest, and we tell you what we decided and why.
5.4 Community data. Information that belongs to a community, rather than to one person, is governed by the Rights Policy. This Policy still applies to any personal data it contains.
6. Artificial intelligence and automated processing
6.1 What we use. The Platform has tools that suggest metadata, extract text and help with search. They run on our own systems. Every suggestion is shown as machine-generated and needs a person to accept it.
6.2 No external AI services. We do not currently send your personal data to external AI services. If that changes, we will first assess the provider's data handling, retention and training terms, put a written agreement in place, update this Policy and give notice under section 15.
6.3 No training without permission. We do not use your personal data or your content to train AI models without separate, specific permission, as clause 9 of the Terms requires.
6.4 No decisions by machine alone. We do not make decisions that produce legal or similarly significant effects for you based solely on automated processing. Applications, reviews, reports and account decisions are made by people.
7. Cookies and browser storage
We use only the cookies and browser storage the Platform needs to work and to remember your choices. We do not use advertising cookies or third-party analytics trackers.
| Name or type | Why we use it |
|---|---|
| ACCESS_TOKEN and REFRESH_TOKEN (cookies) | Keep you signed in securely. They are HttpOnly, so scripts on the page cannot read them, and they are removed when you sign out. |
| NEXT_LOCALE (cookie) | Remembers the language you chose. |
| sidebar_state (cookie) | Remembers whether you collapsed the dashboard sidebar. |
| Local storage | Keeps your basic profile details for faster pages, your recent marketplace searches, the last institution you opened, unsaved article drafts and layout preferences. It stays on your device. |
You can clear cookies and local storage in your browser settings. If you block the sign-in cookies, you will not be able to stay signed in.
8. Who we share your data with
8.1 Service providers. We use providers that process personal data for us, under written terms that require confidentiality and security and forbid using the data for their own purposes:
- Hosting and storage providers for our servers, database and file storage.
- An email delivery provider for service emails.
- XentriPay, our payment provider, for mobile money and card payments. Card and mobile money details are entered with XentriPay and handled under its own terms.
- Google, only if you choose to sign in with Google.
8.2 Other users. Some information is visible to others because of how the service works: your public profile and published contributions, your reviews and comments, your shop and listings, and your messages to the people you write to. When you buy from a shop, the seller receives the name, contact details and delivery address needed to fulfil your order.
8.3 Institutions. If you join an institution's workspace, the institution can see your membership, role and the actions you take there.
8.4 Authorities. We disclose personal data to courts, regulators or law enforcement only when the law requires it or to protect the rights, safety or property of people and communities. Where the law allows, we tell you first.
8.5 Changes to IRAGE. If IRAGE is restructured, merged or sold, personal data may pass to the new operator, which must honour this Policy. We will tell you before that happens.
9. Where your data is stored
We store personal data in Rwanda unless we hold the authorisation or registration that permits storage or transfer outside Rwanda. Any transfer uses a lawful route, including the standard contractual clauses issued by the Data Protection and Privacy Office where they apply.
Some providers, such as Google for sign-in, process data outside Rwanda under their own terms when you choose to use them. We carry out the impact assessments the law requires before any cross-border transfer or high-risk processing.
10. How long we keep your data
We keep personal data only as long as we need it for the purposes in section 4, then delete or anonymise it.
| Data | How long |
|---|---|
| Account data | While your account is open. After you ask us to close it, we delete or anonymise it, except what we must keep for the reasons below. |
| Applications that were not approved | Personal fields are erased 12 months after the application is declined or withdrawn. |
| Payment and order records | For the period tax and accounting law requires. |
| Messages, comments and reviews | While your account is open, unless you delete them sooner. |
| Security and audit logs | As long as needed to protect the Platform and investigate incidents, then deleted. |
| Legal acceptance records | While your account is open and for as long as needed to establish or defend legal claims. |
| Heritage records and their provenance | As long as the record is preserved. Personal data in them is limited to what the record needs, and access is restricted under section 5. |
11. How we protect your data
- Encrypted connections (HTTPS) between your browser and the Platform.
- Passwords stored only as strong one-way hashes.
- Sign-in tokens held in HttpOnly cookies.
- Role-based access, so staff and institution members see only what their role needs.
- Rate limits on sign-in and other sensitive actions.
- Malware scanning and integrity checks on files uploaded to institutional collections.
- Audit trails of actions in institutional workspaces.
No system is perfectly secure. If a personal data breach puts you at risk, we notify the supervisory authority and you within the time the law requires and tell you what you can do to protect yourself.
You help protect your account by keeping your password private and telling support@irage.rw at once if you suspect someone else has used it.
12. Your rights
Under Law No 058/2021 you have the right to:
- be informed about how we use your personal data;
- access the personal data we hold about you and get a copy;
- have inaccurate or incomplete data corrected;
- have your data erased where there is no longer a lawful reason to keep it;
- restrict how we use your data while a concern is resolved;
- object to processing based on our legitimate interests;
- receive your data in a structured, commonly used format and have it sent to another controller (data portability);
- not be subject to a decision based solely on automated processing that significantly affects you;
- withdraw consent at any time where we rely on it;
- designate an heir to your personal data, or be represented by someone you authorise, where the law allows.
How to ask. Write to legal@irage.rw from the email address on your account, or tell us how to confirm your identity. We may ask for proof of identity before we act. Requests are free. We reply within 30 days and tell you if we need more time and why.
You can correct most account details yourself in your profile settings.
13. Children
The Platform is not designed for children on their own. People under eighteen may use designated educational or community services only under the supervision of a parent, guardian, school or institution, as clause 2.2 of the Terms says.
We process the personal data of a child under sixteen only with the consent of the person who holds parental authority, as the law requires. If you believe a child's data was provided without that consent, write to legal@irage.rw and we will delete it.
Heritage records that identify children need the consent of a parent or guardian, and are given restricted access by default.
14. Complaints
If you are unhappy with how we handle your personal data, tell us first at legal@irage.rw so we can try to put it right. We acknowledge complaints within five business days.
You also have the right to complain to the National Cyber Security Authority (NCSA), which supervises data protection in Rwanda through its Data Protection and Privacy Office.
15. Changes to this Policy
We update this Policy when our services, providers or legal duties change. For material changes we give at least 30 days' notice by website notice, email or account alert, with a summary of what changed. The version number and date at the top show which version is in force, and previous versions stay available on request.
Contact
Questions about these documents, or a concern about how heritage is handled? Write to the team responsible.