Privacy policy

Meetext is used by software vendors. Those vendors have their own customers, and Meetext installs the vendor's product into those customers' workspaces. Where a vendor decides what is collected and why, the vendor is the controller and Meetext is a processor acting on their instructions. For our own account and billing records, Meetext is the controller.

• Account: name, email address and the sign-in provider used.
• Organization: name, plan and billing identifiers.
• Operational records for each customer deployment: state, version, timestamps, validation results, incidents and the actions taken.
• Provider error codes such as AADSTS90094, and structured facts derived from them.

Capability results pass through memory and are not written to our database. Capability arguments are audited by name only, never by value, so an argument called query is recorded and what was searched for is not.

Raw provider messages are not kept. Provider prose is logged with short retention for debugging and does not enter the operational record, which holds normalized codes instead.

OAuth grants and API tokens live in a dedicated secret manager under a name scoped to a single customer environment, never in the primary database and never shared between two customers. The database holds only a digest, which is what request authentication compares against.

Revoking a grant at the provider takes effect at the provider. Meetext detects the revocation and marks the environment disconnected rather than continuing to hold a credential that no longer works.

Meetext runs on Google Cloud, uses Firebase for authentication, Polar for billing and Resend for transactional email. Destination providers such as Slack, Microsoft and Google receive only what an installation requires. We will publish a versioned subprocessor list before taking on customers with a contractual right to notice of changes.

Operational history is append-only by design, because the value of the record is that it can be replayed. Deleting an organization removes its environments, deployments, credentials and history. Ask us and we will do it; we will not pretend it is instant, and we will tell you when it is done.

Access, correction, export and deletion. Write to support@meetext.xyz and a person will answer. If you are an end customer of a vendor using Meetext, your relationship is with that vendor and we will route your request to them.

Material changes will be dated here and announced to account owners before they take effect. This page carries a real date that somebody edits deliberately.