Privacy Policy
Last updated: 2026-10-01
BlackOps Center is built for professionals. We respect your privacy and collect only the minimum information necessary to provide our services.
BlackOps Center is operated by Blulyne Group LLC (“BlackOps”, “we”, “us”).
Data We Collect and Why
| Category | Purpose |
|---|---|
| Account information (name, email, sign-in identity) | Creating and securing your account, signing you in, contacting you about your account |
| Billing information | Processing payments for your subscription (card details are handled by Stripe, not stored by us) |
| Content you create (notes, brains, posts, drafts, media) | Storing, organizing, generating and publishing content at your request |
| API and MCP usage metadata (which tool was called, when, outcome) | Reliability monitoring and debugging, as described below |
| Chrome extension data | Saving pages, notes and timeline analysis, as described below |
| Website analytics (aggregate usage of our marketing site) | Understanding which pages are useful and improving the site |
What the Chrome Extension Sends
The BlackOps Center Chrome extension may transmit the following data only in response to explicit user actions or while you are actively viewing supported pages:
- The current page URL and title (when saving a page as a bookmark)
- Highlighted text you choose to save as a note
- Visible tweet content displayed in your X/Twitter timeline for relevance analysis
- A per-user extension token used to authenticate requests to your BlackOps Center account
The extension does not include analytics trackers, advertising identifiers, or third-party tracking scripts.
Data Usage
We use this data solely to deliver core functionality, including saving content to your account and providing contextual analysis.
- Tweet content is analyzed in real time and is not persistently stored unless you explicitly save it
- Your extension token can be revoked at any time via Admin → Settings → Browser Extension
- All data is transmitted securely over HTTPS
How BlackOps Monitors Its Own API and MCP Surface
BlackOps records metadata about every call made through its API and MCP tool surface — which tool or endpoint was called, when, how long it took, whether it succeeded, and which workspace it belongs to. This metadata never includes the content of your request or response, and is kept for 90 days.
In most cases, that is the only thing recorded. BlackOps does not keep a second copy of the notes, drafts, or other content you send through its API.
In a small number of specific situations, BlackOps additionally records the full content of a single call — request and response — for up to 14 days, so an engineer can diagnose exactly what went wrong. This only happens when one of the following is true for that specific call:
- The call failed. The server returned an error instead of completing the request.
- An internal consistency check failed. BlackOps runs automated checks that a write actually did what it claimed to do (for example, that an update you requested actually changed the stored content). If one of these checks fails, the call is flagged and its content is kept so the discrepancy can be investigated.
- The response carried a warning. Some responses include a warning about an unusual outcome (for example, a naming collision that was resolved automatically). Calls like this are kept so the warning can be understood in context.
- The call was made by BlackOps' own automated monitoring probe (a “canary”), which continuously exercises the same API surface real customers use, using disposable test data BlackOps creates and deletes itself. This never involves your data.
- BlackOps has enabled a temporary diagnostic window on your workspace, at your request or with your explicit knowledge, to help debug an issue you reported. This window automatically expires within 24 hours and must be explicitly re-enabled if a longer diagnostic session is needed. Every time this window is opened, BlackOps records who opened it, when, and for your workspace — this record is permanent and cannot be deleted or edited by anyone, including BlackOps staff.
At any given moment, the number of calls meeting any of these conditions is very small — most successful calls with no warnings and no automated monitoring involved are never captured this way. When content is captured, it exists only to let BlackOps diagnose the specific problem that triggered the capture, and it is automatically and permanently deleted no later than 14 days after it was recorded, regardless of whether the underlying issue has been resolved. Fields commonly associated with credentials or secrets (access tokens, API keys, authorization headers) are never recorded under any of the above conditions, including automated monitoring.
This captured content is never used for anything other than diagnosing the specific technical issue it was captured for. It is not used to train models, is not shared with third parties, and is accessible only to BlackOps engineering staff through internal, non-public tooling.
Sharing and Recipients
We do not sell your data, and we do not share it with third parties for advertising or any purpose unrelated to operating BlackOps Center. We do share data with a small set of service providers (subprocessors), only as needed to run the product:
| Category | Provider | Purpose |
|---|---|---|
| AI content generation | OpenAI, Anthropic, Google (Gemini) | Generating and processing the text content you request |
| AI voiceover | ElevenLabs | Generating spoken audio for video features |
| Database and storage | Supabase | Storing your account data and content |
| Application hosting | Vercel | Running and serving the application |
| Transactional email | Resend | Sending account and notification emails |
| Payments | Stripe | Processing subscription payments |
| Website analytics | Google Analytics | Measuring aggregate usage of our marketing site |
Each provider receives only the data needed for its function and processes it under its own data processing terms. When you ask us to publish to a third-party platform you have connected (such as X or LinkedIn), we send that content to that platform on your behalf.
Using BlackOps Center Through ChatGPT
When you connect BlackOps Center to ChatGPT, ChatGPT can search and read your BlackOps notes, brains and posts and create new notes and drafts, within your own account only. It cannot publish or schedule content, and it can run only the Sorties you have marked as available in ChatGPT. Content you ask ChatGPT to create or retrieve is processed the same way as if you used BlackOps Center directly. You can disconnect at any time in ChatGPT; see our Support page for details.
Data Retention
- Account data, notes, brains and posts: kept while your account is active. When you request account deletion, we delete this data within 30 days.
- Access tokens (including the ChatGPT connection): access tokens expire after 24 hours and refresh tokens after 30 days.
- API and MCP call metadata: kept for 90 days.
- Diagnostic content captures: deleted no later than 14 days after they are recorded, as described above.
Your Controls
- Request a data export or account deletion by emailing support.
- Revoke your Chrome extension token in Admin → Settings → Browser Extension.
- Disconnect BlackOps Center from ChatGPT at any time in ChatGPT, or email support to have its tokens revoked immediately.
Removing the Chrome extension does not automatically delete content already saved to your BlackOps Center account.