1. Information we collect
- Account and workspace details such as names, business email addresses, roles and team membership.
- Registration details submitted through our website, including company, phone number, business goals and selected channels.
- Customer conversations, Page or account identifiers, message metadata and permitted profile details received from authorized WhatsApp, Facebook Messenger and Instagram connections.
- CRM records such as contacts, leads, notes, assignments, automation events and audit history.
- Security and diagnostic information such as timestamps, IP-derived abuse signals, request logs and integration errors.
2. How we use information
We use information to provide the shared inbox and CRM, route leads, run requested automations, synchronize authorized channels, secure tenant data, provide support and comply with legal obligations. We do not sell personal information or use connected-channel content for independent advertising.
3. Meta platform data
A workspace owner chooses which Meta assets to authorize. Wappo.io requests only the permissions needed to list eligible Pages, receive messages, send authorized replies and maintain webhook subscriptions. Access tokens are encrypted at rest. Customers remain responsible for their Pages, messaging consent and compliance with Meta Platform Terms.
4. Sharing and processors
Information may be available to authorized members of the customer workspace and to infrastructure or support providers acting under confidentiality and security obligations. We may disclose information when legally required or necessary to protect users, the service or the public.
5. Retention and deletion
Workspace information is retained while an account is active and for a limited period afterward for recovery, security and legal requirements. Channel access can be revoked by disconnecting the account in Wappo.io or Meta. See our data deletion instructions to request deletion.
6. Security
We use tenant-scoped access controls, encrypted credentials, signed sessions, audit logs, HTTPS, private database networking and controlled backups. No system can guarantee absolute security, so customers must protect their credentials and promptly report suspected misuse.
7. Your choices and rights
Depending on applicable law, you may request access, correction, export, restriction or deletion of personal information. Workspace administrators should first handle requests involving their own customer records; we support verified requests where required.
8. Google Calendar and Wappo Meetings
Connecting Google is optional and available to workspace owners. With your consent, we obtain your Google account identifier and verified email address and request permission to manage events on calendars you own. Wappo Meetings uses your primary calendar to create meetings you explicitly schedule, generate Google Meet links and ask Google Calendar to send invitations to the guests you specify. We retrieve the specific event created by Wappo to confirm its details or safely retry a scheduling request. We do not import your calendar history or read your Gmail inbox.
We store the connected account identifier and email, an encrypted authorization token, and the meeting title, agenda, guest email, organizer, date, time, time zone, event identifier, Meet link and scheduling status. These records support scheduling, upcoming-meeting cards and recovery from interrupted requests. Credentials are encrypted at rest, access is workspace- and user-scoped, and transfers use HTTPS.
Meeting information is sent to Google to provide Calendar and Meet services and to the invited guests through Calendar invitations. If you explicitly send meeting details in a customer chat, those details are also shared with that recipient through the selected messaging provider. Our hosting and support processors may process stored records to operate and secure Wappo. Google Calendar data is not sold, used for advertising, or used to train generalized AI or machine-learning models.
Disconnecting Google in Wappo removes the stored authorization token and connected-account identity from the active connection. You can also revoke Wappo access in your Google Account permissions. Disconnecting does not cancel existing Google Calendar events or delete Wappo meeting records. Manage or delete the original event in Google Calendar; request deletion of Wappo records using our data deletion instructions. Stored meeting records follow the retention rules above; restricted backups may retain copies until their retention cycle expires, and records subject to legal or security retention are handled as described above.
Wappo.io's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
9. Website chat
When you use a Wappo website chat widget, the connected business receives your messages and any name, email, phone number or meeting preference you submit. Chat data is stored in that business’s workspace for its authorized team. A random chat identifier in your browser remembers the conversation for up to 30 days; starting a new chat removes that browser reference but does not delete the business’s records. The chat records the website origin and page path without query parameters. We use short-lived, IP-derived counters to limit abuse. If you choose the AI assistant, relevant conversation content is processed by the configured AI service to answer your enquiry. Choosing the team option pauses automated AI replies. Enquiry consent is recorded separately from marketing consent. For requests about a business’s chat records, contact that business or follow our data deletion instructions.
10. Contact
For privacy questions or verified requests, contact Dalile Portal LLC at dalile.uae@gmail.com.