Merome legal information
Subprocessors
Providers are listed according to actual processing and activation state. Provider operations may occur outside Australia even when primary Merome infrastructure is in Sydney.
| Provider | Purpose / activation | Information | Location / controls |
|---|---|---|---|
| Google Cloud / applicable Google contracting entity | Hosting, Cloud SQL PostgreSQL, private objects, Identity Platform, secrets/KMS, logs/monitoring/security | Service, account, content and operational information necessary for those functions | Primary Merome infrastructure: Sydney, Australia; Google provider processing may be international |
| OpenRouter | AI inference gateway; production customer processing pending privacy/credential verification | Only content/metrics needed for requested analysis | International; production requires dedicated credentials, approved providers, collection-deny and supported ZDR controls, without unapproved routing fallback |
| Anthropic | Model inference through approved OpenRouter route; production activation pending | Necessary content/analytical inputs | International; exact approved route and retention controls must be verified before customer processing |
| Porkbun | Incoming support, privacy, legal and security mail forwarding | Sender/contact details and correspondence sent to the published contact addresses | Provider infrastructure may process outside Australia; no analytics, OAuth credentials or app database access |
| Google Gmail | Merome admin/support inbox receiving contact forwards | Contact correspondence and associated email metadata | International Google mail infrastructure; separate from primary Sydney application storage |
Stripe is planned for payment processing and subscription administration. It is not currently an active payment recipient: paid checkout is disabled. When activated it will receive billing identity, payment and subscription information; full card details will be handled by Stripe, not Merome.
1. Meta and Instagram
Meta and Instagram are connected third-party platforms from which Merome receives authorised account information at the user's request. Meta operates independently under its own terms/privacy, not as an ordinary Merome infrastructure subprocessor.
2. Transcription
Whisper executes inside Merome's Google Cloud jobs, not through an OpenAI-hosted API. OpenAI is not listed merely because its open-source model is used; it does not receive customer audio through this implementation.
3. Email
Google Identity Platform supplies authentication emails. The published support, privacy, legal and security addresses are configured with Porkbun forwarding to Merome's Google Gmail admin inbox; these providers receive contact correspondence. Stripe will supply billing messages when billing is enabled. No separate audit-completion or marketing email provider is currently integrated.
PO Box 263, Pyrmont NSW 2009, Australia
support@merome.io · privacy@merome.io · legal@merome.io · security@merome.io