In short
- No analytics, no advertising, no third-party trackers, and no cookies besides the one that keeps you signed in.
- We do not ask for your name or email to use the console; a wallet address is enough.
- Data your agents send is used only to evaluate and record their authorization decisions.
- We never receive or store your private keys or recovery phrases. Never send them to anyone, including us.
What we collect and why
| Data | Purpose | Kept |
|---|---|---|
| Wallet address | To sign you in and identify you as a member of your organization. | Until your organization is deleted. |
| Sign-in records | Challenge, time and domain of each sign-in, and the terms version you accepted, kept in the audit trail. | For the life of the organization (the audit trail is append-only). |
| Session | A random token in a cookie; we store only its SHA-256 hash. | 12 hours, or until you sign out. |
| Organization content | Organization name, members and roles, agents, smart-account addresses, policies, API key labels, operations and approvals your agents create. | Until your organization is deleted. |
| API keys | Only a SHA-256 hash and a short non-secret prefix; the key itself is shown to you once and never stored. | Until the agent or organization is deleted. |
| Network address (IP) | Held briefly in server memory to rate-limit sign-in and API use. Not written to our database. | Minutes. |
| Hosting logs | Our host records request metadata (IP address, time, path, user agent) for operations and security. | Per the host's retention, typically days. |
Wallet addresses and transactions are public on the blockchain by nature. The policies, operations and audit records in your organization are not public: only members of your organization can see them, according to their role.
Legal basis
We process this data to provide the Service you signed up for (performance of a contract), and to keep it secure and prevent abuse (our legitimate interest). We do not sell personal data or use it to profile you.
Cookies and browser storage
One strictly necessary cookie, __Host-ps_session, keeps you signed in. It is HttpOnly, secure and same-site, so scripts and other sites cannot read it. The console also remembers which organization you last selected in your browser's local storage. Neither is used for tracking, so no consent banner is needed.
Where data goes
We use these providers to run the Service. Data is stored in the United States.
- Vercel Inc. (USA): Hosting, request logs, TLS.
- Neon (USA, us-east): Postgres database.
- GitHub Inc. (USA): Encrypted database backups (14 days) and source code.
- GoDaddy (USA): Domain name system and email forwarding.
- Robinhood Chain RPC: Gas price and contract-code lookups for the addresses in a request; no personal data is sent.
- Coinbase and Kraken: Public ETH/USD price; no personal data is sent.
Security
Connections are encrypted with TLS. Sessions and API keys are stored only as hashes. Roles are enforced on the server for every request, and the audit trail cannot be altered. Backups are encrypted. See the security model for details.
Your rights
You can ask for a copy of your personal data, ask us to correct it, or ask us to delete your organization and the personal data in it by writing to contact@palisec.tech from an address you control, and proving control of your wallet when we ask. We answer within 30 days. Because the audit trail is append-only, deletion removes your organization as a whole rather than individual records within it. You may also complain to your local data-protection authority.
Children
The Service is not intended for anyone under 18, and we do not knowingly collect their data.
Changes
We will update the effective date when this policy changes and announce material changes in the changelog.
Contact
Privacy questions and requests: contact@palisec.tech.