GDPR and data processing
How Relia processes your users' personal data on your behalf: our roles, what we process, who helps us, and how we protect and delete it.
In short
- For telemetry from your app, you are the controller and Relia is your processor.
- Inputs are never sent, and common personal details are masked inside the SDK.
- Data is stored on AWS in Mumbai, India; AI processing happens in the United States.
- We notify you of a breach within 72 hours, and a signed DPA is available on request.
Roles
When you install the Relia SDK, your app sends telemetry that can relate to your users. For that data, you are the controller (the data fiduciaryunder India's Digital Personal Data Protection Act, 2023) and Alaknanda Infoplus, which operates Relia, is your processor. We process it only on your documented instructions: these terms, your settings and the requests you make in Relia.
For your own account data, we are the controller; that is covered by our Privacy Policy.
What we process
| Subject matter | Monitoring the customer's software products so Relia can detect, explain and track incidents. |
|---|---|
| Duration | For as long as the customer uses Relia, then until deletion as set out below. |
| Nature and purpose | Collecting, storing, analysing and displaying telemetry; writing incidents, fix plans and answers with AI; sending alerts to channels the customer chooses. |
| Categories of data subjects | The customer's end users who use the monitored product, and the customer's own team members. |
| Categories of personal data | Online identifiers (a random visitor ID, and IP addresses where your app's requests include them), device and browser details, pages and actions in a session, request and error details, and any user identifier the customer chooses to send. Form inputs are never sent and common personal details in text are masked. |
| Special categories | None. Customers must not configure Relia to send them. |
Collecting as little as possible
- What people type into form fields is never sent; only the number of characters is recorded, and replays mask every input.
- Email addresses, phone numbers, street addresses, card numbers and national ID numbers in captured text are replaced before sending.
- Values in database statements are masked, and sensitive request fields such as passwords, tokens and card details are removed, inside the SDK.
- Text people see on the page is not captured unless you switch it on, and session replay is off unless you choose it.
- You can mask or block any element of your app with
data-relia-maskanddata-relia-block.
Subprocessors
You authorise us to use these subprocessors. We bind each to protect the data and tell account owners by email before adding or replacing one, so you can object.
| Provider | What for | Where |
|---|---|---|
| Amazon Web Services | Servers and the telemetry database (ClickHouse) | Mumbai, India (ap-south-1) |
| MongoDB Atlas | Accounts, projects, incidents, settings and session replays | AWS Mumbai, India (ap-south-1) |
| Vercel | Hosting the website and the dashboard; cookieless website analytics and page-speed measurement | Global edge network |
| Anthropic | AI that writes incidents, fix plans and answers | United States |
| Dodo Payments | Subscription payments and invoices | Payment processor |
| Hostinger | Sending email: verification, alerts and summaries | Email service |
| Google and GitHub | Signing inOnly if you choose to sign in with them | United States |
Where data is stored and transferred
Relia stores telemetry and account data on Amazon Web Services in Mumbai, India (ap-south-1), including MongoDB Atlas on AWS in Mumbai. For customers in the European Economic Area, the UK or Switzerland, this is a transfer outside those areas. AI processing takes place in the United States, where only the evidence needed for each task is sent. We will put appropriate safeguards for these transfers in writing in a data processing agreement on request.
Security measures
- Every read is scoped to the project that owns the data, with an isolation test covering every route that takes a project.
- Each project sends with its own ingest key; team roles (owner, admin, member, viewer) control access.
- Short-lived sign-in tokens with rotating refresh, bcrypt-hashed passwords and verified email addresses.
- Deploy-platform tokens are stored encrypted and never sent back to the browser.
- An audit log of account and project actions, and rate limits on abuse-prone endpoints.
The full list is on our Security page. Only people who need access to run the service have it, and they are bound to keep the data confidential.
Breach notification
If we become aware of a personal-data breach affecting your data, we will notify you without undue delay and within 72 hours, with what we know about its nature, the data and people affected, the likely consequences and what we are doing, so you can meet your own obligations.
Helping you with your users' rights
If one of your users asks to access, correct or delete their data, we will help you respond. Most requests can be handled by deleting the relevant project data or sessions; for anything else email relia@alaknandainfoplus.com. If a request reaches us directly, we pass it to you rather than answering it ourselves.
Retention and deletion
| Data | How long we keep it |
|---|---|
| Requests, errors and traces; user sessions and their events; AI-agent runs; app log lines; session replays, if you switched them on | Your plan's history: 7 days (Free), 30 days (Growth) or 90 days (Pro), counted from when the data was recorded. Older data is deleted automatically every day. |
| Detailed inner steps of requests that completed normally | 7 days. The request itself and every error stay for your plan's full history. |
| Database query statistics, uptime check results and server metrics | 90 days. |
| Anything an open incident cites as evidence | Until the incident is closed, then the rules above apply. |
| Aggregated per-route statistics (counts, response times, error rates; no request content) | 2 years. |
| Audit log of account and project actions | 365 days. |
| AI usage records (which feature ran and its cost; no prompts or answers) | 400 days. |
| Incidents, account, team and project settings | While your account or project exists. |
When you delete a project, all of its data is deleted. When you ask us to delete your account, we do so within 30 days, and copies in routine backups are removed as those backups expire.
Data processing agreement
This page sets out how we process data for you. If you need a signed data processing agreement, including the transfer terms your law requires, email relia@alaknandainfoplus.com and we will send one.
Contact
Privacy questions, requests and complaints go to our Grievance Officer, who also handles GDPR matters.
Grievance Officer, Relia
Alaknanda Infoplus, a sole proprietorship registered in Gujarat, India
222, Saketdham Society, Spinning Mill, PunagamIshwarkrupa Society, Bombay MarketSurat, Gujarat 395010, India
Email: relia@alaknandainfoplus.com
You may also complain to your local data protection authority. These terms are governed by the laws of India, with the courts of Surat, Gujarat.