The procurement-ready posture. Where your data lives, how authentication works, how the audit trail holds up, and what we do and don't have access to.
If you're an IT lead, procurement officer, or principal evaluating [GRYD] for client engagements, here's what you need to know in 60 seconds.
Lab results, screening output, and exceedance data live in your browser's IndexedDB and your Excel workbook. They don't move to our servers. Only public regulatory limits travel over the network.
Sign in with the same enterprise identity your team already uses. No separate password to manage, no shadow user directory, no on-prem AD federation required.
Every screening run is stamped with the regulatory pack version, timestamp, and user. The audit trail lives in the workbook you already control — portable, archivable, regulator-ready.
An honest diagram of every place a piece of your data could be at rest or in transit.
[GRYD] doesn't run its own password store. We never see, hash, store, or transmit your password. Instead, we delegate authentication to Microsoft Entra External ID (formerly Azure AD B2C / External Identities).
That means:
The defensibility of an environmental closure depends on being able to answer, two years later, "what guideline values were active when this run was made, and against what dataset?" The [GRYD] audit trail is purpose-built for that question.
AB Tier 2A v2026.04)
The questions that come up in every IT, legal, and procurement review. Honest answers.
In two places, both yours: the Excel workbook on your machine (governed by your OneDrive / SharePoint / local-disk policies), and the IndexedDB store in your browser profile. Nothing about a screening run is persisted to [GRYD] infrastructure.
If your workbook is stored in a Canadian region of OneDrive / SharePoint, your data is in Canada. The CDN that serves regulatory packs uses geographically distributed read-only edges, but it only serves public regulatory text — not your data.
No. We don't have a database of customer screening results because we don't store them. The only thing we can see is anonymized usage telemetry (e.g. "Decay Tracker chart was opened today") that you can disable in settings.
Your workbook keeps working. Any screening outputs, exceedance tables, and audit-trail entries that were written into the workbook stay in the workbook. There is no vendor lock-in — uninstalling [GRYD] doesn't blank your data.
The Ask GRYD agent can be configured per organization: on-device inference, your own private endpoint, or off entirely. By default, the agent only receives the screening results from the current workbook, not raw lab data — and never persists conversation history outside your session.
SSO via Microsoft Entra External ID is the default sign-in path for every customer. SCIM-based provisioning for team workspaces is on the near-term roadmap — talk to us if you need it before general availability.
Because we don't hold customer screening data, the typical "data breach" surface is much smaller than a SaaS competitor's. For any auth, identity, or infrastructure incident, our policy is direct notification of affected tenants within 72 hours, plus a public post on the changelog and security page.
Yes. Email security@grydlogic.com with your standard questionnaire (CAIQ, SIG Lite, custom) and we'll return a completed response.