Cardinal by RAMCOREOpen Cardinal

Privacy policy

Last updated 18 November 2026. See also our Terms of service.

This policy explains what personal information Cardinal collects, why, who it is shared with, and the choices you have. It is written with South Africa's Protection of Personal Information Act (POPIA) in mind.

Who we are

Cardinal is provided by Michael Levendig, trading as RAMCORE ("we", "us"), at cardinal.ramcore.io. Our Information Officer under POPIA is Michael Levendig, reachable at mic@ramcore.io.

Cardinal is software for a services business. It tracks time, hours and AI use, and handles quotes, invoicing, a ledger, messages to clients and an AI assistant (Cardinal AI).

We decide how your account information is used. The business records you keep in Cardinal, including your clients' details, are yours: you decide what goes in and why, and we process them on your behalf.

What we collect, and why

Your account

  • Your name and email address, to sign you in and to show who did what. Your password is handled by our sign-in provider (Neon); Cardinal itself never stores it.
  • Your workspace membership and role, to decide what you can see and do. If you set them, also your job title and time zone.
  • The email address of the Claude account you use with Cardinal, to match your Claude usage to you.

Business records you enter or create

Clients and their contacts, projects, time entries, quotes, invoices and payments, ledger entries, deals, your company details and logo, messages to clients (recipients, subject, body and status), your Cardinal AI chats and questions you ask the help guide. We use these only to provide Cardinal to you and your workspace.

Claude Code usage from your computer

When you set up Cardinal on your computer, Claude Code sends Cardinal usage telemetry: tokens, cost, models, active time, counts of prompts and tool results, and the names of tools and skills used. A session-end hook sends when a session closed and the folder it ran in.

No prompt or response text is ever collected. Claude Code can include prompt and response text in telemetry only if special options are turned on, and Cardinal never turns them on. Any text that arrives anyway is dropped.

If the workspace owner installs Cardinal's runner on their computer, it reads Claude Code's session history on that computer and sends a summary of each session: start and end times, tokens, cost and models, the folder, git repository and branch, the names of files edited and how many edits, tool names and counts, links to pull requests, and the short titles Claude Code gives each session and each sub-agent task. It does not send your prompts or Claude's replies.

