Procurement

Ultimate security pack

Reviewable controls for Infosec. The signed DPA is still a discussion — unlock the live JSON pack in the org console with an Ultimate key.

We document real product controls and the principles behind them. This is not a claim of ISO, SOC 2, FedRAMP, or PCI certification. Ask for a vendor questionnaire, subprocessors list, DPA discussion, and attestation roadmap when your review process requires them.

What the pack contains

DPA discussion draft — roles, deletion, no sale of form data. Countersign via ultimate@ranasi.com.
Subprocessors — Paddle, Railway/Supabase, OpenAI (optional Server AI), Resend.
Data map — device profiles stay local; Org Vault stores templates; fill receipts store field UIDs not values.
Questionnaire answers — SSO/SCIM, retention (365 days), region pin (us/eu).
SOC 2 Type II roadmap — not certified. Ask for the current quarter’s status; we will not invent a date.

Data paths

Path	Leaves device?	What moves	Where
Local profiles	No	Forms, typed values, files, images, signatures, attachments, JSON	Endpoint only (browser / desktop storage you control)
License activate / validate	Yes · narrow	License key + instance id	Ranasi API over HTTPS (api.ranasi.com)
Server AI Auto-Fill (Pro+)	Yes · optional	Field metadata + non-card values for mapping. Card numbers stay on the device. CVC is never stored.	Ranasi API over HTTPS — Ranasi never receives the card
Your OpenAI key (optional)	Yes · your account	Same fill payload under your key & policies	OpenAI under your contract — optional BYOK
Form Test	Layouts optional	Filled answers stay in page DOM only	forms.ranasi.com — no answer archive
Org Vault (Ultimate)	Yes · templates you publish	Form structure, labels, types, hints, optional defaults — not live typed answers	Ranasi API (region pin us/eu)
Fill receipts (Ultimate)	Yes · no values	Actor, portal host, form id, field UIDs, mode, counts	Ranasi API, retained 365 days
Fill evidence (Ultimate Yearly)	Yes · no pixels / no values	Confidence, form version, screenshot SHA-256, counts	Ranasi API — screenshot files stay on the filling device
Audit export (Ultimate Yearly)	Yes · UIDs / hashes	Fill receipts and evidence metadata as SIEM JSON	Customer's SIEM — Ranasi is not the SIEM
Checkout	Payment only	Billing details for purchase — card number goes to Paddle only	Paddle as Merchant of Record. Ranasi never sees the number, never stores it, never charges it elsewhere.

Open org console · Security & trust · Support