SpecialOps
Privacy Policy — Signal Report Generator
Effective date: May 4, 2026 · Applies to this hostname only
This policy describes how SpecialOps (“we”, “us”) handles information when you use the SpecialOps Signal Report Generator web service on the subdomain where this page is hosted (the “Service”). This Service exists solely to turn a structured Signal Check report payload (JSON) into a polished HTML report and to give you a private link to retrieve it for a limited time.
This policy does not replace legal advice. If you need contractual terms or a Data Processing Agreement for your organization, contact us using the email below.
1. Who is responsible
The controller for processing through this Service is SpecialOps. For privacy inquiries about this Service: privacy@specialops.tech.
2. What we process
Depending on how you use the Service, we may process:
- Report payload: JSON you consent to send here via an automated client (for example, a Custom GPT Action). It typically includes organizational context, module summaries, scores, identified signals, suggested next steps, and appendix answers derived from your Signal Check conversation.
- Derived HTML report: the rendered report file we generate from your payload.
- Technical metadata: standard web server and hosting logs that may include timestamps, IP addresses, request paths, user agents, and error diagnostics — retained according to our hosting provider’s logging practices.
- Access credentials for your report link: an opaque report identifier and a secret token embedded in the URL returned to the automation client. Anyone with the full URL can retrieve the HTML until it is removed or becomes unavailable.
3. What we do not intentionally collect through this Service
This Service is not designed to collect passwords, MFA codes, API keys, session cookies from your systems, or similar secrets. Do not paste secrets into Signal Check answers or report payloads.
4. Purpose and lawful basis
We process this information to:
- validate the incoming payload,
- render and store the HTML report,
- return a time-limited retrieval URL,
- operate, secure, and troubleshoot the Service.
Where required by law, processing is based on your consent (you explicitly agree before data is sent via the automation client) and/or our legitimate interests in providing the Service securely.
5. Automation clients (including ChatGPT)
If you use a Custom GPT or similar automation to call this Service, your prompt contents and Action traffic may also be processed under the automation provider’s policies (for example, OpenAI’s Privacy Policy). We do not control that processing.
6. Storage, subcontractors, and locations
The Service is hosted on Vercel. Generated HTML may be stored using Vercel Blob. Processing may occur in regions where these providers operate. Their privacy notices describe categories of data they handle as infrastructure providers.
7. Retention
The Service communicates an intended retrieval window for generated reports (typically on the order of several days). Retention in backend storage may not delete instantly at expiry; we aim to align storage with that window and operational needs. You may request deletion of a specific report by contacting privacy@specialops.tech with the report URL if you still have it.
8. Security measures
- HTTPS for browser and API traffic.
- Report viewer responses use private, no-store caching headers where applicable.
- Report HTML responses include X-Robots-Tag: noindex, nofollow.
- Opaque identifiers and tokens reduce guessability of report URLs.
9. Sharing
We do not sell personal information. We share data only with subprocessors needed to run the Service (currently hosting/object storage as described above), or when required by law.
10. Your rights
Depending on your jurisdiction, you may have rights to access, rectify, delete, restrict, or object to certain processing, and to lodge a complaint with a supervisory authority. Contact privacy@specialops.tech.
11. Changes
We may update this policy by posting a revised version on this path. Material changes may be reflected by updating the effective date above.