Your workspace holds your brand strategy, prompts, competitor data and connected-account credentials. We design aeoora so that data is protected in transit and at rest, kept separate between customers, and accessible only to the people you choose. This page explains our security controls and how to report a vulnerability. For privacy and data processing, see the Privacy Policy and GDPR and Data Processing.
Encryption
- In transit. All traffic to the app, API and MCP server uses TLS.
- At rest for secrets. Connector credentials (for example tokens for your CMS or analytics accounts) are encrypted before they are stored.
- Passwords. If you use a password, it is stored only as a one-way hash. You can also sign in with Google or GitHub, so we never see that password.
Workspace isolation
aeoora is multi-tenant. Every request is limited to the workspaces and brands that the signed-in person can access. This separation is enforced where the data is stored, not only in the app, which reduces the chance that a bug in one place exposes another customer’s data.
Access control
- Four roles: Admin, Manager, Analyst and Agency partner, with per-person brand access and menu access so people see only what they need.
- Short-lived access tokens (about 1 hour), httpOnly refresh cookies, and session records you can review and revoke.
- API keys and MCP connections are scoped, and read-only access is available. OAuth for MCP apps is revoked automatically if the app is unused for 30 days.
- Agents that can publish content act only within the connections and approvals you set, and you review what goes live.
- Access to production systems by our team is limited to what is necessary to operate and support the service.
AI providers and your data
To produce AI answers and drafts, we send the necessary content to AI providers (such as OpenAI, Anthropic, Google, Perplexity and xAI). We do not use your prompts or responses to train models, and we use provider terms that do not allow training on this data. The Privacy Policy describes the service providers we use.
Backups and availability
Data is backed up daily, and 14 daily backups are kept. Backups let us recover from failures or mistakes, and they roll off on that cycle. We do not currently publish an uptime commitment.
Application security
We limit how data from the internet (such as AI-bot logs and webhooks) is accepted: for example, AI-bot log lines older than 7 days are refused. Form submissions on the marketing site are protected against bots and spam.
Compliance
We support customers with GDPR obligations, including a Data Processing Addendum on request. We do not currently hold a SOC 2 or ISO 27001 certification.
Responsible disclosure
We welcome reports from security researchers. If you believe you have found a vulnerability in aeoora, please email security@aeoora.com. Please do not open public issues or post details before we have fixed the problem. You can write in English.
What to include
- What the issue is and what an attacker could do with it.
- Steps to reproduce it, or a proof of concept.
- The affected URL, endpoint or version.
- Anything you know about a fix or workaround.
What to expect
- We acknowledge your report within 3 business days.
- We give a first assessment (whether we can reproduce it and how severe it is) within 10 business days.
- We send updates at least every 2 weeks until it is resolved.
- Once fixed, we credit you publicly if you wish. Please keep details private until then. If a fix takes longer than 90 days, we will agree a disclosure date with you.
These are targets, not guarantees. aeoora is maintained by a small team.
Scope
In scope: aeoora Cloud at app.aeoora.com, including the web app, its API and MCP endpoint, store and CMS connectors, and the separation between workspaces. Out of scope: flaws in third-party services (report those to the vendor), denial of service or load testing, spam, social engineering or phishing of our staff or users, physical attacks, reports from automated scanners without a working proof of concept, and issues needing a compromised device.
Safe harbor
If you make a good-faith effort to follow this policy, we consider your research authorized. We will not take or support legal action against you, and we will work with you to fix the issue quickly. To stay within it, test only against accounts and data you own or have permission to use (a free trial works well), do not access, change or delete other people’s data (if you reach it by accident, stop, keep no copy and tell us), do not degrade the service for others, and give us reasonable time to fix the issue before you disclose it. If you are unsure whether something is allowed, ask us first in a private report.
Contact
Vulnerability reports: security@aeoora.com. Security questions from customers and procurement teams: support@aeoora.com. Last reviewed: November 13, 2026.