Security at Omucloud.

Access to customer mail

Omucloud makes no claim that it is technically incapable of reading customer mail. A provider asserting such an incapacity should be asked to identify the cryptographic mechanism that produces it.

Administrative access

A small number of personnel hold administrative access to production systems, and that access is technically capable of reaching message content. It is restricted by internal policy to four purposes: investigating a delivery failure reported by the account holder, investigating suspected abuse, responding to a lawful order or direction, and restoring the service during an incident. Access for any other purpose is prohibited and is a disciplinary matter.

Customer mail is not read to construct user profiles, is not sold or disclosed for commercial purposes, and is not used to train machine-learning models. No automated analysis of mailbox content runs on the service. The single AI feature, Omu AI, is off by default and invoked per message by the account holder; it transmits the recording and the message being answered to the two providers named under Subprocessors, at that moment and at no other.

One automated process does examine account activity, and it examines how accounts send rather than what they write. Once a day it reads sending volumes, recipient counts, delivery outcomes, sign-up details and the shape of activity across accounts, and where an account passes a threshold it also reads that account’s subject lines, reduced to an eighty-character template with numbers removed. That material, for flagged accounts only, is sent to the provider named for abuse detection under Subprocessors so that it can be ranked for a person to review. Message bodies, attachments and the individual addresses of recipients are never part of it, and an account that passes no threshold is not included at all. Its purpose is to find spam, fraud and impersonation sent from this platform, and nothing found by it is used for any other purpose.

Administrative access to message content is not recorded in an audit log. There is accordingly no record against which such access could be reviewed after the event.

Parties with no access

Message content is not written to application logs. Omucloud incorporates no error-monitoring service, no tracking pixel and no advertising tag. The website uses Vercel Web Analytics to count page views in aggregate; message identifiers are stripped from those events before they are sent, and message content is not included. No third party therefore receives message content as a by-product of instrumentation.

Storage, retention and deletion

Data stored

Sent and received mail, comprising subject lines, full message bodies and attachments, together with the transmission details of each message: sender, recipients and time of delivery. Also stored: the account address, company name and signature where set, calendar entries, and the original sign-up record.

Deletion of an individual message

Supported. A message may be deleted from the message itself, in either direction of mail. Deletion moves the message to Trash rather than erasing it: the message is retained in full, body and attachments included, for 30 days, during which the account holder may restore it. A scheduled job then erases it permanently. Individual attachments may also be deleted from Settings, and the account may be deleted in full.

Two consequences follow, stated because neither is apparent from the operation. Storage occupied by a deleted message’s attachments continues to count against the account’s allowance until the message is erased. And a message delivered to more than one Omucloud account is removed from the deleting account only; it is retained by the other recipients, to whom it also belongs, and is erased only once the last of them has deleted it.

Deletion of an account

An account holder may delete their account from Settings without contacting us. The operation requires the account password and a typed confirmation, and removes received mail, sent mail, attachments, calendar entries and the account record.

Two consequences follow from deletion. A message delivered to more than one Omucloud account is removed from the deleting account only and is retained by the other recipients, to whom it also belongs. Where the account holds a custom domain, deletion removes every mailbox on that domain.

Backups

Deletion takes effect immediately in live systems. Backup snapshots are held by our database provider under its own retention schedule, and deleted data persists in those snapshots until they expire. No figure is published for that window: the schedule is the provider’s default and is not a commitment we are in a position to give.

Subprocessors

Operating a mail service requires third-party infrastructure. The following list is exhaustive as at the date of this statement.

Certification held by these providers, verified against their published trust documentation: Supabase is SOC 2 Type 2 compliant, ISO/IEC 27001 certified and HIPAA compliant. Resend is SOC 2 Type II compliant and commissions independent penetration testing. Those attestations cover the providers’ own platforms.

A signed data processing agreement is not currently offered. Where one is required for procurement, contact us and we will discuss what can be put in place.

Vulnerability disclosure

Suspected vulnerabilities should be reported to us before publication. Write to security@alano.ai with sufficient detail to reproduce the issue. We will acknowledge receipt, provide progress updates, and confirm when the issue is resolved.

We will not pursue legal action against a researcher who reports in good faith, does not access or alter data belonging to others, and allows a reasonable period for remediation before disclosure. No paid bounty programme is operated. Credit is given on request.

Reports of spam or misuse of the service should be sent to abuse@omucloud.co. Requests relating to personal data are dealt with under the Privacy Policy.

Controls not yet in place

Neither of the following is implemented.

Basis of this statement

Each control stated above has been verified against the source code operating the service. That verification is an internal review. It is not an independent audit, an attestation or a penetration test, and it is not presented as any of those. This statement is accurate as at the date shown at the head of the page and is amended when a control changes.