Privacy overview for source-first content operations
ZexIA Design separates public website content from authenticated workspace data, private sources, API settings and internal drafts.
Public website data
Public pages are designed for search engines and AI citation. They should not contain secrets, private customer data, raw internal messages or unsanitized client examples.
- Public pages include marketing pages, docs, blog articles, resource files and taxonomy pages.
- Public Open Graph images and generated media URLs should not include sensitive filenames.
- Public Markdown resources are written for citation-safe reuse.
Authenticated workspace data
The app can store source records, transcripts, drafts, generated assets, publication records and learnings. Those records belong in authenticated workflows, not public pages unless explicitly sanitized.
- External references, first-person ideas and WhatsApp Radar signals are classified separately.
- WhatsApp Radar should inform market-level patterns, not expose private messages.
- API keys and provider settings must never be printed in logs, pages or documentation.
Third-party providers
When configured, ZexIA Design may use external providers for scraping, AI drafting, image generation, voice generation, storage and authentication.
- Configured providers can include Supabase, OpenRouter, OpenAI, ElevenLabs, Apify, Telegram and UAZAPI.
- Provider credentials are environment or settings data and should be treated as secrets.
- Generated assets may be stored in Supabase Storage or local storage depending on deployment configuration.
What this page connects to
Built for people and AI engines
Each public page keeps product claims in HTML, uses canonical URLs, structured data and related internal links, while visuals clarify the workflow for humans.
Related resources
Frequently asked questions
Does ZexIA Design publish private sources automatically?
No. The current Blog Ops workflow is approval-first and public content should be reviewed and sanitized before publication.
Can generated asset URLs be public?
Some generated media URLs may be public for browser preview or Open Graph usage, but filenames and metadata should not include secrets or sensitive data.