Skip to content
Legal

Privacy Policy

How we collect, use, and protect your data. Plain-language summary first, formal text below.

Bought GloriaMundo through Microsoft Marketplace? Also read If you bought through Microsoft Marketplace at the end.

Last Updated: 16 November 2026

1. Plain-language summary

GloriaMundo is an AI workflow automation platform run by GloriaMundo Ltd, a small UK company. You describe automations in plain English; we turn them into workflows that connect to your existing tools (Gmail, Slack, Google Calendar, and hundreds of others).

To do this, we need some of your data. When you sign in with Google, we get your name, email, and profile picture. When you sign in with Microsoft, we get your name, your email address, and the IDs Microsoft uses for your account and its organisation. When you connect third-party services, your OAuth tokens are stored by Composio (a US-based service), not by us. When you type a message or upload a document, that content is sent to AI providers (Anthropic, Google, and others via OpenRouter) for processing, and in some cases to E2B for code execution. Your workflows are orchestrated through Inngest. We use PostHog for product analytics and Sentry for error tracking. All traffic passes through Cloudflare.

Most of these services are based in the United States. Our own infrastructure runs on Microsoft Azure in the UK (UK South), but data does leave the UK when it reaches our sub-processors. We rely on appropriate transfer safeguards where they are in place.

We keep your data while your account is active. You can delete individual workflows and projects yourself, and your whole account: from Settings, or at app.gloriamundo.com/account/delete, which shows what is deleted and what we must keep. We complete the deletion within 14 days, apart from a few records that need a separate step (section 7). If you can't sign in, email us and we will process it manually within 30 days. Some categories of expired data are not yet subject to automated cleanup. We retain billing records for 7 years to comply with HMRC requirements.

If you apply to our funded Tees Valley workflow programme, we keep the application and programme administration record through 31 March 2031 to meet programme delivery and audit requirements. You can withdraw optional contact permissions at any time.

You have rights under UK data protection law: access, correction, deletion, restriction, portability, objection, and the right to complain to the ICO. Email privacy@gloriamundo.com to exercise any of them.

We do not sell your data. We do not use it to train AI models.

This summary is not a legal substitute for the formal text below.

2. Who we are

GloriaMundo is operated by GloriaMundo Ltd, a company registered in England and Wales (Company Number: 16729892).

Registered office: 21 Deacon Gardens, Seaton Carew, Hartlepool, England, TS25 1UU

Data protection contact: privacy@gloriamundo.com

Controller role outside the Marketplace processing covered by Standard Contract 2.3

We are the data controller for the personal data described in this policy. Where we use third-party services to process data on our behalf (sub-processors), we remain responsible for how your data is handled.

3. What information we collect

3.1 Account information

When you sign in with Google, we receive your email address, name, and profile picture. We use these to identify your account and personalise the interface.

When you sign in with a Microsoft work, school, or personal account, we receive your name, your email address, and identifiers for your Microsoft account and the organisation (tenant) it belongs to. We keep your email address only when Microsoft confirms that it belongs to you. We do not receive a profile picture, and we do not store any Microsoft sign-in token. We use this information to identify your account and personalise the interface.

3.2 Billing information

When you purchase credits, Stripe (our payment processor) collects your billing address, payment card details, and tax identification if provided. We never see or store your full card number.

3.3 Content you provide

  • Conversations: messages you send and AI responses
  • Workflows: automation workflows you design and save
  • Uploaded files: documents (PDF, DOCX, TXT) and images you share for the AI to read
  • Soul and skills documents: custom instructions and context you configure for your agent

3.4 Third-party integration data

When you connect third-party services (Gmail, Slack, Google Calendar, and others) via OAuth, we store a reference linking your GloriaMundo account to the connection. The actual OAuth tokens are stored by Composio, a US-based third party that manages integrations on our behalf. Composio currently supports approximately 1,000 integrations. Your tokens remain in Composio's infrastructure until you disconnect the integration, at which point they are revoked.

