Transparency

Data & Security

A pharmacy is being asked to put its drug register, its GST records and its patients' names into a tool it has never audited. This page is the technical answer to "why should I trust you", written to be checked rather than admired.

Effective 27 September 2026

At a glance

QuestionAnswer
Where does my data live?Cloudflare: database, file storage and application code, behind HTTPS
Who can see my patient records?Your signed-in team, within their role. Our administration view has no route to invoice line items or your customer register
Are passwords readable?No. One-way PBKDF2-SHA256, 100,000 iterations, unique salt per account
Do you store card details?No. Checkout is hosted by Razorpay. Card data never reaches an Anvip server
Do you run analytics or ad trackers?No. No tracking scripts, no advertising cookies, no third-party font loader
Is my data used to train anything?No. Nothing of yours trains a model, and no workspace record - invoice, customer, stock or supplier - is sent to an AI service that writes anything for you. The one opt-in exception is Scan bill, where the bill photograph you upload is read by LlamaCloud's document parser and nothing else in your workspace is ever visible to it; it holds files for at most 48 hours, states it never uses data for training, and keeps no copy here. See the full list
Backups?Automated daily snapshots of the business tables, on the same platform
Certifications?None claimed. See what we do not promise

Infrastructure

The site is served from Cloudflare Pages, the API is a Hono application running on Cloudflare Workers, and data sits in Cloudflare D1 with files in Cloudflare R2. Requests reach the API through a same-origin proxy that deliberately strips forwarding, authorisation and geo metadata headers before the Worker sees them, so the application is not passed visitor location or raw auth context.

  • All traffic is HTTPS; TLS is terminated and managed by Cloudflare
  • The browser bundle ships without source maps
  • Storage regions are selected by Cloudflare and are not pinned to a named country by us. If a contract requires India-only residency, ask us at [email protected] before relying on it
  • Production builds are deployed from a private repository through a single CI job

Store isolation

This is the control that matters most, because a shared pharmacy database is exactly what a patient would fear. Every read and write in the API is scoped by your store identifier. There is no query path that returns another store's invoices, buyers, stock or suppliers to you, and none that aggregates your patient records into a cross-store dataset.

  • A person who buys at two Anvip pharmacies exists as two unrelated rows. We do not link them
  • Access is granted by role: owner, manager, biller, viewer. A store has one owner
  • Bulk exports and the customer register additionally require full workspace mode and an owner or manager role. Stock-only stores hold no customer records at all
  • Team member accounts are created by the owner, who sets the initial password - a deliberate design with a real consequence, so read the note on it in Terms

Accounts, sessions and passwords

ControlHow it is implemented
Password storagePBKDF2-SHA256, 100,000 iterations, a 16-byte random salt per account, constant-time comparison. Recovering a password from the hash is not practical
Password policy12 to 128 characters, enforced on both signup and change
SessionA signed JWT held in an HttpOnly, Secure, SameSite=Lax cookie, valid for 30 days. The browser never reads it and the app cannot be tricked into handing it out
Session revocationA counter embedded in every token is compared against the live account row on each request. Changing a password, or an approved email change, signs out every device immediately
Cross-site request protectionA CSRF token paired with a Host-anchored cookie, required on sign-in and on state-changing forms
Redirect protectionPost-login destinations are allowlisted to known workspace paths, so a crafted "return to" link cannot send you to an outside site
Login bot defenceA Cloudflare Turnstile challenge is verified on our server before credentials are even looked up, so a password-guessing script pays a bot-check cost first
Failed sign-in limitsEight wrong passwords inside 15 minutes lock that account for an hour. Five wrong two-factor codes lock the second factor for 30 minutes. One device trying many accounts is capped at 25 attempts an hour. The counters live in the database, not the browser, and a successful sign-in clears them
Email privacyPlatform administration is limited to an allowlisted address plus an explicit account flag, and signing up with that reserved address is refused indistinguishably

Two-factor authentication

