Security & trust
Your bids are competitive assets. We treat them like one.
Everything below is how Palmar actually works today — stated plainly, including what we don't have yet.
Encrypted in transit and at rest
All traffic is TLS-encrypted, and tenders, drafts and saved answers are encrypted at rest. There is no unencrypted path to your bid content.
Role-based access control
Workspace roles (Owner, Admin, Editor, Reviewer) scope who can see and edit which bids. Sessions are cookie-based with secure, httpOnly tokens; sign-in is passwordless (Google, Microsoft, or email link) — there are no passwords to leak.
Your data is never training data
We never train public or shared models on your tenders or responses, and our AI providers are contractually bound the same way. Your past bids improve your answer library — and nothing else.
Tenant isolation
Every query is workspace-scoped at the API layer. One workspace can never read another's documents, requirements or drafts.
Deletion on request
Ask, and your workspace's documents, drafts and derived data (including embeddings) are deleted. Export your responses any time before that.
Built for regulated procurement
Palmar exists for government and enterprise tenders — confidentiality of bid material is the product's core constraint, not an afterthought.
Certifications — a straight answer
We're an early-stage company and we don't yet hold SOC 2 or ISO 27001 certification. Independent certification is on our roadmap as the team grows; until then, we'd rather tell you exactly how the system works than show you a badge. Send us your security questionnaire — a founder answers it directly, usually within two business days.
Request our security overview