3.5 Automatically collected data

  • Usage data: features used, models selected, workflow executions (collected via PostHog). PostHog also derives an approximate location (city and country) from your IP address.
  • Device information: browser type, operating system, screen resolution
  • Log data: IP addresses, access times, pages viewed (stored in our platform logs)

3.6 Memory system (optional)

If you enable the Memory feature, we store facts and preferences you share across conversations to personalise your experience. Memory is held in our Azure PostgreSQL service in the UK. It is opt-in and can be disabled at any time in your account settings.

3.7 Funded programme applications

If you apply to our Tees Valley workflow programme, we collect your business name, contact name and email address, location and Tees Valley connection, sector, business size, the task you want to improve, how you heard about the programme, and your versioned contact preferences. We also record the application's status and programme administration history, whether or not it is selected. Please do not put customer data, special-category data, credentials, or other confidential information in the application form.

4. Why we use your information and our lawful basis

Under UK GDPR, we need a lawful basis for each way we use your personal data. Here is how each purpose maps to a legal basis:

Purpose Lawful basis
Providing the service (processing AI requests, executing workflows, managing your account) Performance of contract (Art. 6(1)(b))
Processing payments and maintaining billing records Performance of contract (Art. 6(1)(b))
Product analytics and service improvement Legitimate interests (Art. 6(1)(f)): understanding how people use the service so we can improve it
Error tracking and debugging Legitimate interests (Art. 6(1)(f)): maintaining service reliability
Security and fraud prevention Legitimate interests (Art. 6(1)(f)): protecting users and the platform
Sending marketing and lifecycle emails Consent (Art. 6(1)(a))
Memory feature (storing preferences across conversations) Consent (Art. 6(1)(a))
Reviewing, administering, and delivering the funded Tees Valley workflow programme Taking steps at your request before entering an agreement and performance of an agreement (Art. 6(1)(b)); legitimate interests in administering and evaluating the programme (Art. 6(1)(f))
Contacting programme applicants and sending optional programme follow-up Consent (Art. 6(1)(a))
Maintaining programme application and delivery records through 31 March 2031 Legitimate interests (Art. 6(1)(f)): meeting programme administration, evaluation, and audit requirements
Retaining billing and transaction records Legal obligation (Art. 6(1)(c)): HMRC tax record-keeping requirements

5. Who we share your data with

We use third-party services (sub-processors) to help deliver GloriaMundo. For a complete list with purposes, data categories, processing locations, and links to each provider's privacy notice, see our Sub-processors page.

Below is a summary of the key data flows you should understand:

5.1 OAuth tokens for connected services

When you connect a third-party service (Gmail, Slack, Google Calendar, etc.), your OAuth tokens are stored by Composio, a US-based integration provider. We do not store OAuth tokens ourselves. Disconnecting an integration in GloriaMundo revokes the token at Composio.

5.2 Documents and file uploads

Documents you upload are stored in our private Microsoft Azure storage and indexed in our Azure PostgreSQL database for retrieval. To index them, PDFs and images that need text extraction are sent as files to Azure Document Intelligence (UK South), and the extracted text is sent to an Azure-hosted embedding model to make it searchable; that model runs on Azure resources in the United States on Global deployments, as described in section 5.4. We no longer use Graphlit, the US-based service that held documents uploaded before our move to Azure: it was retired on 31 October 2026, and the copies it held have been deleted.

5.3 Code execution

Code generated by workflows runs in sandboxed virtual machines operated by E2B, a US-based service. This code may process data fetched during earlier workflow steps.

5.4 AI providers

