Every factual statement on this page traces to one of four sources: verified implementation (confirmed directly against the systems and code that run this business), documented company policy, legal commitments already in force, or operational practice explicitly confirmed by Revni's leadership.

Where something has not been independently verified by a third party, or where a certification is not currently held, this page says so plainly rather than implying otherwise. An absence stated honestly is more useful to a security reviewer than a confident-sounding gap.

Revni Digital's own corporate website is hosted separately from client delivery infrastructure, on ScalaHosting, in their Sofia, EU data centre. Client engagement infrastructure defaults to AWS and Cloudflare, consistent with the practices described on the Technology Stack page, and may also extend to Microsoft Azure, DigitalOcean, Vultr, Cloudways, or OVH depending on engagement requirements.

Infrastructure for client engagements is provisioned via Terraform where infrastructure-as-code is appropriate to the engagement. The corporate website itself is managed directly through ScalaHosting's control panel rather than infrastructure-as-code.

Development, staging, and production environments are logically and operationally separated by default, to reduce the risk of data leakage, cross-environment interference, and accidental production instability.

Data at rest is encrypted: client information stored in Zoho is encrypted using AES-256, with keys generated, rotated, and maintained through Zoho's own key management service. The corporate website's server files are restricted through strict file-permission settings, and ScalaHosting's SShield monitoring scans for and blocks malicious code and unauthorised data-injection attempts. Data in transit is encrypted site-wide using automatically renewing Let's Encrypt TLS certificates.

Backups for each data type are stored separately from the primary operational environment: client and project data in dedicated Google Cloud Storage buckets, customer information within Zoho's own geographically isolated data centres, and the corporate website through ScalaHosting's included backup provisions. Per ScalaHosting's own terms, backup availability is not contractually guaranteed, and Revni does not currently maintain a separate, independent backup of the corporate website outside of that included service. Client hosting and development projects deployed across partner cloud networks use each provider's native, automated backup protocols, stored separately from the active compute instances.

The CMS admin panel is protected by Payload CMS's built-in authentication (email and password, issuing a session cookie scoped to the admin panel only). There is no visitor login or account system anywhere on the public-facing site.

Multi-factor authentication is mandatory across business-critical systems, cloud infrastructure, code repositories, and core SaaS platforms, using time-based one-time passwords or authenticator push notifications. Password-only access to operational environments is not permitted.

Access to production environments, cloud infrastructure, and CMS platforms is restricted to a small number of authorized personnel — currently around 3 to 5 core team members — scoped by role under the principle of least privilege: administrative or root access limited to senior infrastructure engineers, developers granted scoped environment-specific access, and CMS users segmented into Administrator, Editor/Manager, and Contributor roles.

A formal offboarding protocol applies to any change in team member status: access to critical environments is revoked within 24 hours of departure, typically immediately, and role changes trigger an immediate update to access permissions. Access is reviewed periodically against the active team roster.

API keys, tokens, and production secrets are never hardcoded into source code or committed to repositories. Secrets are stored in cloud-native secrets managers or injected as encrypted environment variables, with access controlled by role, and keys are rotated on a regular schedule, after any personnel change affecting privileged access, and on demand following a suspected security anomaly.

The current state of cookies and tracking on this site is documented in full on the Cookie Policy page, and this page defers to that one as the source of truth for cookie-specific facts rather than restating them here.

Personal data is processed under a mapped legal basis per category: client engagement and onboarding data under performance of a contract, website contact and lead-form inquiries under legitimate interest, and project development and application data under a combination of contract performance and legitimate interest for security purposes.

Data is retained only as long as necessary for the purpose it was collected: client engagement and financial records for 7 years following the end of the relationship, reviewed and purged annually; active project development data and backups for 30 to 90 days post-contract; prospect web inquiries for 12 to 24 months if no engagement follows.

Personal data submitted through a contact form is used only to address that request, provide quotes, and support onboarding. Submitting a contact form does not opt a prospective client into marketing communications — those require separate, explicit opt-in. Data is not shared, rented, or sold to third-party data brokers or marketing networks.

During delivery and hosting engagements, Revni frequently acts as a data processor on behalf of clients who act as data controllers, under standard Data Processing Agreements or equivalent contract clauses. Client application environments are kept separate from Revni's internal operations, with access to environments containing client end-user data limited by role and mandatory multi-factor authentication.

Individuals whose data Revni holds can exercise rights of access, portability, rectification, erasure (subject to statutory retention requirements), and restriction of or objection to processing, by emailing privacy@revnidigital.com. Verified requests are fulfilled within one calendar month of receipt under UK GDPR, extendable by a further two months for complex requests, free of charge.

By default, data resides within a client's designated hosting region and production infrastructure does not migrate geographically. Because Revni's engineering team operates from a technical hub in Hyderabad, India, remote cross-border technical access does occur for maintenance and support, governed by Standard Contractual Clauses. Engineers do not download or store live production datasets locally; access is conducted over encrypted connections, protected by mandatory multi-factor authentication and role-based restriction.

