RATIVERA
Privacy Policy
Effective date: 13 November 2026 · Version: 2026-11-13-v2
1. Who is responsible
TG DevOps Consulting Ltd ("RATIVERA"), 191 Cranston Gate SE, Calgary, Alberta T3M 1L9, Canada. Privacy contact: support@rativera.ca.
2. What we collect
| Category | What | Why |
|---|---|---|
| Sign-in account | Your e-mail address, and the record that you accepted these policies, held in RATIVERA's sign-in directory (Microsoft Entra External ID) when you create an account | to let you in |
| Sign-in identity in RATIVERA | Created only when you create an organization or accept an invitation: a random identifier, your lower-cased e-mail address, status and dates; and a sign-in binding (issuer, a sign-in identifier Microsoft issues for RATIVERA, status, dates) | to show your members list, match invitations and decide who you are (by the sign-in identifier, never by e-mail) |
| Organization data | organization name; members, roles and invitations; actions in the activity timeline | to run your organization |
| Azure environment data you connect | tenant, subscription and cluster identifiers and names; workload, namespace and container names; CPU, memory and throttling measurements read from your Managed Prometheus; Git repository and branch names if you connect Git | to produce recommendations |
| Support communications | what you send to support@rativera.ca | to help you |
| Technical data | two first-party cookies (session and forged-request protection) in the portal; operational logs with opaque identifiers and, when an organization is created, its name | to keep you signed in and the service secure |
We do not collect payment data: billing is not available. We do not use your data for advertising and do not sell it.
3. How your e-mail is used
Your sign-in e-mail is stored as display information (shown to administrators of your organization in the members list) and to match invitations. It is never used to decide who you are. RATIVERA's application automatically sends e-mail for organization invitations (through Azure Communication Services, with no tracking). RATIVERA may also send e-mail manually to answer support requests, give Trial notices, and share important service information. We do not use these messages for advertising.
4. Where it is processed, and who else handles it
Microsoft Azure runs the service and its database in Canada Central; database backups are geo-redundant. RATIVERA's sign-in directory is a Microsoft Entra External ID tenant created with country Canada. GitHub receives requests only if you connect Git (read-only). Google Workspace hosts the support mailbox. Our service providers are Microsoft (Azure, Entra External ID, Azure Communication Services), GitHub (only if you connect Git) and Google (support mailbox); we use no other sub-processor. GitHub and Google may process data outside Canada, and Microsoft personnel may access support data from other regions.
5. How long we keep it
| Data | Kept | Notes |
|---|---|---|
| Your organization's data: clusters, evidence and telemetry from your environment, assessments, recommendations, decisions, members, invitations, activity | until your administrator deletes the organization | RATIVERA does not currently expire evidence or telemetry on a schedule, including after a Trial |
| Records about people after an organization is deleted (section 6) | kept today | see section 6 |
| Database backups | 14 days, then overwritten | data you deleted can remain in a backup for up to 14 days |
| Operational logs | 30 days | opaque identifiers, and the organization name when an organization is created (no e-mail address) |
| Sign-in account in the sign-in directory | until we remove it | if you sign up but never create or join an organization, RATIVERA's database holds no record of you; the directory account stays until you ask us to remove it |
| Support e-mail | 12 months after the last message in the thread, then deleted | kept in our support mailbox |
6. What deleting an organization removes, and what remains
Removed (permanently, in one step, by an administrator): the organization, its members and invitations, clusters and everything attached to them (evidence and telemetry received from your environment, assessments, recommendations, decisions, outcomes, history, notifications), Git connections and mappings, the Azure connection record, the organization's stored connector credentials, and its Trial and entitlement records. Not touched: your Azure resources, your GitHub repositories and App installation, and software you run in your own cluster. Remains after deletion (because other records refer to it, so it cannot simply be removed):
- for each person who used the service: one identity record (random identifier, lower-cased e-mail, status, creation date) and one sign-in binding (issuer, sign-in identifier, status, dates);
- one customer-account record (a random identifier and a creation date, no name or e-mail);
- one deletion record per deleted organization (organization identifier, deletion time, the identifier of the person who deleted it, no name and no e-mail);
- replay-protection identifiers and digests that contain no personal information.
RATIVERA has not yet adopted a procedure to de-identify the retained person records on request, and we do not describe them as deleted. We will update this policy when we do. Until then we can tell you exactly what we hold and what remains, and we will treat your request seriously (section 7).
7. Your rights and how to use them
You can ask to see what we hold about you, to correct it, and to ask for deletion. Write to support@rativera.ca; we verify you before acting, and we aim to answer within 45 days. What we can do today: give you a report of what we hold; correct your e-mail through your sign-in; have your administrator delete the organization; remove your account from the sign-in directory; and tell you plainly which records remain. What we cannot do today: de-identify the retained identity, sign-in binding, customer-account and deletion records under an approved procedure, or remove data from backups sooner than their 14-day schedule. If we cannot verify that you control the sign-in a request concerns, we will not act on it, and we will explain why. You may also complain to the privacy regulator that applies to you (for Alberta, the Office of the Information and Privacy Commissioner of Alberta).
8. Security
Sign-in uses one-time e-mail passcodes; the database requires an encrypted connection; secrets are kept in a managed vault; access between customers is separated in the database; invitations are single-use and tied to the invited e-mail. We do not claim certifications. If we learn of a breach of personal information that creates a real risk of significant harm, we will notify the affected organizations and, where required, the regulator, without unreasonable delay.
9. Cookies
The portal uses two first-party cookies that keep you signed in and protect against forged requests. The sign-in page of our identity provider (Microsoft) sets its own cookies for sign-in. No advertising or analytics cookies are used in the portal.
10. Children, and changes
The service is for business use by people 18 or older. We will post changes to this policy and show a notice in the portal; material changes apply at least 14 days after notice where practicable.
See also the Terms of Service. This policy covers the RATIVERA service at portal.rativera.ca. For how this marketing website handles visitor information (hosting, analytics and enquiries), read the website privacy notice.
