Privacy Policy
Agentic Copilot (ai.nowidevops.com) · Operated by iDevOps LLC · Effective date: July 6, 2026 · Last updated: September 26, 2026
This Privacy Policy describes how iDevOps LLC ("we", "us") collects, uses, stores, and protects information when you use Agentic Copilot, our AI-assisted development platform available at https://ai.nowidevops.com (the "Service").
1. Information We Collect
- Account information — your email address and authentication identifiers, managed through Firebase Authentication when you sign in.
- Content you provide — prompts, uploaded files, screenshots, and other material you submit to AI analysis sessions.
- Connected-service data — data accessed from third-party services (Google Drive, Microsoft OneDrive, Gmail) only when you explicitly connect those accounts, as described below.
- Usage information — session records, feature usage, and credit/billing activity associated with your account.
2. Google User Data
Certain features let you connect your Google account. We request only the minimum scopes each feature needs:
- Google Drive (read-only) —
drive.readonly: when you connect Google Drive and explicitly grant a session access, AI models can list, search, and read files in your Drive (or a folder you designate) to answer your requests. The Service never modifies, creates, shares, or deletes your Drive files.
- Gmail (read-only) —
gmail.readonly: used solely by the Email Summaries feature to read messages for generating summaries you request. The Service never sends, modifies, or deletes email.
- Email address —
userinfo.email: used to display which account is connected.
How Google user data is used, stored, and shared
- Use — file and message content is processed only to fulfill the specific request you make in a session (e.g., "summarize this document"). We do not use Google user data for advertising, profiling, or training our own models.
- Storage — OAuth tokens are stored per-user in Google Cloud Firestore, isolated by your account ID and encrypted at rest by Google Cloud. File content read during a session may be included in that session's saved record, which only you can access and which you can delete at any time. We do not maintain a separate copy of your Drive or mailbox.
- Sharing — content you ask the Service to analyze is transmitted to the AI model providers that power your session (e.g., Anthropic, OpenAI, Google) solely to generate the response. We never sell Google user data or share it for advertising. We do not transfer it to third parties except as required to provide the feature you invoked or as required by law.
- Human access — we do not read your Google user data except with your permission for support, when required for security investigation, or as required by law.
3. Microsoft User Data (OneDrive and Teams)
When you connect Microsoft OneDrive, we request the read-only Files.Read permission. AI models may list, search, and read files in your OneDrive (or a folder you designate) only within sessions where you explicitly grant access. OAuth tokens are stored per-user in Firestore with the same isolation and encryption as described above. The Service never modifies, creates, shares, or deletes your OneDrive files.
When you connect Microsoft Teams, we request read-only permissions (Chat.Read, Team.ReadBasic.All) so AI models can list your chats and read messages you can already see, only within sessions where you explicitly grant access. Reading team channel messages additionally requires your organization administrator's consent. The Service never sends, edits, or deletes messages on your behalf.
3a. Slack Data
When you connect Slack, we request read-only user-token scopes (channel/group/DM read and history, and search where your workspace plan allows it). AI models may list conversations and read messages visible to your Slack account, only within sessions where you explicitly grant access. Slack tokens are stored per-user in Firestore with the same isolation as above. The Service never posts, edits, or deletes Slack messages. You can revoke access at any time from the Disconnect button or from your Slack workspace's app management page.
4. Your Controls: Access, Revocation, and Deletion
- Per-session control — connected drives are only available to AI models in sessions where you check "Grant access this session". You can also limit access to a single folder.
- Disconnect anytime — the Disconnect button on each connector immediately deletes the stored OAuth tokens for that provider.
- Provider-side revocation — you can also revoke the Service's access from your Google Account permissions or Microsoft account permissions.
- Session deletion — you can delete any saved session (including any file content quoted within it) from your session history.
- Cancel your account — from the Account page. Sign-in is turned off and your data and credit balance are kept. The confirmation email has a link to reactivate the account, and you can ask for a new link from the sign-in page at any time.
- Remove your account — from the Account page. Sign-in is turned off right away, and your personal data is erased 30 days later unless you stop the removal from the link in the confirmation email.
- Delete your account — from the Account page. We email a one-time link that expires in 24 hours. When you confirm from it, your account closes at once and your sign-in and personal data are erased in the background, usually within minutes (a step that fails is retried, which can take a few hours). This cannot be undone.
- What removal and deletion keep — billing records (payments, invoices, refunds, credit purchases and credit history, license purchases) are kept as the law requires, together with the account email they belong to and a minimal record of the deletion (the email and the dates). Any unused credit balance is forfeited. Teams you own and shared collaboration content are reviewed by us rather than deleted automatically, because other people use them. You can also contact us at the address below.
5. Data Security
The Service runs on Google Cloud (Firebase Hosting, Cloud Run, Firestore). Data is encrypted in transit (TLS) and at rest. OAuth connections use signed, expiring state tokens; access tokens are refreshed automatically and never exposed to your browser or to other users. Each user's connections and sessions are isolated by their authenticated account ID.
6. Data Retention
OAuth tokens are retained until you disconnect the provider or delete your account. Session records are retained until you delete them. Operational logs are retained for a limited period for security and reliability purposes. A cancelled account is kept, closed, until you reactivate, remove or delete it. A removed account is erased 30 days after the request. Billing records are retained after removal or deletion for as long as tax and accounting law requires.
7. Children's Privacy
The Service is not directed to children under 13, and we do not knowingly collect personal information from children.
8. Changes to This Policy
We may update this policy from time to time. Material changes will be reflected by an updated effective date on this page.
9. Contact
iDevOps LLC
Email: info@nowidevops.com