1. Why we publish a changelog
Legal policies shouldn't be a black box that changes quietly. We publish this changelog for the same reasons open-source projects publish theirs:
- Trust. You see not just the final text but the history of how it got there.
- Accountability. If we changed something material (a new subprocessor, new terms), it can't be quietly forgotten.
- Convenience. If you signed with us a year ago, it's easier to see what's different now.
- Regulatory. GDPR and CCPA require us to notify of material changes to data processing. A changelog is the standard way.
2. How we publish changes
Entry format:
- Date — when the change took effect.
- Page — which policy was updated.
- Description — what changed, in 1-3 sentences.
- Type — minor (typography, wording fixes) or major (new subprocessor, new data categories, change of rights).
Material changes that require consent or notice:
- Active business clients get an email 30 days ahead.
- All site visitors may see a notice in the cookie banner or on the policy page itself.
3. Subscribe to updates
Ways to stay in the loop:
- Active KVOKA business clients — auto-receive an email when material changes ship.
- Message us anytime — ask Maks on WhatsApp / Telegram to be flagged when a specific policy changes.
- Manual watch — bookmark this page and check back; the date at the top of each policy always reflects the latest version.
4. Change log
All entries in reverse chronological order (newest first).
2026-05-27 — Initial publication of the legal section
- All policies: first public version of 22 KVOKA legal documents. Includes Privacy Policy, Terms of Service, Cookie Policy, Refund Policy, Warranty Policy, DMCA Policy, Acceptable Use Policy, IP / Content Ownership, Anti-Discrimination Policy, Security Practices, Accessibility Statement, AI Use Disclosure, Company & Contact, Subprocessor List, Cookies Inventory, DPA template, Do Not Sell My PI, Data Deletion Request, Legal Sitemap, Policy Changelog, and related pages.
- Type: Initial publication. Material.
- Applies to all new clients starting on this date.
2026-05-27 — Privacy Policy
- CCPA / CPRA section added and brought up to date (Right to Correct, Right to Limit Sensitive PI).
- PIPEDA / Quebec Law 25 section added.
- Cross-border transfer language updated for Schrems II SCCs.
- Type: Major. Active clients notified.
2026-05-27 — Subprocessor List
- Added Anthropic (Claude) and OpenAI (ChatGPT) as AI subprocessors with an explicit note that no client PII flows to them.
- Type: Major (new subprocessors). 30-day notice given.
2026-05-27 — Cookie Policy + Cookies Inventory
- Cookies Inventory (new page) published as the detailed technical inventory of every cookie / localStorage entry.
- Cookie Policy simplified; it now points to Cookies Inventory for the technical detail.
- Type: Minor (structural reorganization; substantive content unchanged).
2026-05-27 — AI Use Disclosure (new page)
- Published the public AI tool disclosure page (Claude, ChatGPT, GitHub Copilot, Midjourney) covering studio workflow.
- Includes a section on client data protection and opt-out options.
- Type: Major (new page, applies to all active projects).
5. Viewing past versions
We keep past policy versions on file:
- Every document shows its effective date and last-updated date in the page hero.
- If you need the exact prior version — for example, the terms in force when you signed with us — message us and we'll send it.
6. Contact
If you have a question about a specific policy change, or you want to object to a change that affects you as a KVOKA client:
- 📱 WhatsApp: wa.me/37120469306
- 💬 Telegram: @maks_kvoka
- ✉️ Email: hi@kvoka.com (with subject
[Policy]for priority)
For active clients: if you object to a material change (new subprocessor, new terms) — you have 30 days from notification to:
- Propose an alternative.
- Request a transitional regime (new rules apply from your next project, not the current one).
- Terminate the contract with a refund for the unworked portion.
Question about a policy change?
Message Maks with subject [Policy] — priority queue. Active clients can object within 30 days.