Cardinal also records where a Claude Code session ran (a terminal, VS Code or the Claude app's Code tab), and a "Using Claude" tag if you set one on a timer. It does not track the Claude app's chat, the browser or a phone; you can log that time yourself. Cowork usage reports, a Claude chat export and a member's own transcript sync are off unless the workspace owner turns them on, and each sends times and counts only, never words.

Recording the Claude use of members who are not the workspace owner is off until the owner of that workspace, or a person the owner has given full access, switches it on. Before anything about you is recorded, Cardinal shows you a notice. It says what is recorded: when you start and stop, for how long and in which folder, which model and tools, and what it cost, never what you or Claude said. It also says that the workspace's owner, people with full access and the people who manage you can see it, and that Cardinal logs each time they look. You can answer "OK" or "Don't record me", and you can change your answer on Your account at any time. Saying no stops recording of you at once, on every route, including anything the owner set up. What was recorded before is kept. To ask for it to be removed, write to the address at the end of this page.

Apps you connect to Cardinal

If you connect an app such as Claude to Cardinal, or use the Cardinal command line, it reads your workspace with a token you allow, and it can read, and with your permission add meetings and notes to your own meetings. It never confirms anything: only your press of Confirm in a signed-in Cardinal session does. What it reads leaves Cardinal for that app and its provider, under your own agreement with them. Cardinal keeps a record of each call (the tool, when, and which records) and you can revoke the token at any time.

Notes you bring in from your own notetaker are kept with that meeting as your private prep, with the link you gave, until you delete them or the meeting, or your account is erased. A copy you share to a client's record stays there.

Your calendar

There are two ways Cardinal can see your day, and you choose. If you connect Google Calendar on Your account, Cardinal's server reads your events from Google when you open Plan or Today (at most every 10 minutes) or press Refresh. If your workspace turns on Google Meet transcripts, the server also looks for the transcript of a meeting you organised, a few times in the day after it ends. Or, without connecting anything, your own Claude on your computer reads that day's events through your own calendar connector when you ask.

From either calendar, Cardinal keeps each event's times and title, a one-line location and how many people are invited, the domains of the people invited, and a Meet, Zoom or Teams link when there is one. From a connected Google calendar only, it also keeps who was invited: their names and their replies (yes, no, maybe or no reply), up to ten people for an event, and whether the invitation has any text. We keep people's names only as the invitation gives them, never their email addresses, and someone it gives no name for is shown as Guest. The text of an invitation is kept only when you save it as a prep note. Cardinal keeps a day's calendar until you ask us to delete your account, and disconnecting a calendar does not remove days already read. When you connect Google Calendar, the refresh token is sealed with AES-256-GCM and access tokens are never stored. Your calendar is private to you: nobody else in your workspace sees it, and these names and replies are never sent to Claude, to your clients or into your morning brief. A Meet transcript is handled differently: see Google Meet transcripts. The request and Claude's raw answer are cleared from Cardinal's job queue once the job ends.

Google Meet transcripts

If your workspace turns on Google Meet transcripts and you allow it, Cardinal reads Google's transcript of the Meet meetings you organise, shortly after they end, and keeps a copy on that meeting. It holds what other people said. For a meeting with one of your workspace's clients, the copy is also filed on that client's record: people who can open clients see a summary once your Claude has written it (until then, only that a transcript was filed), and the workspace owner and the people the owner chooses can read the full text. The summary is written by your own Claude on your computer, which is sent the transcript for that purpose. A meeting with no client stays visible to you alone. It stays until you or the owner delete it, or your account is erased. Cardinal does not read recordings or Gemini's notes. Text you read through Cardinal AI stays in your own chat history.

When your client opens a share link

When someone opens a link you shared to an invoice, quote or deck, Cardinal records when it was first and last opened and how many times. Cardinal does not store the visitor's IP address: it is used only in memory, to limit how often a link can be opened. Shared pages tell browsers not to pass their address on to other sites, and ask search engines not to index them.

Technical information

Our hosting provider keeps server and request logs, which can include IP addresses and browser details, for a limited time. We use them to keep Cardinal running and secure.

Google user data

If your workspace owner connects a Google account to send email, or you connect your own Google Calendar, Cardinal asks Google for these permissions:

  • Send email as you (gmail.send).
  • Your email address and sign-in identity (openid, email), so Cardinal knows which Google account is connected.
  • See the events on your calendars, read-only (calendar.events.readonly), only if you connect Google Calendar.
  • See your Google Meet meeting records and transcripts (meetings.space.readonly), only when your workspace turns this on.

Cardinal sends only the messages you approve, or that an always-allow rule you set covers, from the address you choose. It lists your send-as addresses so you can pick one. Cardinal never reads, searches or stores your inbox or any other mail: it has no permission to. It keeps the connected account's address, the permissions granted, your verified send-as addresses and names, and a copy of each message it sent for you in your workspace's records.

Calendar access is separate and optional. Any member may connect their own calendar on Your account, and nobody else in the workspace sees it. Cardinal can only read events: it cannot create, change or delete one. It keeps times, titles, a one-line location, the domains and, from Google, the names and replies of the people invited, and a Meet, Zoom or Teams link. It keeps an invitation's text only when you save it as a prep note.

Google's long-lived refresh token is encrypted at rest with AES-256-GCM. Short-lived access tokens are not stored.

Google user data is never sold, never used for advertising, never used to train AI models, and never transferred to anyone except as needed to send your mail, show your calendar and, when your workspace turns it on, file your Meet transcripts as this page describes, which includes sending a transcript to your own Claude on your computer to write its summary.

Cardinal's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

To disconnect Gmail, go to Comms › Sending setup › Disconnect. To disconnect your calendar, go to Your account › Disconnect. Cardinal revokes its access at Google and deletes the stored token (if the same Google account is still connected to another Cardinal workspace, access stays until that workspace disconnects too). If the same Google account also sends your workspace's email, disconnecting one keeps Google's permission until the other is disconnected too. You can also remove Cardinal at myaccount.google.com/permissions.

People you email

When you message your clients through Cardinal, we process their details on your behalf. You are responsible for having a lawful basis to contact them. Cardinal records consent and opt-outs, and will not send to an address that has opted out.

Who we share information with

We never sell personal information. We use these service providers to run Cardinal:

  • Vercel: hosting, server logs, and storage for our encrypted weekly backups.
  • Neon: the database and sign-in.
  • GitHub: runs the weekly backup job.
  • Upstash: short wake-up messages that tell your computer there is work. They carry internal ids only, no personal information.
  • Resend: Cardinal's own emails (invites and the weekly digest), and messages you send through Cardinal mail, if you use it.
  • Google: only if you connect Gmail, to send the messages you approve, or Google Calendar, to read your events and, when your workspace turns it on, the transcripts of Meet meetings you organise.

Cardinal AI and Cardinal's drafts run on your own computer, through your own Claude account. Cardinal sends your computer a job made from your workspace's data, your own Claude answers it, and the answer comes back to Cardinal. Anthropic handles that under your own agreement with them. Cardinal's servers do not send your data to an AI provider.

In a firm's workspace, Cardinal AI answers each person through the runner on that person's own computer and their own Claude account. Cardinal sends that computer only what the person's own pages show them, and Anthropic handles it under that person's agreement with them.

Your information is stored and processed outside South Africa, in the United States. Each provider is bound by its own data protection terms. We may also disclose information where the law requires it.

Cookies and browser storage

  • Sign-in session cookies, to keep you signed in.
  • A short-lived cookie (10 minutes) while you connect a Google account.
  • A cookie that remembers whether you collapsed the sidebar.
  • Your browser's session storage keeps the Cardinal AI panel's place and any unsent message in that tab.

Cardinal uses no advertising or analytics trackers.

Security

Cardinal is served only over HTTPS. Connection secrets, such as the Google token, are encrypted at rest. Access is limited by workspace and by role, so people see only their own workspace and what their role allows.

How long we keep information

We keep your information while your account is active. Ask us to delete your account and data and we will do so within 30 days, except records the law requires us to keep (for example issued invoices, for tax).

Encrypted backups are not edited after they are made. We keep daily backups for 7 days, weekly ones for 4 weeks, monthly ones for 12 months and one at each tax year end for 7 years, then delete them, so deleted information can remain in a backup until it expires.

Deleting your information

To delete your account, go to Your account › Your data › Delete my account. Your access ends at once and we finish within 30 days. A workspace's own records, such as time entries and issued invoices, stay with that workspace under the name Former member. To download your data first, use Download my data on the same page.

Your rights

Under POPIA you may ask to:

  • see the personal information we hold about you;
  • correct it, or delete it;
  • object to how we process it.

Contact our Information Officer, Michael Levendig, at mic@ramcore.io. If you are not satisfied with our answer, you can complain to the Information Regulator at inforegulator.org.za.

If you are a client of a business that uses Cardinal, contact that business first: it decides what it keeps about you. We will help it answer.

Changes to this policy

We will update this page when Cardinal changes how it handles personal information, and change the date at the top.

Contact

Michael Levendig, trading as RAMCORE
354a Jan Smuts Avenue, Craighall, Johannesburg, 2196
Email: mic@ramcore.io
Website: ramcore.io