Time-based one-time passwords are available to every account type, and we recommend them for owners.

  • Six digits, 30-second validity, one step of clock tolerance, standard RFC 6238 - so any authenticator app works
  • The setup QR code is drawn by the app itself on your device; no external QR service sees your secret
  • Ten single-use recovery codes, stored hashed, each consumed once and marked used
  • Turning two-factor off requires your password and a current code, so a stolen password alone is not enough to strip your protection
  • It is optional today, not enforced. Enabling it is a Settings change that takes about a minute - please do it. Recovering a forgotten password switches two-factor off with it, because an authenticator bound to a password you no longer know would lock you out of the account you just recovered - so keep your recovery codes as the paper records you would not throw away

Payments

Money moves through Razorpay's hosted checkout, which keeps card and UPI interaction off our servers. Billing is an auto-renewing mandate held by Razorpay; our side of the design is about making a charge impossible to fake or reuse.

  • The price is resolved from our own plan record on the server. A browser cannot ask for a different amount
  • An authorisation left half-finished is not a subscription: it charges nothing, grants nothing, and is not treated as auto-renew being on
  • Before access changes hands we re-read the subscription and the payment from Razorpay and require the payment to belong to that subscription and be captured - the browser callback is never trusted for either fact
  • The webhook is authenticated with an HMAC signature and runs the same re-read, so a forged callback cannot create access
  • Each captured charge can be granted once, because its payment id is recorded; a replayed webhook or callback cannot buy a second period
  • A mandate you cancel in Settings ends at the period already paid for, and the token that would debit you stays with Razorpay and your bank - see the Subscription Terms
  • Stored payment data is limited to identifiers, amount and dates. No card number, no expiry, no CVV - see the Privacy Policy

Uploads and stored files

Two kinds of file can reach Anvip, and only one of them is kept. The store logo is stored: up to 300 KB, with its type decided by inspecting the file's magic bytes rather than trusting what the browser claimed, so an HTML or script payload cannot be dressed up as an image. Replacing or removing a logo deletes the old object, and logo responses carry a nosniff header. A scanned supplier bill is forwarded to the reader and never stored - described below.

The only document a store can send us is a supplier bill for Scan bill, and it is not retained here: the file is forwarded to the reader, and what stays in our database is a checksum, the file type and the line count. So no bill photograph sits in our storage, and no prescription image exists in it either - though the scan box will take any image you point at it, which makes that discipline yours, not ours.

Exports and printing

  • Accounting export is restricted to owner and manager roles and to a bounded date window, 366 days at most; the full set of ceilings is tabulated in Terms
  • Downloaded files are served with a no-store cache directive so they do not linger in a shared browser
  • Every exported cell is guarded against spreadsheet formula injection: text starting with = + - or @ is neutralised, so a medicine name or buyer name cannot execute inside Excel
  • The partner dashboard shows up to 100 of your own referral records, and nothing belonging to another partner
  • Invoices reach your customers as a printed bill or a PDF you save from the browser. Anvip never emails your customers; the messages we do send go to you - one-time account-recovery codes - and renewal notices for an auto-renewing subscription come from our payment provider

Backups and recovery

A scheduled job takes a JSON snapshot of the business tables every day - stock, batches, purchase and sales invoices, line items, buyers, suppliers, subscriptions, payments, commission ledger and store profiles - and writes them to private object storage, keeping a dated copy and a latest copy. Losing the database is therefore a recovery exercise rather than a catastrophe.

  • Snapshots are not public and are not served to browsers
  • Per-table failures are isolated, so one bad table cannot abort the run
  • Restoration is a manual, operator-run procedure today. There is no automated failover, no point-in-time replay, and no tested disaster-recovery clock
  • Snapshots age out only when we act on them. That is why an erasure request under the Privacy Policy explicitly includes clearing backup copies, not just the live row
  • Your own discipline is part of the plan: take the accounting export periodically and keep it. Do not let us be the only copy of your statutory records

Logging

