PELIKAN&8BELLS / PRIVACY

Privacy policy

Effective and last updated: November 15, 2026

Scope and operator

Pelikan&8Bells is the application name shown on the Google OAuth consent screen. This policy applies to its shared-email and file-management modules, Pelikan Shared Gmail and Pelikan Drive (the “Applications”), operated by Pelikan Trading Inc for authorized business users, and to this public documentation website. The Drive application is being prepared for deployment. Features described here apply when available and enabled.

Information we access

Depending on the permissions granted and features used, Gmail data may include the connected account address, message headers, senders and recipients, subject lines, bodies, attachments, labels and draft or sent-message information. Drive data includes files uploaded through the application or explicitly made accessible to it, file names, IDs, types, folder relationships and relevant metadata. We also process user identity, access permissions, connection credentials and operation records such as actor, action, file or message reference, time and outcome. Hosting services may process IP addresses, browser information and technical logs to deliver and secure the service.

Purpose and permissions

We use this information only to deliver and maintain user-facing business functions: authorized shared-email access and enabled email actions; file upload, listing, preview, download, deletion and print initiation; access administration; troubleshooting and security. Gmail permissions depend on enabled features and the consent screen. Drive is intended to use the per-file drive.file scope rather than blanket access to the entire account. Connecting an account may allow other organization-authorized application users to access its connected data according to assigned permissions. Only connect accounts you are authorized to share for this purpose. Google passwords are entered with Google, not collected by the Applications.

How each data category is used

Gmail message headers and labels support mailbox lists, search and message organization. Bodies and attachments are retrieved to display selected messages and attachments to authorized team members. When enabled and initiated by a user, recipient addresses, draft text and attachments are submitted to Gmail to send or reply to business email. Drive file contents are transferred to the connected Drive account when a user uploads a document and retrieved for authorized preview or download; names, IDs and folder metadata support file lists and folder-level access. A delete action affects the selected item according to the implemented function. Account identifiers link connections to authorized users; OAuth credentials allow the server to make authorized requests without collecting Google passwords. Operation records support accountability and troubleshooting. We do not request access to all Google services simply because an account is connected.

Google data and Limited Use

Our use and transfer of information received from Google APIs will comply with the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including their Limited Use requirements. We do not sell Google user data, use it for advertising or profiling for advertising, or use it to develop, train or improve generalized AI or machine-learning models. Human access is limited to authorized user-facing collaboration, user-consented support, security investigation, legal obligations, or other uses expressly permitted by those policies.

Storage, disclosure and security

Source emails remain with the connected Gmail account, and Drive files remain with the connected Drive account unless an authorized action changes or deletes them. Application databases or caches may hold synchronized content, metadata, permissions and operation records needed for enabled functions. Data is processed by Google and service providers supplying hosting, storage or technical operations, only as needed for the service. Authorized team members may be located in the United States or China, and service providers may process data in other countries. We restrict access to business needs and require appropriate safeguards for credentials and data. No system can guarantee absolute security. Information may be disclosed when legally required, subject to applicable Google data-use restrictions.

Who can receive data

Data is not made public by connecting an account. It is accessible to the account holder and organizational users granted the relevant permissions. Sending email intentionally discloses the message and attachments to the recipients selected by the user. Google processes API requests as the connected email or file provider. Hosting, database and technical-support providers may process data solely to operate and secure the application under appropriate confidentiality and access restrictions. We do not provide Google user data to data brokers, advertising networks or unrelated third parties. Any other disclosure requires a permitted purpose and, where required, consent or a legal obligation consistent with Google’s Limited Use rules.

Retention and deletion

We retain application data only for as long as needed to provide the enabled service, maintain business records, resolve disputes or meet legal obligations. Retention varies by data type; no single automatic deletion period applies to every record. To request deletion of locally held account data, credentials, synchronized copies or identifiable operation records, email the contact below and identify the relevant account and application. We verify authority, delete data no longer needed, and explain any lawful retention exceptions. Residual backup copies are removed through the applicable backup lifecycle. Disconnecting or revoking access stops future authorized API access but does not itself erase previously stored copies or source Gmail/Drive data. Source data must be deleted through the relevant service or an enabled authorized application action.

Your choices and contact

You may review or revoke Google access at Google Account connections. Contact your organization administrator to change application access. For access, correction, deletion or privacy questions, contact Pelikan Trading Inc at hughie@pelikantrading.com. Do not send passwords or authorization tokens. This documentation site uses a browser preference to remember language; it does not request Google account access or include advertising analytics. The Applications are intended for authorized business use, not services directed to children. Material policy updates will be reflected here with an updated date and, where required, notice or renewed consent.

Data deletion requests and revocation

Email hughie@pelikantrading.com with the subject “Pelikan&8Bells data deletion”, the connected account address, the relevant module and the data you want removed. We may request reasonable evidence that you control the account or are authorized to act for the organization. We will identify application-held copies and credentials, remove data no longer required, and explain any business-record or legal retention exception and its basis. Shared business records and data belonging to other users cannot be removed solely on an unauthorized request. You can revoke Google access independently at myaccount.google.com/connections. Revocation does not delete original emails, Drive files, copies already downloaded by authorized users or messages already delivered to recipients. Contact us to coordinate deletion of application-held data separately.