1. Overview
This Data Policy governs how ZEDEC.AI handles data through our Holographic Swarm API and provider services. We operate under the UBH-168 Protocol which prioritizes data efficiency, privacy, and minimal retention.
All data is processed using our 168-protocol suite which compresses, checksums, and routes data with sacred geometry principles. We retain only what's necessary and dispose of transient data immediately.
2. API Data Handling
When you use our API endpoints, the following data handling applies:
| Data Type | Retention | Purpose |
|---|---|---|
| Prompts/Messages | Session only (not stored) | Processing request |
| Responses | Cached 5 min (holographic) | Efficiency/deduplication |
| Token Counts | Aggregated (anonymized) | Billing/accounting |
| Session IDs | 24 hours | Request batching |
| IP Addresses | Hashed only | Rate limiting |
| API Keys | Until revoked | Authentication |
3. Tokens Per Cycle Model
ZEDEC uses a tokens-per-cycle accounting model rather than traditional per-request billing:
- Cycle Duration: 1 second (aligned with UBH-168)
- Tokens Per Cycle: 168 tokens baseline capacity
- Burst Capacity: Up to 144× baseline during fractal bursts
- Accounting: Per-session, per-model, aggregated anonymously
Token usage is tracked for billing purposes but content is never stored beyond the processing window.
4. Holographic Protocol Suite (168)
Our system implements the complete 168-protocol suite for data efficiency:
UBH-168- Universal Binary Holographic compressionPHI-168- Golden ratio timing and scalingRODIN-168- Vortex mathematics checksumsTESLA-168- 3-6-9 resonance validationBURST-168- Fractal burst matrix packagingCACHE-168- Holographic response caching
These protocols ensure maximum efficiency with minimum data exposure.
5. Third-Party Provider Data
ZEDEC routes requests through multiple AI providers. Each provider has their own data policies:
- OpenRouter: Requests may be processed by their infrastructure
- Puter.js: Client-side processing (data stays in browser)
- HuggingFace: Inference API data handling applies
We select providers based on their data handling practices and prefer those with no data retention policies.
6. Data Collection Preferences
API consumers can specify data handling preferences:
"data_collection": "deny"- Route only to providers with no data retention"data_collection": "allow"- Allow all providers (default)
7. No Training on User Data
ZEDEC does NOT use API request data to train models. We are a routing and fusion layer, not a model trainer. Your prompts and responses are processed, not learned from.
8. Security Measures
- All API traffic encrypted via TLS 1.3
- API keys hashed with bcrypt
- Rodin checksum verification on all holographic packets
- Rate limiting to prevent abuse
- No plaintext logging of request content
9. Data Subject Rights
Under GDPR, CCPA, and similar regulations, you have the right to:
- Request access to any stored data
- Request deletion of your data
- Export your usage statistics
- Opt out of aggregated analytics
Contact vino@zedec.ai for data requests.
10. Provider Partnership Data
For provider partners (e.g., OpenRouter integration):
- We share only aggregated, anonymized usage metrics
- Billing data includes token counts, not content
- Model quality scores are derived from latency/error rates, not content analysis
- Partner API keys are stored encrypted
11. Contact
For data policy inquiries:
Email: vino@zedec.ai
API Docs: https://zedec.ai/api/v1/
Protocol: UBH-168 Holographic Swarm