Stated completely, because a security page that hides its logging is not a trustworthy one.

  • The API records a request line for each call: method, path, status and duration. Because some search boxes use query strings, text typed into a search - a buyer name, for example - can appear in that log entry
  • Request bodies, cookies, authorisation headers and IP addresses are not written to application logs
  • The application does not capture visitor IP addresses or user-agent strings at all. Referral visits are anonymous counters
  • Platform-level telemetry held by Cloudflare, Razorpay and the bill-scan reader is governed by their settings and their own policies
  • There is no third-party analytics, error-reporting or session-replay service in the product
  • There is no separate audit trail of administrative reads yet; staff activity is limited by design rather than monitored

Who at Anvip can see what

Administration is one allowlisted account. It can see store identity, address, contact fields, drug licence number, GSTIN, owner name and email, invoice counts, total billed value, subscription dates, payment identifiers, partner records including UPI IDs, and the free-text notes on demo and email-change requests. It can suspend a store and can grant time-limited access, each grant recorded with a written reason.

It cannot, through any route in the product, list a store's invoice line items, open the customer register, read dosage instructions, or export patient data. Aggregates are counts and totals, not records.

What we do not promise

We would rather you learn this here than discover it later.

  • No SOC 2, ISO 27001, PCI-DSS or any other third-party attestation. Card data is outsourced to Razorpay, but we make no compliance claim about Anvip itself
  • No uptime guarantee, no service credits, no contractual recovery time
  • No published penetration-test or vulnerability-scan report, and no bug-bounty programme
  • A lockout is silent: we do not email you when repeated failures lock an account, and there is no sign-in history or device list to inspect
  • No field-level encryption of database columns beyond the platform's own storage protection, and no key-management separation from the database
  • No self-service account closure, data-deletion request or full data export inside the app; those go through email and are handled by hand
  • No signed data-processing agreement, custom contract, on-premise deployment or security questionnaire response
  • No email or SMS verification of an address at signup, which means an account email is claimed, not proven - keep your address private and never share a login
  • A forgotten password is recovered with a code emailed to the address on the account, so for a recovered account your mailbox is the credential that matters most - whoever controls it can set a new password

If any of these are hard requirements for you, the honest answer today is that we do not offer them at all, and those controls belong with enterprise vendors. We will tell you the same thing before you pay as after.

Protecting your pharmacy

Most real-world compromises of a counter system come from the counter, not the software. A short checklist:

  • Turn on two-factor for the owner account the day you set up, and save the recovery codes somewhere physical
  • Use a password nobody else has, and never the store's public phone number or licence number
  • Give staff the lowest role that lets them work. A biller does not need manager
  • Remove a departing team member immediately - deleting the membership signs their session out
  • Do not share your login with a consultant, an accountant, or a software representative, and never let a partner register on your behalf
  • Record a buyer name only when you need it; the default walk-in entry exists for a reason
  • Lock the counter device, and do not save the workspace password in a shared browser
  • Take a periodic accounting export, and keep printed or PDF bills as your own statutory copies
  • Check the printed invoice against the pack before handing it over: medicine, batch, expiry, dose, schedule

Reporting a problem, and how we handle one

If you find a weakness, or believe an account is compromised, write to [email protected]. Please report in good faith: prove a point without exfiltrating patient data, and give us a chance to fix it before telling anyone. We aim to acknowledge within 2 working days, and we will credit a reporter who wants it.

If we become aware of a breach that affects your workspace, we will contact affected account holders by email without undue delay, say what was exposed, describe what we have done, and tell you what you should do next - including where we cannot say more. We will not dress up an incident, and we will not pretend a notification happened that we did not send.

Contact

Security questions, requests for our handling of a specific control, or a written statement of how data is processed for your records: [email protected]. See also the Privacy Policy for what we collect and how long we keep it.

Questions about this document

We would rather explain a clause than have you guess at it. If you are about to pay, or already pay, and something on this page is ambiguous, email us and we will answer plainly - and correct the page if it is badly written.