Automated backups of production databases are taken at least daily, with hourly snapshotting or point-in-time recovery for high-transaction or mission-critical applications where required. Backups are retained on a rolling 30-day window, executed through native cloud tooling and managed hosting platforms.

Backups are encrypted both at rest (AES-256) and in transit (TLS 1.2+), with keys managed through cloud-native key management services. Custom retention windows beyond the standard 30 days can be provisioned at the infrastructure layer where a client requires it.

Backup restoration is tested systematically: full database and image-snapshot restoration is dry-run and verified before any environment moves to production, automated checksum routines continuously scan backup blocks for corruption, and mock restoration drills are run in isolated staging environments on a twice-yearly schedule and after any major architecture change.

Recovery Point and Recovery Time Objectives are established per engagement, based on the client's operational requirements and agreed service levels, rather than applied as a single fixed target across every project. Recovery procedures are reviewed periodically through restoration testing.

Infrastructure uptime is addressed by cloud service providers under their own standard uptime service-level agreements — separate from any uptime commitment Revni may agree directly with a client for a specific engagement. Revni layers its own application- and endpoint-monitoring on top of this, with automated alerting to the technical operations team when an endpoint becomes unresponsive or a resource threshold is breached.

Automated audit trails are enabled at the infrastructure, application, and CRM layers, tracking administrative actions with a standard retention window of 90 to 180 days: infrastructure audit logs for a rolling 180 days, server and application access logs for a minimum of 90 days before automatic purge.

Every code change must pass a formal review before merging or deployment to production: work happens on isolated staging or development branches, a second engineer or technical lead reviews and approves each pull request, and automated checks run before manual review is finalised.

Automated dependency scanning runs across all code repositories to continuously check for known vulnerabilities. Critical-severity alerts are tracked and remediated immediately, with updates validated in an isolated staging environment before moving through standard review and deployment.

The application has not yet undergone a formal third-party external penetration test. Internal controls in place ahead of one include mandatory peer-reviewed code changes on protected branches, automated repository vulnerability scanning, and isolated production environments with firewalls, least-privilege access, and mandatory multi-factor authentication.

An incident response protocol is documented and active: detection through continuous automated monitoring or internal escalation, containment and triage by isolating affected environments, revoking compromised credentials, or adjusting firewalls, and root-cause analysis through system logs. Where a verified data breach affecting client data occurs, formal notification follows to affected clients and relevant regulatory bodies within statutory timelines.

In the event of a confirmed or strongly suspected data breach involving client data, the incident is escalated internally to leadership immediately on detection, with technical containment and root-cause analysis beginning at once. Revni commits to notifying the ICO, or the relevant supervisory authority, without undue delay and, wherever feasible, within 72 hours of becoming aware of a qualifying breach, in line with UK GDPR. Affected clients are notified without undue delay, with the aim of doing so within that same window wherever practicable, with a written notice covering the nature of the breach, containment measures taken, a designated point of contact, and recommended client-side mitigations. A formal written root-cause analysis report follows within 7 to 14 business days of resolution.

To the best of Revni's knowledge, the company has not experienced a confirmed security incident involving unauthorized access to customer data since its inception. Infrastructure and application environments are monitored continuously to maintain that record.

Revni does not directly process, store, or transmit protected health information or raw cardholder data within its own internal systems. Payment processing uses tokenized third-party gateways such as Stripe, keeping cardholder data out of scope for Revni's core infrastructure. Where a client requires alignment with a framework such as PCI-DSS or HIPAA, Revni supports architectures capable of meeting those requirements, with compliance ultimately dependent on the client's own operational environment and contractual scope.

AI assistance is used within software engineering workflows under an internal Engineering & Data Handling Security Policy, confined to the engineering and architectural design phase. That policy prohibits the submission, uploading, or parsing of any real-world client data, production databases, or personally identifiable information into any third-party AI tool.

Engineers are restricted to an approved registry of development-assistance AI tools (including GitHub Copilot and Gemini), explicitly configured with enterprise privacy settings where data retention and model training are disabled. All AI-assisted code, configuration, and documentation is treated as an unverified draft requiring manual review and lead-engineer sign-off before it moves to staging or production.

Revni's engineering approach avoids proprietary frameworks, custom black-box hosting, or locked codebases, so that clients retain operational autonomy. Where commercially and technically appropriate, production environments are provisioned directly within client-owned cloud accounts, or structured for straightforward transfer of ownership, using industry-standard open-source codebases so a competent internal team or another agency can take over and maintain the application. Repository access, configuration scripts, API keys, and architectural documentation are accessible to the client throughout the engagement.

Where an engagement concludes, or responsibility transfers to another provider or an internal client team, Revni supports the handover through documentation, repository access, deployment information, and knowledge transfer, in accordance with the agreed contractual scope. Standard master service agreements include continuity clauses covering the transfer of deployment keys, master credentials, and knowledge-base assets to the client's designated technical lead.