Trust

How Veritory protects your data

Veritory records verified field activity for pharmaceutical and FMCG sales teams: customer visits, GPS location during the working day, orders and photos. This page states what we commit to for that data, who processes it, and what is in place today versus what lands before our first production tenant. Procurement and legal teams can request the signed versions of these commitments from their account manager.

Version
1.0
Last updated
20 October 2026
Operator
Purs & Gold
In placeBefore first production tenantPlanned

Who operates Veritory

Operator

Veritory is operated by Purs & Gold, a Nigerian company. Veritory is the product and trading name. Contracts, DPAs and sub-processor agreements are signed by Purs & Gold.

In place
Role under NDPA 2023

For all tenant data (customers, HCPs, reps, orders, visits, location) the tenant is the data controller and Purs & Gold is the data processor, acting only on the tenant's documented instructions.

In place
Data Processing Agreement

A DPA aligned with the Nigeria Data Protection Act 2023 and the NDPC's GAID 2025 is part of every subscription agreement and is available on request before signature.

Before first production tenant
Security contact

A monitored security and privacy mailbox on the production domain, published here once the domain is live. Until then, the account manager named in your pilot charter.

Before first production tenant

Tenant isolation and access

Isolation

Every tenant-owned table is protected by Postgres Row Level Security keyed on the organisation. 247 policies across 100 tables; the isolation test suite runs in CI on every change and a failure blocks the release.

In place
Dedicated tier

Enterprise tenants can run on a dedicated database and application environment provisioned from the same migrations, with data residency per region as an option.

Planned · Stage 2
Authentication

Email and password with mandatory TOTP multi-factor authentication for Admin, Manager and Finance roles. SSO (SAML/OIDC) is an Enterprise add-on planned for Stage 3.

In place
Authorisation

Role templates built from a catalogue of 69 permissions; each user's data scope (own, team, region or organisation) is enforced in the database, not only in the apps.

In place
Audit trail

Approvals, flag reviews, order changes and privileged actions are written to append-only tables; the database itself rejects updates and deletes on them.

In place
Vendor access

Purs & Gold support staff have no standing access to tenant data. Access is granted per case, time-boxed, with a recorded justification, and appears in your audit log.

Before first production tenant
Rep devices

Reps use their own phones; one active device per rep, revocable by your admin. The app stores only the rep's own working set, encrypted at rest by the operating system.

In place

Encryption and data handling

In transit

TLS 1.2 or higher on every connection between the apps, the API and sub-processors. No plaintext endpoints.

In place
At rest

Database, backups and object storage are encrypted at rest with AES-256 by the hosting providers (Supabase on AWS, Cloudinary).

In place
Photos

Proof-of-visit and receipt photos are hashed (SHA-256) on the device and uploaded only through signed requests. The hash is kept so tampering is detectable.

In place
Secrets

API keys and service credentials live in the hosting providers' secret stores, never in source code or on devices.

In place
Data minimisation

The rep app collects location only inside an open daily session. It does not read contact lists, call logs or other phone data.

In place

Backups, continuity and performance

Backups

Daily backups plus Point-in-Time Recovery on every production database.

Before first production tenant
Recovery objectives

Recovery point objective 15 minutes or better; recovery time objective 4 hours or better.

Before first production tenant
Restore drills

A full restore drill before go-live and every 6 months thereafter. The last drill date is published on this page.

Before first production tenant
Availability

99.9 % monthly availability for Command and the sync API, measured by external probes, with a public status page.

Before first production tenant
Offline operation

The rep app keeps working without connectivity. Captured visits and orders are queued and sync in order when a connection returns.

In place

Vulnerability management and testing

Automated checks

Dependency and static analysis on every change in CI; the isolation test suite is part of the same gate.

In place
Penetration testing

An independent third-party penetration test of Command, the rep app and the API at least annually, the first before the first production tenant. A summary letter is available to tenants under NDA.

Before first production tenant
Remediation targets

Critical findings fixed or mitigated within 7 days, high within 30 days, medium within 90 days.

Before first production tenant
Responsible disclosure

Researchers can report issues to the security contact. We acknowledge within 3 business days and do not pursue good-faith research.

Before first production tenant

Incidents and breach notification

Monitoring

Error and crash reporting on both apps, database log drains and uptime probes alert an on-call engineer.

Before first production tenant
Tenant notification

Affected tenants are notified without undue delay and no later than 72 hours after a personal-data breach is confirmed: what happened, which data and people are affected, the actions taken and the actions we recommend.

Before first production tenant
Regulator notification

Where NDPA 2023 requires it, the NDPC is notified within 72 hours. As controller, you receive the information you need for your own notifications to data subjects.

Before first production tenant
Post-incident report

A written root-cause report within 10 business days of closure.

Before first production tenant

Retention and deletion

Tenants can shorten any retention period. Periods are never lengthened without a documented legal basis from the tenant.

DataDefault retentionStatus
Raw location pings90 days, then deletedIn place
1-minute location roll-ups12 monthsIn place
Daily route summaries, visits, orders, audit logLife of the contractIn place
Veritory IQ query logs90 daysPlanned
Error reports90 daysBefore first production tenant
After contract endExport on request, then deletion from production within 30 days and from backups within the rotation period (35 days or less)Before first production tenant

Rep location tracking

These rules are shown to every rep in the app before tracking starts. They are public because reps, their managers and their unions read them.

  • Location is collected only between clock-in and clock-out of a daily session. A persistent indicator shows when tracking is on, and clock-out is always available.
  • Each rep records a versioned, explicit consent in the app at first use and again whenever the policy text changes.
  • Supervisors see live positions of their own team only. Location history exports are an admin action and are audited.
  • If the phone reports a mock location, the rep is told in the app rather than silently flagged.
  • Retention follows the table above and cannot be extended by the tenant without a documented basis.

Sub-processors

Tenants are told of additions or replacements at least 30 days before they take effect and may object in writing. Data shared with each sub-processor is limited to what the listed purpose needs.

Sub-processorPurposeDataLocationStatus
Supabase (on AWS)Database, authentication, realtime, file metadataAll tenant dataAWS eu-west-2 (London); other regions on the Enterprise dedicated tierIn place
VercelHosting of Veritory CommandRequest data in transit; no tenant data at restGlobal edge; server functions in LondonIn place
CloudinaryStorage and delivery of proof-of-visit and receipt photosPhotos with GPS and timestamp EXIFEUIn place
MapboxMap tiles and renderingMap viewport requests; no customer recordsGlobal CDNPlanned · Stage 1 maps
Google Maps PlatformGeocoding of customer addresses during importCustomer addressesGlobalPlanned · Stage 1 maps
SentryCrash and error reportingDevice and app diagnostics; personal data scrubbed before sendingEUBefore first production tenant
GitHubSource code and CINo tenant dataUSIn place
AnthropicVeritory IQ natural-language queriesOnly the tenant-scoped records needed to answer a question; no training on tenant dataUSPlanned · Stage 2
SMS / WhatsApp provider (to be named)NotificationsPhone numbers and message textNigeria / globalPlanned · Stage 2

Certifications

Purs & Gold does not hold ISO 27001 or SOC 2 today and does not claim to. A SOC 2 Type I readiness assessment is on the Stage 3 backlog and will be announced here when scheduled. The hosting providers' own reports (AWS, Supabase, Vercel, Cloudinary) are available from those providers.