Local-first profiles for vendor, KYC, and internal intake workflows. Card fields stay off Server AI. Endpoint DLP / MDM still applies. Evaluate cloud AI deliberately — or keep fill on-device.
Trust center · worldwide
Built so banks, governments, and leading orgs can say yes
Global institutions evaluate autofill on one question: where does our data go? Ranasi is local-first by design. Cloud is optional, narrow, and documented — so Infosec, privacy, and procurement can approve Ranasi as a primary workflow tool with confidence.
Why institutions buy
Confidence to pay. Confidence to standardize.
Ranasi is sold as a paid platform — not a free consumer toy — so security and legal teams can treat it like other enterprise software: clear plans, clear data paths, and a reviewable control story.
- Primary workflow tool — customize once, Auto-Fill across Chrome, Edge, Firefox, Android Firefox, and desktop
- Endpoint control remains yours — forms and uploads stay on the device; MDM / DLP still apply
- Cloud is a choice — local fill, Ranasi Server AI, or your own OpenAI key
- Procurement path — vendor questionnaire, subprocessors, DPA discussion, and attestation roadmap on request
Product controls
What protects your data in practice
Concrete behaviors reviewers can verify — not slogans.
- Device-held profilesForms, typed values, uploads, and signatures live in storage on the endpoint you manage — not a shared customer data lake Ranasi can browse.
- Least data to the cloudLicense checks and optional Server AI only. Payment card fields are stripped from server fill. Basic can stay fully local.
- Explicit AI scopeTurn Server AI off by staying on local fill, or use your own OpenAI key so the request runs under your account and policies.
- Form Test without retentionPractice Auto-Fill on forms.ranasi.com. Layouts may be optional; filled values are never saved as an answer archive on that site.
- Encrypted in transitLicense and Server AI calls use HTTPS. Checkout is handled by our payment provider under their PCI-aligned processes.
- Reviewable & accountablePublished Security page, Privacy Policy, and Terms. Vendor questionnaires, subprocessors, and DPA discussions available on request.
Data paths
Every path. Explicitly scoped.
Show this table to Infosec. If a path is not required by policy, leave it unused — Basic and local fill never need Server AI.
| 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 | Ranasi API over HTTPS; card fields stripped |
| 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 |
| Checkout | Payment only | Billing details for purchase | Paddle as Merchant of Record (PCI-aligned) |
International framing
Principles security programs already use
Language Infosec and privacy teams recognize worldwide — so Ranasi fits existing control libraries without pretending to hold certificates we have not published.
- ISO/IEC 27001 principlesConfidentiality, integrity, and availability: minimize what leaves the device, protect API traffic, and keep clear purpose limits on processing — without claiming ISO certification.
- Privacy by designLocal storage by default. Optional cloud features are explicit. Form Test defaults to not remembering filled answers on the site.
- Data minimization & purpose limitServer fill sends only what mapping needs. No permanent warehouse of customer form profiles on Ranasi servers.
- NIST-minded control thinkingIdentify what data exists on the endpoint, protect transit, detect narrow cloud use, and respond via clear policies and contacts — mapped to how Infosec teams already reason, not a NIST certification claim.
- GDPR-minded handlingDevice-held profiles support data minimization. License and optional AI processing are purpose-limited. Contact us for deletion / DPA discussions when required — not a claim of formal GDPR certification.
- AccountabilityPublic Security, Privacy, and Terms. Honest non-certification disclaimer. Procurement-ready questionnaire support for global buyers.
Who this is for
Banks · governments · leading organizations
One product story, three institutional contexts — same local-first controls.
Designed for controlled endpoints: forms and uploads remain on the device by default. Optional Server AI is narrow and documented so policy teams can approve or decline cloud assist without ambiguity.
One license unlocks browsers and desktop. Enterprise / Ultimate add generate, uploads, and Form Test for org-scale intake — with a security review path built for global procurement.
Evaluate quickly
A review path Infosec can finish
- Confirm device storageForms, uploads, and signatures stay on the endpoint. Apply your existing extension / desktop MDM and DLP policies.
- Decide AI scopeAllow Ranasi Server AI, require BYOK OpenAI, or keep fill local. Card fields are stripped from Server AI either way.
- Test without retention riskUse Form Test on forms.ranasi.com knowing filled answers are not archived there.
- Request the vendor packEmail bnatharuch@gmail.com for questionnaire support, subprocessors, DPA discussion, and attestation roadmap.
- Purchase and standardizeChoose Enterprise or Ultimate when org-scale generate, uploads, and Form Test are required — then activate with your license key.
Procurement
Vendor questionnaire & security pack
Global banks, governments, and leading organizations can request a written response pack: architecture summary, data-flow paths, subprocessors, DPA discussion, and attestation roadmap — without marketing fluff.