Where Data Is Held

US regions, and who at Anty Virtual can reach what

The platform is hosted in the United States. Payments for Nigerian restaurants are processed in Nigeria. Nothing is held anywhere else by us; what our suppliers hold is on the sub-processor page.

Last updated 27 September 2026. Written to be read, not to be survived.

The regions

WhatWhereRead from
The database (every record), sign-in, file storageSupabase on AWS us-west-1, Northern California, United States. Backups in the same region.The project’s connection host and Supabase’s backup listing, 23 and 27 September 2026
The application (the pages, the dashboards, the jobs)Vercel, server functions in iad1 (Washington DC area), static assets on Vercel’s global edgeThe Vercel project’s function region, 27 September 2026
Voice calls, recordings and transcriptsRetell AI, United StatesRetell’s terms
Language model requestsAnthropic, United StatesAnthropic’s commercial terms
EmailResend, United StatesResend’s DPA
Payments and courier payouts (Anty Food)Monnify (Moniepoint), NigeriaMoniepoint’s privacy policy
WhatsApp and Instagram messagesMeta’s infrastructure, globalMeta’s platform terms

So: the data of a business in the United States stays in the United States. The data of a business in Nigeria, and of its customers, is held in the United States and processed for payment in Nigeria. The Nigeria Data Protection Act asks for a basis for that transfer; the basis is the business’s contract with us and the DPA, which says so in words.

Who at Anty Virtual can reach it

WhoCan reachHow it is bounded
The ownerEverything, including the database console, the hosting console and the supplier accountsOne person. The audit log records what they change. The Supabase account’s second factor is not yet switched on (open item on the Security page).
Staff with a capability (restaurants, couriers, rider operations)The console pages that capability covers, and nothing elseGranted by the owner on the People page, re-checked on every request, removed the moment it is withdrawn; a suspended person loses access on the next request.
Staff viewing as a clientThat one client’s dashboard, as the client sees itA signed, four-hour session bound to the staff member, written to the audit log; the client sees a banner on every page while it is on.
Field agentsThe prospects and restaurants in their own bookA partner account scoped to their own restaurants.
CouriersThe one order they have accepted: name, phone, address, until deliveredThe courier app shows nothing else.
SuppliersWhat their part needsEach under a data-processing agreement; the list is published.

How that access is controlled

  • Sign-in is by a code or link emailed to the person; there are no shared passwords.
  • The public browser key to the database can read nothing: every table is denied to anonymous and signed-in browser roles, and the server alone holds the key that can (confirmed live, September 2026).
  • A console session ends after a week without activity; a courier’s after a month.
  • Identity numbers, bank accounts and connection tokens are sealed under a master key held only by the running application, so a copy of the database on its own does not reveal them.
  • Every sign-in is logged with its address; every change to money, identity and settings is logged with who and when. Reads are not logged today.

Questions about access: security@antyvirtual.com.