Zulora AI · Zulora Drive

Privacy Policy

This policy explains how Zulora AI accesses, uses, stores, and protects account details, connected Google Workspace data, AI requests, and files stored in Zulora Drive.

Official website: https://zulora.in · Operated by Shiven Panwar (Zulora AI) · Support: zulora.help@gmail.com

Effective date: October 1, 2026

1. Information we collect

We handle the information needed to provide Zulora AI and Zulora Drive. Depending on the features you connect and use, this can include:

  • Account data: name, email address, profile picture, and account identifiers from sign-in.
  • Prompts and app activity: chat messages, responses, generated results, connector actions, and service diagnostics needed to operate your account.
  • Files: images, documents, media, and other files that you attach, upload, generate, or ask Zulora Drive to retrieve or analyze.
  • Connected Google Workspace data: Gmail message headers, metadata and preview snippets; Calendar event details; spreadsheet cell values and spreadsheet metadata; Drive file metadata; and Forms responses, as applicable to the scopes you authorize and the action you request.
  • Zulora Drive records: file name, type, size, folder path, owner identifier, upload and update timestamps, searchable text for supported text files, storage path, and file download URL.
  • Connector details: connected account email, provider, authorized scopes, and connection status. Google OAuth credentials are encrypted on the server before they are saved in the signed-in user's Firestore connector document. An encrypted, HttpOnly cookie provides a browser-session fallback when Firestore is unavailable.
  • Storage metric: Zulora Drive calculates the combined size of indexed files for the signed-in Drive account. Firebase does not expose a per-user remaining bucket quota to the web application.

2. How we use information

We use information strictly to provide the features you ask us to perform: execute requested AI commands, process images and files, display indexed storage usage, manage your files, and automate productivity workflows through connected services. We do not use connected Google data for unrelated profiling, advertising, or marketing.

Google Workspace connector actions run directly against the relevant Google API. Their results may be displayed in your Zulora chat and saved with your chat history. Google connector results are excluded from later AI model context. A copy is written to Zulora Drive only when your request explicitly asks to save or export that report there.

3. Google Workspace access and Limited Use

Google services are accessed only after you connect the service and ask Zulora AI to perform an action that requires it. We use the data returned for that task—for example, to read requested Gmail messages, view or create Calendar events, read or update a spreadsheet, list spreadsheet names using Drive metadata, or retrieve responses from a Form you identify.

The connector requests service-specific scopes. Gmail access can include reading and managing messages and creating or sending drafts; Sheets access can include reading and writing spreadsheets; Calendar access can include viewing and creating events; Forms access is limited to reading responses. The Sheets connector uses Google Drive metadata access to list spreadsheet names and links; it does not provide general access to the contents of all Google Drive files.

Zulora AI'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.

We never sell or rent Google API data, monetize it, use it for targeted advertising, or disclose it to independent AI model providers. We use it only to complete the Google action you requested. Connector results may appear in your Zulora chat history, which Firebase stores to provide your account and chat features. If you explicitly ask to save a Google connector report to Zulora Drive, that report is uploaded to your separate Drive account.

Google user data is never used by Zulora to train or fine-tune generalized AI or large language models.

4. Sharing and service providers

We do not sell or rent Google API data, use it to serve advertisements, or disclose it to independent AI model providers. Google APIs receive requests needed to carry out the Google action you asked for. Google Firebase is a third-party infrastructure provider that processes account and chat records and hosts Drive files and metadata so Zulora can provide its authentication, chat, and storage features.

When you explicitly ask Zulora AI to analyze a Zulora Drive file or an attachment, the relevant file content and prompt may be sent to an AI inference provider to produce that result. Depending on the feature and configured route, providers may include Google Gemini, Groq, Cerebras, Mistral AI, or Pollinations. This applies to Zulora Drive files or attachments; Google Workspace connector results are excluded from model context. Provider-specific processing and retention are governed by each provider's terms.

We do not authorize service providers to use Google API data for advertising or generalized model training on Zulora's behalf. Firebase is a third-party infrastructure provider that processes account, chat, and Drive information to operate the service. This means we do not sell or disclose Google data to independent third parties for their own purposes, but Firebase does process relevant data as our service provider. We may also disclose information if required by law or needed to protect service security.

5. Zulora Drive storage and file access

Zulora Drive uses a separate Firebase project for authentication, file storage, and file metadata. When you upload a file through the Zulora AI connector panel or request an upload, the file is stored in Firebase Storage under your Drive account's owner-scoped path. Its directory record is stored in Firestore. Supported small text files may also have searchable text indexed so you can find them later.

The connector panel shows the total size of indexed files for the signed-in Drive account and updates that total as file records change. This is indexed file usage, not an independent measurement of every byte in the Firebase bucket. Firebase does not expose a per-user remaining bucket quota or a separate Zulora Drive storage plan to the web app, so Zulora does not show a fabricated plan limit or upgrade status.

You can list, preview or open, retrieve for an expressly requested AI task, upload, and delete your files from the Connectors panel. Current Firebase Storage rules limit normal file access and management to the authenticated owner. A Firebase download URL is a bearer link: anyone who obtains that URL may be able to access the file, so share it only with people you trust.

6. Retention and deletion

  • Google access: choose Disconnect in the Zulora AI dashboard to clear Zulora's in-session token and connector record. To revoke Google's authorization grant, remove Zulora AI from your Google Account settings. Disconnecting inside Zulora alone does not revoke Google's grant.
  • Individual Drive files: use the delete control beside a file in Connectors. Zulora deletes the indexed record and the corresponding stored object.
  • All Drive files: choose Delete all in the Drive files panel to remove indexed files and their corresponding stored objects from that Drive account.
  • Complete account-data deletion: use Account Settings or email zulora.help@gmail.com to request deletion of your Zulora account data. The in-app flow deletes the app profile, chat sessions, generated assets, and Zulora browser-stored values. Zulora Drive uses a separate Firebase project and sign-in, so use Delete all in the Drive panel or include that account in your deletion request to have its files removed too.

Some records may remain for a limited period in service backups, security logs, or where retention is required by law. If a deletion action fails or you need help, email support. Revoking Google access stops future API requests that require the grant but does not itself erase existing chat history or Drive files.

7. Security measures

Browser-to-service and service-to-service connections use HTTPS/TLS encryption in transit where supported by the relevant endpoint. Firebase Authentication and owner-scoped Firestore and Storage security rules are used to restrict account and file access. Google OAuth access and refresh tokens are encrypted before storage and are only decrypted by the server for authorized connector requests. An encrypted HttpOnly cookie supports the session if Firestore is temporarily unavailable. Firebase download URLs are bearer links; anyone who obtains one may be able to access that file. No internet service can guarantee absolute security, so keep credentials and download links private and contact support if you suspect unauthorized access.

8. Children's privacy

Zulora AI and Zulora Drive are not intended for children under 13. We do not knowingly collect personal information from children under 13. Contact us if you believe a child has provided personal information so we can review the request.

9. Updates and contact

We may update this policy when our services or data practices change. The effective date at the top identifies the current version.

For privacy questions, Google access revocation, or complete account-data deletion requests, contact our 24/7 Zulora AI & Zulora Drive user support team at zulora.help@gmail.com or WhatsApp +91 6395211325.

Official domain: https://zulora.in