A data security platform. It connects to systems you already run, finds personal and regulated data inside them, labels what it finds by sensitivity, and masks or removes the exposure. It reads content inside scanned documents and images as well as native files.
No. Engagements often start with one department or a single share drive. Licensing scales with data volume and source count, so a small deployment is priced as one.
On your own servers, in a cloud region you control, or as a hosted service. Where you put the server decides your jurisdiction. Deployment options
Discovery, indexing, optical character recognition and classification all run on the GEODI server. The AI question answering path sends the prompt and retrieved context to a language model, and never the source documents. Where policy forbids any external call, that model can be self hosted so nothing leaves at all.
Not by itself. Discovery runs read only. Remediation is a separate switch turned on per source with credentials you supply and can revoke, and every action it takes is recorded against an account.
File shares, FTP, SSH, WebDAV, Amazon S3, Dropbox, Google Drive, One Drive, SharePoint, Microsoft Teams, Confluence, Jira, mail platforms, relational databases, web content and endpoints. More than 200 adapters in total.
Yes. Optical character recognition is enabled per project, which brings scanned PDFs, images and archived paper into the same search as native text. This is usually where the surprises are.
Prebuilt recognizers detect payment cards, financial fields, currency values and regional identifiers such as health numbers and social insurance numbers. Dictionaries add keyword matching, and classification rules assign each finding to a class you control.
That depends on their group. Masking and anonymization profiles are bound to user groups, so the same record shows full values to one group, masked values to another, and realistic substitutes to a third.
No, and treat any vendor claiming otherwise with suspicion. It supplies the inventory, the labels, the controls over sensitive content and the audit record. Lawful basis, retention policy, training and certification stay with your program. Where the line sits
PIPEDA, Quebec Law 25, PHIPA, FIPPA and MFIPPA in Canada. HIPAA, CCPA and CPRA, GLBA and SOX in the United States. LFPDPPP in Mexico. PCI DSS across all three.
Licensing is a subscription priced against data volume, source count, the capabilities you need and deployment model. Quotes are built per environment after a scoping conversation. What drives a quote
A scoped demonstration on representative data, at no cost. Most organizations then run a pilot on one real source before committing to a wider rollout.
Yes, across Canada, the United States and Mexico. The process runs five stages and nothing is signed until stage three. How partnering works
Commercial terms are agreed per partner and stay confidential under the distribution agreement, so they are not published. They are discussed once mutual non-disclosure is in place, which happens early.
Register the opportunity and it is recorded against your organization on the submission date, with acknowledgment inside five business days. Where a second partner approaches the same account later, the registered entry is the reference. Register a deal
The partner holds first and second line. Product defects and unresolved technical issues escalate to vendor engineering, and the partner keeps the customer relationship throughout.
Yes, once an agreement is in place. It arrives with sample projects already configured, alongside technical training and a certification path. What enablement covers