Your messages, conversation context, and workflow prompts are sent to language model providers for inference. We use Anthropic's API directly for certain calls, send some model requests and realtime voice conversations to Microsoft's Azure AI services (US-based resources on Azure's global deployments, so requests may be processed in any Azure region), route other requests through OpenRouter to models from Google, Anthropic, and other providers, and send searches of posts on X directly to xAI. We do not use your data to train AI models. The AI providers that process your requests have their own data terms, which vary by model and provider, and some may permit training on API inputs. Enterprise customers can contact us to ask for their processing to be restricted to providers that do not train on inputs.

5.5 Workflow orchestration

Workflow payloads are processed by Inngest, a US-based orchestration service. These payloads include user identifiers, step definitions, and step results, which may contain personal data fetched from your connected accounts (for example, email content or calendar events).

5.6 Analytics and error tracking

PostHog receives product analytics events, including user identifiers and feature usage data, and derives an approximate location (city and country) from your IP address. Sentry receives error reports, which may include stack traces, request metadata, and user identifiers. Both services are US-based.

5.7 Traffic and infrastructure

All HTTP traffic to GloriaMundo passes through Cloudflare for CDN delivery and DDoS protection. Cloudflare sees IP addresses, request URLs, and headers.

5.8 Email

Account, lifecycle and marketing emails are sent through Postmark (AC PM LLC, part of ActiveCampaign, in the United States). Our email contact list is kept in Loops, which can also send these emails as a standby. Transactional notifications (such as error alerts) may be sent through SendGrid (a Twilio subsidiary). Postmark and SendGrid receive recipient email addresses and message content. Loops receives the contact details and events listed on our Sub-processors page, and, when it sends as the standby, the content of each email.

5.9 Image generation

Image generation requests are sent through OpenRouter to the selected image model. Prompts may contain user-provided creative descriptions.

5.10 Web search and extraction

When your workflows include research steps, search queries and extraction requests may be sent to Serper, Tavily, Firecrawl, or BrightData depending on the task. Search queries may contain personal data from your workflow context. If you do not use research workflows, your data is not sent to these services.

5.11 Other disclosures

We do not sell your personal data. We may disclose your information if required by law, court order, or to protect the rights, property, or safety of GloriaMundo, our users, or others.

6. International transfers

Our primary infrastructure runs on Microsoft Azure in the United Kingdom (UK South). However, most of our sub-processors are based in the United States, and some data necessarily leaves the UK when it reaches them. BrightData is headquartered in Israel.

When personal data is transferred outside the UK, we rely on appropriate safeguards including UK International Data Transfer Agreements (UK IDTA), the UK Addendum to EU Standard Contractual Clauses, or adequacy decisions where applicable.

We are a small team and are working to ensure that formal transfer mechanisms are documented for every sub-processor. Where a specific mechanism is not yet fully documented, we assess the transfer risk and rely on the sub-processor's own data protection commitments and standard contractual terms. See our Sub-processors page for the processing location of each service.

7. How long we keep your data

We want to be honest about what happens to your data, including the gaps:

Data Retention Deletion mechanism
Account data (email, name, profile) While your account is active Delete your account in Settings or at app.gloriamundo.com/account/delete, and we complete it within 14 days (section 7 lists the few records that take longer); or email us to request erasure
Conversations and chat history Until you delete them No automated cleanup; individual deletion available in-app
Workflows Until you delete them Hard-deleted when you delete a workflow
Projects and uploaded documents Until you delete the project Project hard-deleted; its documents stay recoverable for 7 days, then are deleted from our storage (Azure may hold a recovery copy for up to 7 further days)
Connected service tokens (OAuth) Until you disconnect the integration Hard-deleted locally; token revoked at Composio
Memory facts (if enabled) While your account is active Deleted when you delete your account. Turning the feature off does not delete stored memories; email us to have them erased while you keep your account
Funded programme applications, consent records, status history, and delivery records Through 31 March 2031 Optional permissions can be withdrawn; the application and audit record is retained for programme administration, evaluation, and audit requirements
Billing and transaction records 7 years from the transaction date Retained to comply with HMRC requirements
Error tracking data (Sentry) Per Sentry's default retention (typically 90 days) Managed by Sentry
Analytics data (PostHog) Per PostHog's default retention settings Managed by PostHog
Application and platform logs Per our Azure platform retention settings Managed in Microsoft Azure
Expired session and workflow state data Indefinite (see note below) Cleanup functions exist but are not currently run on a schedule

A note on expired data: Some categories of expired data (such as abandoned session state and orphaned workflow records) are not currently subject to automated deletion and may persist until you request erasure or we run a manual cleanup. We are working to close this gap by connecting our existing cleanup functions to a scheduled process.

When you delete your account from Settings or at app.gloriamundo.com/account/delete, we complete the deletion within 14 days, apart from the records described below that need a separate step, and you can withdraw the request until the deletion starts. The deletion also asks Composio (your connected accounts), PostHog (analytics) and Loops (our email contact list) to delete what they hold for you. If you ask us by email instead, we will process your request within 30 days. We will confirm deletion by email once complete.

After your account is deleted, we keep these records, for these periods:

  • Our billing and payment records, without your name: 7 years, for tax law. Stripe, our payment processor, keeps its own records of your past payments and invoices, with the name and email they were made with.
  • Audit records of connected-app activity, without your name: 2 years.
  • A record that you asked for deletion and that it was done: 7 years.
  • A scrambled fingerprint of your sign-in, so a new account doesn't receive the free signup credit again: 2 years.
  • Your email address on our do-not-email list, if you unsubscribed, an email bounced or was reported as spam, or you asked us to stop. It stays there indefinitely, so we never email you again. Postmark, which sends our emails, keeps its own do-not-email list too.
  • Postmark's record of the emails we sent you, including the one confirming the deletion: 45 days.
  • If you applied to a funded programme: your application and its records, to 31 March 2031.

Deleted data leaves our backups within 7 days. Error reports and platform logs are kept as the table above describes. Some records are kept with no set end date, against an account number with no personal details. They include what you added to a shared take-off workspace, which stays with that workspace; Creator operation records, including the workflow data they captured; audit records; counts of adopted automations; records of changes to your soul documents and of migration assessments; and staff reviews of your library listings, which keep a copy of the listing.

If you used the Creator programme, imported a custom API or ran a migration assessment, a few of those records need a separate step, which has no set date yet. Until it is done we keep your account record, those records, and the automations they are tied to, and we email you when the deletion is complete.

8. Your rights and how to exercise them

Under UK data protection law, you have the following rights:

  • Right of access: you can ask us for a copy of the personal data we hold about you.
  • Right to rectification: you can ask us to correct inaccurate data.
  • Right to erasure: you can ask us to delete your personal data. We will do so unless we have a legal obligation to retain it (for example, billing records). You can delete your account yourself from Settings or at app.gloriamundo.com/account/delete, or email us.
  • Right to restrict processing: you can ask us to limit how we use your data while a concern is being resolved.
  • Right to data portability: you can ask us to provide your data in a structured, machine-readable format. We do not currently have a self-service export tool, so we process these requests manually.
  • Right to object: you can object to processing based on legitimate interests. We will stop unless we have compelling grounds that override your interests.
  • Right to withdraw consent: where we rely on consent (marketing emails, memory feature), you can withdraw it at any time. For marketing, use the unsubscribe link in any email. For memory, disable it in your account settings.

To exercise any of these rights, email privacy@gloriamundo.com. We will respond within 30 days. If your request is complex or we receive many requests at once, we may extend this by a further 60 days, but we will tell you within the first 30 days if that is the case.

Right to complain: if you believe your data protection rights have been violated, you have the right to lodge a complaint with the Information Commissioner's Office (ICO). You can do so at ico.org.uk/make-a-complaint or by calling 0303 123 1113.

9. Cookies and similar technologies

We use the following cookies and tracking technologies:

Technology Provider Purpose Can you disable it?
Session cookies GloriaMundo Authentication and CSRF protection No (essential for the service to work)
Website analytics, without cookies (our website's own pages, such as home, pricing and these policies) PostHog Counting page views and clicks on our website's own pages. They set no cookie and store no identifier on your device, so each page you open is counted on its own. Via ad-blockers or by turning off JavaScript
App analytics, without cookies (app.gloriamundo.com, and the public automation Library and publisher pages) PostHog Product analytics in the app: page views, feature usage, user identifiers. The public automation Library and publisher pages are part of the app, even when they appear under gloriamundo.com. The app sets no analytics cookie and stores no analytics identifier on your device. When you are signed in, page views are linked to your account; otherwise each page you open is counted on its own. Via ad-blockers or by turning off JavaScript
Referral cookie (gm_ref, app.gloriamundo.com) GloriaMundo Set only when you follow someone's referral link while signed out. It holds that referral code for up to 60 days, so we know who referred you if you sign up. Via browser settings
Performance and security cookies (__cf_bm, __cflb) Cloudflare Bot detection, load balancing, DDoS protection No (required by our CDN infrastructure)
Payment security cookies Stripe Fraud detection on checkout pages Only present on payment pages

Neither our website nor the app sets analytics cookies or stores an analytics identifier on your device, so there is no cookie banner. The public automation Library and publisher pages are part of the app and use the app's analytics, as the table shows. You can manage cookies and local storage through your browser settings.

10. Security

Here is what we do to protect your data:

  • Encryption in transit: all connections use TLS.
  • Encryption at rest: sensitive credentials in our vault are encrypted with AES-256-GCM, with keys derived via HKDF-SHA256.
  • Authentication: OAuth 2.0 and OpenID Connect via Google Sign-In or Microsoft sign-in, with secure session management.
  • Infrastructure: hosted on Microsoft Azure managed services (Container Apps, managed PostgreSQL, and Redis) in the UK South region.
  • Code sandboxing: workflow code execution runs in isolated E2B virtual machines, separate from our main infrastructure.
  • Input sanitisation: we redact secrets from workflow payloads before they reach orchestration services, and we redact PII patterns from error reports.

No system is perfectly secure. If you discover a security vulnerability, please report it to privacy@gloriamundo.com.

11. Children

GloriaMundo is not intended for anyone under 18 years of age. We do not knowingly collect personal data from anyone under 18. If we learn that we have collected data from someone under 18, we will delete it. If you believe a child has provided us with personal data, please contact us at privacy@gloriamundo.com.

12. Changes to this policy

We may update this policy from time to time. For material changes, we will give at least 30 days' notice by email or through the service before the changes take effect. Your continued use of GloriaMundo after the effective date constitutes acceptance of the updated policy. We will always keep the current version available at this URL.

13. Contact

If you have questions about this policy or want to exercise your data protection rights:

Email: privacy@gloriamundo.com

Post:
Data Protection Contact
GloriaMundo Ltd
21 Deacon Gardens
Seaton Carew
Hartlepool, England
TS25 1UU

If you bought through Microsoft Marketplace

Microsoft Marketplace privacy scope and contractual roles

For Marketplace purchases and setup, Microsoft identity and commerce services support authentication and subscription management. GloriaMundo processes account/subscription associations and workflow, execution and usage records needed to supply the Offering. Marketplace inference uses configured customer-owned Azure resources; optional native X search uses the customer's connected xAI account. General descriptions of Stripe checkout and publisher-routed AI services should not be read as describing the Marketplace purchase and inference path.

For processing covered by Standard Contract 2.3, the contract provides that you are controller and GloriaMundo is processor, except where you act as processor, in which case GloriaMundo is subprocessor, or applicable Offering-specific terms state otherwise. GloriaMundo processes that covered data on your documented instructions. Other purposes and individual providers' roles must be described according to applicable agreements and actual processing.

Where Standard Contract 2.3(d) applies, GloriaMundo remains responsible for its subprocessors' compliance and gives at least 14 days' notice before a new subprocessor accesses Personal Data. The specified right to terminate the affected subscription without penalty applies if the customer does not approve the change and gives the required notice and explanation within that period.