Legal
Privacy policy
Last updated 13 September 2026
Meetext sits between a software company and that company's customers. This policy explains what crosses that boundary, what is retained, and what remains inside each customer environment.
Scope and roles
This policy covers Meetext's websites, dashboard, APIs and customer deployment service. For account administration, security, billing and our own communications, Meetext determines why information is used and acts as controller. When a software company uses Meetext to process information from its customer environments, that company is normally the controller and Meetext acts as its processor under its instructions.
If your employer or a software vendor gave you access to a Meetext-powered integration, its privacy notice also applies. Direct questions about that organization's use of your data to the organization first.
Information we collect
- Account details such as name, email, sign-in provider and organization membership.
- Organization, plan, subscription, invoice and billing identifiers.
- Product, source, capability, approval and deployment configuration.
- Customer-environment state, versions, timestamps, health checks, incidents and audit events.
- Technical data such as IP address, browser, device, request metadata and security logs.
- Support messages, feedback and information you submit through forms.
Where information comes from
We receive information directly from account holders, organization administrators and API clients; from identity and billing providers; and from destinations you authorize, such as Slack, Google Chat, Salesforce or ServiceNow. We also receive operational signals from the cloud services used to deliver and secure Meetext.
How we use information
- Provide, authenticate, configure and maintain the service.
- Route requests to the correct customer environment and approved capability.
- Validate deployments, refresh credentials, detect failures and support recovery.
- Process subscriptions, prevent abuse and protect accounts and infrastructure.
- Answer support requests and send service, security and billing notices.
- Understand aggregate service performance and improve reliability.
- Comply with law, enforce agreements and protect legal rights.
Where applicable, these activities rely on performing our contract, complying with legal obligations, protecting legitimate security and operational interests, or consent when the law requires it.
AI and capability execution
A vendor may connect its own assistant or choose an assistant provided through Meetext. Requests are scoped to the selected customer and the capabilities that customer is entitled to use. Capability results transit through memory and are not written to the operational database. Capability arguments are audited by field name, not value.
Conversation history is not sent to a vendor assistant or stored by Meetext as chat history. A stable thread reference may be used so the vendor's assistant can manage continuity. We do not use customer content to train general-purpose AI models.
Credentials and secrets
OAuth grants, client secrets and API tokens are stored in managed secret storage under identifiers scoped to one customer environment. They are not stored as plaintext fields in the primary operational database and are not shared between customers. Access is restricted to the service identities and operations that need it.
Revoking access at a destination takes effect there. Meetext detects failed or revoked grants and marks the affected environment for reconnection. Some destinations require an administrator to remove or revoke the installation in that provider's own console.
Retention and deletion
We keep information only while needed to provide the service, meet contractual or legal obligations, resolve disputes and protect the service. Active account and deployment records remain while the organization uses Meetext. Security and operational records may be retained for a limited period after an event. Billing records may be retained for the period required by tax and accounting law.
Deleting an organization removes its environments, deployments and environment-scoped credentials from active systems. Encrypted backups age out on their normal schedule and are not restored except for disaster recovery. We may retain minimal records where law requires it.
Security
We use encryption in transit, managed secret storage, least-privilege service identities, customer-scoped credentials, authorization checks, audit records and monitoring designed to protect information. No system is completely secure, so please report suspected security issues promptly to support@meetext.xyz.
International transfers
Meetext and its providers may process information in countries other than yours. Where data-protection law requires safeguards for an international transfer, we use an approved legal mechanism, such as contractual protections, together with appropriate technical and organizational measures.
Your choices and rights
Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, or withdraw consent. You may also complain to your local data-protection authority.
Send a request to support@meetext.xyz. We may verify your identity before acting. If Meetext processes the information for one of our customers, we will direct the request to that customer and assist them as required.
Children
Meetext is a business service and is not directed to children. We do not knowingly collect personal information from children through the service.
Changes
We may update this policy as the service, providers or law changes. The effective date appears at the top. We will provide reasonable notice of material changes through the service or account email.
Contact
Privacy questions and requests may be sent to support@meetext.xyz. Our mailing address is 403 Greenwood, Block H, Gomti Nagar Extension, Lucknow, Uttar Pradesh 226010, India.