How we handle your information
Last updated 15 November 2026 · Operator: Agentica LLC
This notice covers this website and Bizily's connected-mailbox and workspace features. A business workspace decides which mailbox to connect, which correspondence belongs in its shared history, and which colleagues can access its records.
For a privacy question or request, write to hello@bizily.ai. Identify the workspace and the information concerned; do not send us your password or Google access tokens.
Website enquiries
Contact forms collect the fields you type and your e-mail. We use them to reply to your enquiry. We do not sell these submissions, share them with other applicants, or add enquiry submissions to the early-access list without its separate consent.
Submissions are delivered to hello@bizily.ai and kept while the pilot conversation is open. Contact that address to request removal. This website sets no advertising cookies.
Language preference
We use your browser’s language preference to choose English or Thai on supported pages. If you choose a language, a first-party cookie named bizily_locale remembers that choice for up to one year. It contains only the language code and is not used for advertising or to identify you. You can change the choice using the language menu or clear it in your browser.
Early-access waitlist
The waitlist is separate from a product account and from ManaEsse template downloads. If you check its consent box, Agentica LLC uses your email, selected role, optional company, language, consent date and notice version to manage early-access interest and contact you about access or purchasing needs. We also save a limited referral label: whether the link came from ManaEsse templates, which template category, and which link placement. We do not save the full referring URL or its query string in your waitlist record.
You can also join from the Bizily box on ManaEsse’s template pages. That box sends the same details straight to this waitlist under the same notice. ManaEsse does not receive or store them, and the template download does not depend on joining.
Waitlist details are stored in a separate database hosted by Neon. The website has permission to submit signups, without direct permission to read, update or delete the list. This form does not send an automatic email, create a company workspace, contact suppliers or place orders. Joining does not guarantee access or a launch date. Supplier prices and procurement records are not collected by this form.
We keep these details while organizing early access and review them when the pilot or your participation ends. You can withdraw consent, request a copy or ask us to delete your waitlist details by emailing hello@bizily.ai. Any future subscription emails must include an unsubscribe option. A waitlist withdrawal stays withdrawn if the same address is submitted again.
What a Gmail connection accesses
Google sign-in identifies the verified account requesting workspace access. Connecting Gmail is separate: the connection records the mailbox identity and granted permissions, and stores encrypted refresh credentials for the enabled features.
Correspondence sync uses Gmail read-only access. It retrieves Sent messages, including sender and recipient information, subject, message text and HTML, timestamps, message identifiers, attachments and the raw message. The first sync reviews a bounded period of up to 90 days; later runs follow new Sent-mail history. This is a backfill limit, not a promise that imported records are deleted after 90 days.
Messages are fetched and parsed before workspace routing rules are applied. Eligible correspondence is added to shared customer history. Internal-only mail is excluded. Other messages may be held or skipped when sender, recipient, BCC or customer-matching rules are not satisfied; an existing customer-thread association can resolve some otherwise unknown recipients. Routing exceptions retain limited evidence rather than importing the body into shared customer history.
The sync does not edit or delete Gmail messages. Read-only permission is broader than the application's Sent-mail use; the routing rules do not change the permission Google grants.
What Gmail sending is used for
Gmail sending requires separate authorization. Supported uses include e-Tax invoice filings and supplier quotation requests and follow-ups through a connected mailbox's sending identity. Sending controls are separate from correspondence sync. A connection that already has both permissions can retain both when reconnected.
Sending discloses the message and included attachments to its recipients. Review the recipient and relevant sender settings before sending. A successful Google authorization is not evidence that a message was delivered or that a tax filing was certified.
Storage, sharing and workspace access
Imported correspondence becomes a business record in the workspace. Message content and routing information are stored in its database; imported attachments and raw messages can also be stored in private file storage. Authorized workspace users can view shared records according to their permissions.
Vercel hosts the application, Neon provides its database, Cloudflare R2 stores private originals, and Google supplies sign-in and Gmail access. Other services receive information when their corresponding feature is used. The Subprocessors page describes those services. A service's inclusion does not mean every message is sent to it.
Saved Gmail refresh credentials are encrypted. The application checks access to shared records and private originals. See Security for the controls and their limits.
AI assistance and human access
Correspondence in shared history may be available to workspace AI assistance when an authorized user or configured feature uses that history. Relevant text can then be sent to the configured AI service. The provider and handling depend on the feature and workspace configuration; connecting Gmail alone does not mean every Sent message is automatically submitted to an AI model.
For gateway calls governed by the workspace's zero-data-retention policy, Bizily requests zero retention and prohibits prompt training. Separate services follow their own disclosed handling and the applicable workspace restrictions. Zero retention is distinct from a provider's default no-training policy.
We do not use Google Workspace API data to develop, improve or train generalized or non-personalized AI or machine-learning models, and do not authorize our providers to do so.
Access by our personnel or service providers to Google-derived content is limited to the user's documented permission for the specific information, security needs, legal obligations, or another circumstance expressly permitted by Google's Limited Use requirements. Shared access by workspace colleagues follows the connection's disclosed purpose and workspace permissions.
Google API data and Limited Use
Bizily's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements, and the applicable Google Workspace user-data policy. These commitments cover derived information as well. We use Google data for the disclosed user-facing features; we do not sell it, use it for advertising or transfer it for unrelated purposes.
A working mailbox connection does not mean Google has verified the application's Gmail scopes. This notice does not claim Google approval or a completed security assessment.
Disconnecting, retention and deletion requests
Disconnect removes Bizily's saved refresh credentials for that connection. It does not retract a sent message or erase imported business history. You can also revoke access in your Google Account.
Imported records remain available for the workspace's customer history and audit purposes. Archive hides a conversation and supports restoration; it does not erase its messages or original files. Neither the 90-day backfill limit nor workspace closure establishes that all stored copies have been deleted. Automated organization-wide permanent purge is not currently enabled.
To request access, correction or deletion, contact hello@bizily.ai. We verify the request and affected workspace, identify the records and stored copies involved, explain any retention or technical limitation, and confirm the action actually completed. Do not treat Disconnect, Archive or closure as confirmation of permanent removal.