Subprocessors

This page lists third-party subprocessors that Mirentra uses to deliver the hosted platform, based on services verified in the current codebase and deployment configuration. The list is maintained at this URL and may change as infrastructure or service providers are added, replaced, or removed. Material changes will be reflected here and, where required by contract or law, communicated to customers in advance.

Google LLC (Firebase / Google Cloud Platform)

Legal entity: Google LLC (and affiliated Google Cloud / Firebase entities as applicable to the contracted services).

Purpose: Host and operate the Mirentra application — user authentication (Firebase Authentication, including email/password and Google sign-in); application database and workspace documents (Cloud Firestore); file evidence storage (Cloud Storage for Firebase); static application hosting (Firebase Hosting); and server-side Cloud Functions for transactional workflows (including email dispatch and related operational jobs where deployed).

Data categories: Account identifiers (for example email address and authentication identifiers); organisation and workspace content submitted by customers; file evidence uploaded by customers; application logs and operational metadata generated by the services; and related technical metadata required to deliver the platform.

Regions (verified for the current Mirentra Firebase project mirentra-7c061): Cloud Functions are deployed in us-central1 (United States). Cloud Firestore uses the nam5 multi-region location (United States). Firebase Authentication, Firebase Hosting, and Cloud Storage for Firebase for this project are operated by Google in the United States as part of the same Google Cloud / Firebase project footprint; contact ibrahimbandak@mirentra.com if you require a current Storage bucket location confirmation for a specific environment.

International transfers: Where personal data is transferred internationally, Mirentra relies on lawful transfer mechanisms described in our Privacy Notice, which may include adequacy decisions and the European Commission’s Standard Contractual Clauses (and UK Addendum where applicable) as offered by Google for Google Cloud / Firebase services.

Privacy information: Firebase privacy — https://firebase.google.com/support/privacy — and Google Cloud Privacy Notice — https://cloud.google.com/terms/cloud-privacy-notice

Resend, Inc.

Legal entity: Resend, Inc.

Purpose: Transactional email delivery from Cloud Functions when a Resend API key is configured (for example account verification, team invitations, and operational notifications).

Data categories: Recipient email address; message subject and body content required to deliver the email; and standard delivery and bounce metadata returned by the email service.

Region: Email is sent via Resend’s hosted infrastructure as described in Resend’s documentation and privacy materials. Processing location may include the United States and other regions used by Resend to deliver the service.

International transfers: Where required, Mirentra relies on lawful transfer mechanisms described in our Privacy Notice, including Standard Contractual Clauses or another recognized safeguard as applicable to the provider relationship.

Privacy information: Resend Privacy Policy — https://resend.com/legal/privacy-policy

List maintenance

This list includes only subprocessors verified in the Mirentra repository and deployment configuration at the time of publication. It does not include vendors that may be added in the future, customer-selected identity providers, or services not yet deployed. Before relying on this list for procurement or regulatory purposes, confirm the current version at /legal/subprocessors or contact ibrahimbandak@mirentra.com.