What we hold, why, and the choices you have.
Revised 3 November 2026
Diggr is operated by Alcaras LLC, a company registered in the United Arab Emirates. Alcaras LLC is the data controller for your account and for the public directory. For your private workspace, the data you and your team add or connect, we act on behalf of your organisation (or of you, if you use Diggr on your own): it decides how that data is used, and we use it only to provide Diggr. You can reach us about anything on this page at contact@getdiggr.com.
Diggr keeps two very different kinds of data: your private workspace, and a public professional directory of telecom and media companies and the people who work at them. This notice covers both.
Your account (your name, your work email and your organisation), and everything you and your team create or bring in: your setup, notes, tasks, meetings, pipeline and the contacts you import from your address book or your CRM. All of it is private to your own workspace: isolated to your organisation at the database level, never shared with any other customer, never added to the public directory, and never sold.
When you connect a CRM, Diggr reads from it to match your accounts and contacts against the market. When you connect a mailbox, Diggr keeps the mail people outside your company send you, private to you, with the date, the subject and Outlook’s short preview of your replies, and reads each new message once to summarise it and suggest a next step. The sender’s name and yours are replaced, and contact details removed, before it is read. Diggr never keeps or reads mail that is only between you and your colleagues. If you switch on logging your email conversations, Diggr files each conversation with a company you follow into that company’s history, for you only: the subject and the day, never the message. Diggr never writes to your mailbox.
Diggr writes to your CRM only if you switch on Sync to your CRM and press send. It then only adds what you created in Diggr, or fills a field your CRM left blank: it never deletes anything, never overwrites what your CRM holds, and never puts Diggr’s own market intelligence into your CRM.
If you connect Zoom and turn on Read my recorded meetings, Diggr reads the transcript of each meeting you record to the Zoom cloud, once, to draft a meeting note for you to check. The full names of the people speaking are replaced before the transcript reaches the service that drafts the note. Diggr keeps only the note, never the recording or the transcript. A note you do not log or discard is deleted after 30 days.
When you book a meeting in Diggr and choose Zoom, Diggr asks your own Zoom account to create that one meeting when you press Open, so its join link can go into the invitation you send from your own calendar. Diggr keeps neither the meeting nor the invitation.
Connecting is your choice, made in Settings, and it asks Google for two things only: read-only access to the events on your calendar, and the email address of the Google account you connected, so we can show you which one it is. Diggr never creates, changes or deletes anything on your calendar. It does not read Gmail, your contacts, your files or anything else in your Google account.
What Diggr reads from each event, and why:
Your calendar is read live and not stored. Each time a screen shows your meetings, Diggr asks Google again. Two things are kept, both only for you:
When you ask Diggr to prepare you for a meeting, the meeting title and the job titles of the people in it - never their email addresses - are sent to our AI engine (Google Gemini) to write that one briefing. We do not use anything from your calendar to train an AI model.
Your calendar is private to you. It is not shown to your colleagues, not added to the shared directory, not sold, and not used for advertising. No person at Diggr reads it, unless you ask us to for support, or the law requires it. The permission Google gives us is stored encrypted.
To stop: press Disconnect in Settings. Diggr deletes its permission, tells Google to withdraw it, and reads nothing more. You can also remove Diggr from your Google account at any time, at myaccount.google.com, under Security. Meetings you logged stay in your activity until you delete them, or until your account is deleted.
Diggr’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Some Diggr features send data to our AI engine (Google Gemini) to write a result for you. Most run when you ask - researching an account, preparing for a meeting, or reading a document you upload. Some run by themselves: the suggestions on your Today page and your monthly report are written from a short summary of where you stand with each account you follow, and, if you connect a mailbox, new mail is read as described above. Only the inputs needed for each result are sent. That can include the text of your own notes and logged conversations for the account you are researching, including those brought in from your CRM, and for the document reader it is the whole file you uploaded. We do not use any of it to train AI models. Nor do our AI providers: Google does not use what we send its paid Gemini service to improve its products, and model training is switched off on the Claude accounts behind the tools we build Diggr with, except for a session Anthropic flags for a safety review. Section 3 of the Terms of Service has the details.
When you share a story on LinkedIn from Diggr, Diggr makes a page of it on getdiggr.com that anyone with its address can read. The page names nobody: not you and not your company. It holds the story and its source, never your notes, sales opportunities, contacts or targets. You can take it down at any time with Stop sharing.
When you leave your address on our website, we keep what you gave us - your work email and, if you filled in the second step, your name, your company, your role, and what you told us you want from Diggr - so that we can decide who to invite and get in touch with you. We send you an acknowledgement, and the request is emailed to us. We do not sell it, share it, or add it to the public directory, and we use it for nothing else.
When you send a message from the contact box on our prices page, it reaches our inbox as an email with your work email address, so that we can reply to you. That email is the only copy of your message and your address that Diggr keeps, and we use them only to answer you.
When you open a page of getdiggr.com without signing in, Diggr counts the visit itself, without cookies and without storing anything on your device: the page, the site you came from, the link’s campaign tags, your country and your type of screen, under a code that changes every day and cannot be traced back to you once the day is over and its random key is deleted, within two days. Your IP address is used only to make that code and is never kept. We keep these counts for up to 13 months.
This part is for anyone who finds their professional details in Diggr. It is our notice under Article 14 of the GDPR.
For everyone in the directory: name, job title, employer, and a link to the public page we took it from. Where the same public sources carried it, we also hold a photograph, a professional biography (always shown with a link to where it was published), a link to a public professional profile (we store the address so a reader can click through), the city the role is based in, the sales region the role covers, and the date the source showed them in the role.
Two things are worked out by Diggr from the job title rather than taken from a page: a seniority band and a role area (engineering, procurement, marketing and so on). Everything else was already public before we held it.
We hold no email addresses and no phone numbers for anyone in the directory, and nothing about a person’s private life.
Diggr draws on publicly accessible sources, such as companies’ own websites, their announcements and public filings.
The directory is what Diggr shows its users. Your workspace data stays inside your organisation. To run Diggr we use a small set of service providers - hosting, database, backup storage, web search, email delivery and AI processing - which handle data only on our behalf. We do not sell personal data and we do not use it for advertising.
Diggr’s database is in the European Union (Ireland). Some of our service providers are based in the United States, so data passes to them there when a feature needs it. One, DeepSeek, is based in China: it searches and reads public web pages for the directory, so the public facts the directory holds about a person can pass to it there. Your workspace data stays out of it.
Your account and workspace: while your account is open. When it is closed, we wait 30 days, so that a mistake can be undone, and then delete it. We keep a safety copy of what we delete until you ask us to remove it, and our nightly backups keep theirs for 30 days. Early-access requests: until you ask us to delete them. A directory record: only while it stays accurate and relevant to the market; we re-check records, and those that go stale are refreshed or removed.
You can ask us to tell you what we hold about you and where we got it, to correct it, to delete it, or to stop using it (to object). If you are in the European Union or the United Kingdom, the GDPR applies to this directory even though Diggr is based outside Europe, and you also have the right to complain to your local data protection authority.
How to ask. If you are in the directory, use getdiggr.com/remove to have your entry corrected or removed: we email you one link and nothing is recorded until you press the button in it. Or write to us from your own email address at contact@getdiggr.com, with REMOVE or CORRECT in the subject, your name and the company you work for. When you object or ask for removal we act promptly and add you to a do-not-re-add list, so the same details are not picked up again. For your account, your workspace or an early-access request, write to the same address, or edit and delete what you added yourself at any time.