Privacy notice
How Relvista handles personal data: the data your team puts into it, and the data we need to run your account. Written for the businesses that use Relvista, the people who sign in to it, and the people whose details a customer stores in it.
Last updated 17 November 2026
1. Who we are
Relvista is provided by MindForge Technologies LLC, a limited liability company organised under the laws of the State of Wyoming, United States ("we", "us"). For any privacy question or request, contact the contact form at mindforgetech.net with "Privacy" in the subject.
We have not appointed a data protection officer; we are not required to, and the contact above handles all privacy questions.
2. Our two roles
Processor, for your workspace's contents. Your organisation decides what goes into its workspace — companies, contacts, deals, pipelines, tasks, notes, activities, lead-form submissions and email sequences. For this data your organisation is the controller and we are its processor. We process it only on your organisation's instructions and only to provide the service. We do not sell it, use it to train AI models, or combine it across customers. Our data processing terms are section 8 of the terms; ask us if you need a separately signed agreement.
Controller, for account and billing data. For the data we need to run and charge for the service — your name, email address, sign-in details, memberships and roles, the workspace owner's billing details, and our service and security records — we decide why and how it is used, so we are the controller.
3. What data we handle, and where it comes from
Account data (we are controller). Name, email address and profile details, given when you sign up or accept an invitation and held by our identity provider, Clerk; workspace memberships and roles, set by owners and admins; your settings and notification preferences.
Billing data (we are controller). The workspace owner's billing contact, address and any tax ID, entered on Stripe's hosted pages; subscription status and Stripe's customer and subscription identifiers. We never see or store card numbers.
Service and security records (we are controller). Request and error logs held by our hosting provider, Cloudflare, which can include the information your browser sends with each request; the audit log and deal history in each workspace, written by the database and not editable by the application; hashed API keys and invitation tokens. The application itself does not store IP addresses.
Workspace contents (we are processor). Whatever your team records — for example names, job titles, email addresses, phone numbers and company details of contacts; deals, tasks, notes and activities; and the consent evidence recorded before a contact is added to an email sequence. Submissions to public lead forms a customer publishes; each form must link to that customer's own privacy notice.
Connected mailboxes. If a user connects a Google or Microsoft mailbox, we store the subject, sender and time of emails and calendar events — not email bodies or attachments — and they stay private to that user unless they share an item into the workspace. If the user also grants write access, the service can send email and create or update calendar events from that user's account when they ask it to.
What we deliberately do not store: passwords (Clerk handles sign-in), card numbers (Stripe handles payment), and email bodies or attachments from connected mailboxes.
4. Why we use data, and our lawful basis
This covers data we control. For workspace contents, your organisation sets the purposes and is responsible for the lawful basis.
| Purpose | Data | Lawful basis (GDPR / UK GDPR) |
|---|---|---|
| Create and run your account, sign you in, apply your role | Account data | Contract (Art. 6(1)(b)) |
| Send service email: invitations, task reminders, weekly summary, scheduled reports, billing notices | Name, email, settings | Contract (Art. 6(1)(b)) |
| Take payment, issue invoices, calculate tax | Billing data | Contract (Art. 6(1)(b)); legal obligation for tax and accounting records (Art. 6(1)(c)) |
| Keep the service secure: logs, audit history, spam protection, preventing abuse | Service and security records | Legitimate interests (Art. 6(1)(f)) in keeping the service and our customers' data secure |
| Answer support and privacy requests | Contact details and what you send us | Contract (Art. 6(1)(b)), or legitimate interests (Art. 6(1)(f)) if you are not a customer |
| Tell workspace owners about changes to the terms or this notice | Owner's email | Legal obligation (Art. 6(1)(c)) and contract (Art. 6(1)(b)) |
| Establish, exercise or defend legal claims | Records relevant to the claim | Legitimate interests (Art. 6(1)(f)) |
- We do not send marketing email from the service.
- We make no automated decisions with legal or similarly significant effects on anyone. A deal's probability comes from its pipeline stage, not from profiling a person.
- Account data is needed to use the service; without it we cannot create an account.
- Each person can turn off task reminders and the weekly summary in their notification settings.
5. Cookies and similar technologies
We use only what the service needs to work. There are no advertising cookies and no analytics or tracking cookies, so there is no cookie banner.
| Name or type | Set by | What it does | How long |
|---|---|---|---|
| Sign-in cookies | Clerk | Keep you signed in and protect your session | Your session, as Clerk sets them |
| crm_workspace | Us | Remembers which workspace you last opened | 1 year |
| Theme and sidebar width (local storage) | Us | Remember your display preferences on this device | Until you clear them |
| Scroll position (session storage) | Us | Return you to the same place on a page | Until you close the tab |
| Security cookie | Cloudflare | Distinguishes people from automated traffic | Short-lived, per Cloudflare |
| Lead-form check | Cloudflare Turnstile | Checks a form is sent by a person, not a bot | Per Cloudflare's policy |
| Checkout and billing portal | Stripe, on its own pages | Payment and fraud prevention | Per Stripe's policy |
6. Who receives data
Subprocessors. These providers process data for us, only as needed for the purpose shown. We will update this list, and give workspace owners at least 30 days' email notice, before adding or replacing one.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Cloudflare | Hosting and delivery; request and error logs | Every request to the service and its logs | Global network |
| Neon | Database | All workspace contents and account records | EU (Frankfurt, Germany) |
| GitHub | Nightly encrypted database backup | A full database copy, encrypted before it is stored | United States and other GitHub locations |
| Clerk | Sign-in and identity | Name, email address, sign-in sessions | United States |
| Stripe | Subscription billing | The workspace owner's billing and payment details | United States and other Stripe locations |
| Resend | Sending email, including sequence emails | Recipient address, subject and content of emails the service sends | United States |
| Cloudflare Turnstile | Spam protection on public lead forms | Browser and device signals from the form visitor | Global network |
| Only if a user connects a Google mailbox or calendar | Mailbox and calendar details; email sent and events created at the user's request | Where the user's Google account is hosted | |
| Microsoft | Only if a user connects a Microsoft mailbox or calendar | Same as Google | Where the user's Microsoft account is hosted |
Sequence emails are sent through our email provider, Resend, from the service's sending address, with an unsubscribe link in every message.
Recipients your organisation chooses. If your admins set up a webhook (for example to Slack) or an API key, workspace data goes where they direct it, and your organisation is responsible for those recipients. Slack is such a destination, not our subprocessor.
Other disclosures. We disclose data only where the law requires it, for example to answer a valid legal demand, or to protect our rights. We do not sell personal data and do not share it for advertising.
7. International transfers
Workspace data is stored in the EU, in Frankfurt. Some providers above are based in, or access data from, the United States and other countries, and as a US company our own access is also a transfer out of the EU and UK.
Where personal data from the EU, UK or Switzerland leaves those areas, we rely on the European Commission's Standard Contractual Clauses with the UK International Data Transfer Addendum, and on our providers' safeguards, including the EU-US Data Privacy Framework and its UK and Swiss extensions where a provider is certified. For a copy of the relevant safeguards, contact the contact form at mindforgetech.net.
8. How long we keep data
- Workspace data is kept while the workspace exists, including after a trial or subscription ends, so it can still be read and exported.
- Archived records are hidden but kept, so history stays complete, and are erased when the workspace is closed.
- Closed workspaces. When an owner closes a workspace and its subscription has ended, we erase its data within 30 days.
- Inactive workspaces are not deleted automatically. To have yours removed, close it or ask us.
- Backups. Erased data can remain in backups until they expire: daily database branches for up to 7 days, encrypted nightly copies for up to 30 days, and the database provider's recovery window for a further 6 hours. One additional database snapshot taken on 13 November 2026 is kept until we delete it.
- Hosting logs are kept by Cloudflare for up to 7 days.
- Sign-in identity. If you belong to more than one workspace, closing one does not remove your identity. Ask us if you want your sign-in account deleted as well.
- Billing records. Stripe keeps invoices and payment records under its own legal duties, often for several years.
9. Security
Each workspace's data is kept separate by the database itself. All traffic uses HTTPS and the database is encrypted at rest; mailbox credentials, queued outgoing messages and backups are encrypted a second time. No system is completely secure. The Security page says what is in place and what is not yet.
10. Your rights
Depending on where you live, you may have the right to access your personal data and get a copy, correct it, have it erased, restrict or object to how we use it (including use based on legitimate interests), receive it in a portable format, and complain to a data protection authority.
- Workspace owners and admins can export the whole workspace at any time from Settings → Data and privacy; owners can request closure and erasure there too.
- Anyone with edit rights can correct a record; the change is kept in history.
- For anything else, write to us at the contact form at mindforgetech.net. We may need to confirm who you are. We reply within one month, extendable by up to two more months for complex requests — and we will tell you if we extend.
If your details are in a customer's workspace, that organisation controls them and decides what it records, so contact them first. If you cannot reach them, or do not know which customer holds your details, write to us and we will pass your request on and help them answer it. Every sequence email has an unsubscribe link.
Complaints. You can complain to your local data protection authority in the EU, or to the Information Commissioner's Office (ico.org.uk) in the UK. We would like the chance to resolve your concern first.
11. California residents
This applies to the extent the California Consumer Privacy Act, as amended by the CPRA, applies to us.
- Categories collected in the last 12 months: identifiers such as name and email; commercial information such as subscription and billing records; internet or network activity such as request logs; and professional information such as job title and company. Sources, purposes and retention are in sections 3, 4 and 8.
- No sale or sharing. We do not sell personal information or share it for cross-context behavioural advertising, and have not done so in the last 12 months.
- Sensitive personal information is not used or disclosed to infer characteristics about anyone.
- Your rights are to know, delete and correct, and not to be treated differently for using them. Write to the contact form at mindforgetech.net; an authorised agent may act for you if we can verify their authority. We respond within 45 days, extendable once by 45 days with notice.
- Data in a customer's workspace we process as a service provider; send requests to that customer, or to us and we will pass them on.
12. Children
Relvista is a business tool. It is not directed to children under 16 and we do not knowingly collect their data. If you believe a child has given us personal data, write to us and we will delete it.
13. Changes to this notice
When this notice changes we update the date at the top. We email workspace owners at least 30 days before a change that affects how workspace data is used.
14. Contact
MindForge Technologies LLC — the contact form at mindforgetech.net, with "Privacy" in the subject.