How Pelican protects your information
Your information.
Your intelligence.
Your say.
Security is about more than where a server lives. It is also about who can read a record, what an agent can do, which device can connect and what happens before information leaves.
Questions worth asking
Clear boundaries.
Clear answers.
Does local mean nothing ever connects to the internet?
No. Local inference and approved outside connections are different paths. Email, a business integration or another external service may require a connection and transfer information. Your walkthrough should show what leaves, to whom and under which permission.
Can my phone see everything on the Mac?
A device’s access depends on its pairing, assigned role and the user’s permissions. A reception kiosk or room screen is not intended to expose the owner’s whole workspace. Supported hardware and each enabled workflow are confirmed during installation.
Will an agent send things without asking every time?
Only where an applicable standing grant authorizes that supported action. You define the scope and can revoke it. A new agent starts without a standing sending grant, and changing its general work permission is not itself a sending grant.
Does this website store our practice or property data?
No. This marketing website is separate from the Pelican products. It has no customer-record upload or product login. The contact form only prepares an email draft; keep patient, client and other confidential records out of it.
What should we verify before using Pelican?
Walk through your actual configuration: selected sources, roles, a paired device, an agent proposal, an AKF check and an outgoing handoff. Confirm supported features, device readiness, backup/recovery and your organization’s requirements before relying on the deployment.