1. Controller and contact
Kagenami is operated by Denys Hoptsii, the controller of the personal data described here. Contact: denys@kagenami.com.
Website: kagenami.com. Postal address: Koliště 639/21, 602 00 Brno - Zábrdovice, Czechia.
2. Information we handle
- Account data: email, name, profile image if provided by sign-in, account identifier, authentication records and sessions.
- Creative data: prompts, scripts, project settings, uploaded references and assets, generated visuals, narration, videos, recipes and metadata.
- Usage and billing: plans, credits, generation status, provider usage, transaction and subscription identifiers, payment status, refunds and disputes. Checkout providers handle card entry; Kagenami does not store full card numbers or security codes.
- Technical and security information: requests, timestamps, errors, IP-related request identifiers and operational logs needed to run and protect the service.
- Support correspondence, privacy requests, showcase submissions, shared recipe links and referral records when you use those features.
Do not put sensitive personal data, private identity documents or another person's confidential information in prompts or uploads. You must have an appropriate basis and permissions for personal data you supply about others.
3. Why we process data
- Accounts, generation, storage, downloads and support: performing our contract or taking steps you request before it.
- Billing and refunds: performing the contract; required accounting, tax and legal records: legal obligations.
- Security, abuse prevention, troubleshooting, reliability and defending claims: legitimate interests, balanced against your rights.
- Optional publication or features requiring consent: your specific choice or consent where applicable; consent can be withdrawn without affecting earlier lawful processing.
Without data necessary for a requested feature, that feature may be unavailable. We do not use your content to train a general-purpose Kagenami AI model. This does not replace connected providers' independent processing policies.
4. Providers and recipients
Content needed for enabled features may be sent to Anthropic, Google or OpenAI for AI text, image, speech or related processing. Optional voice dictation sends your recording to OpenAI for transcription. Kagenami does not save the original dictation recording to application storage; the transcript can become part of your prompt.
Google sign-in supplies account profile information when selected. Support messages sent to denys@kagenami.com are forwarded through Namecheap email forwarding to Gmail (Google). The service for outgoing sign-in links and application messages is still to be confirmed. Infrastructure providers host service data. Authorised operators access information as needed for support, security, maintenance and moderation.
Checkout providers process payment and fraud-prevention information. Paddle acts as a separate controller for its payment processing: see Paddle's privacy notice. A Stripe checkout instead involves Stripe. The checkout identifies the provider used.
Selected hosting for launch (not yet deployed): OVH SAS (OVHcloud). Primary application data location: London, United Kingdom. This location does not cover separate AI, email, sign-in or payment providers. Their processing arrangements and the hosting processor agreement must be confirmed before public launch.
Necessary disclosures may be made to meet legal requirements, protect rights, investigate abuse or complete a lawful business transfer with safeguards. The current application does not sell personal data or supply it to advertising networks.
6. Cookies and browser storage
Authentication and security cookies enable sign-in. A theme cookie and local browser storage remember appearance, language and creative preferences. Session storage can hold prompt drafts and referral tokens during navigation. The theme cookie lasts up to one year; local storage remains until cleared or replaced; session storage normally ends with the tab's session.
The current application has no advertising trackers or third-party marketing analytics. Sign-in and checkout providers may use cookies under their own notices. Clearing or blocking storage can affect sign-in and preferences. New optional tracking would require an updated notice and consent where applicable.
7. Retention and deletion
The following retention schedule is selected for the public launch. Server schedules, backup expiry and deletion after restoration still require deployment verification; this draft does not claim they are already operating.
- Account details, completed projects, prompts, references and generated media: while your account and the relevant content are maintained, until you delete them or request deletion. Projects are not automatically deleted after 30 days.
- Working media files of failed, cancelled or deleted generation tasks: scheduled cleanup after 30 days from the last task update. This file cleanup does not itself erase the database task history.
- Routine technical and security logs: up to 30 days, with earlier deletion possible under size limits. Relevant evidence for a specific incident or dispute may be restricted and retained until that matter is resolved.
- Routine backups, including older copies of deleted data: up to 7 days. They are used for recovery and not for ordinary account access.
- Ordinary support correspondence: 12 months after the request is closed. Necessary evidence of privacy requests, disputes and legal compliance is kept separately for the period needed to fulfil the obligation or resolve the matter.
- Billing and credit records: while needed to provide and reconcile your credits, payments and refunds, then for the accounting or tax period applicable to the record and the operator, or while a specific claim remains unresolved. Mandatory financial retention does not require keeping your creative content. Paddle retains its own records under its privacy notice.
Account deletion removes access and application-held video files, clears or redacts related content and removes personal creative libraries. Accounting and operational records can remain linked to an internal identifier: removing name and email does not necessarily make them anonymous. Approved shared catalog assets can remain as described above.
Deletion does not erase providers' independent records or downloaded files. After recovery from a backup, completed deletion requests must be reapplied before access to restored data is reopened. Retention exceptions are limited to the information necessary for a documented obligation, incident or claim.
8. International processing and security
Providers may process information outside your country, including outside the European Economic Area. Before production processing starts, the operator must confirm processor agreements, locations and required transfer safeguards, such as adequacy decisions or standard contractual clauses. Request details through denys@kagenami.com.
Access controls, signed media links and other technical measures help protect data; absolute security cannot be promised. The public service must use HTTPS. Local development is not evidence of production hosting or security.
9. Your rights
Where applicable, you can request access, correction, deletion, restriction or portability; object to processing based on legitimate interests; and withdraw consent. Rights depend on the legal basis and circumstances. We may request proportionate information to verify a request.
Email denys@kagenami.com. We normally respond within one month and explain any permitted extension within that period. You can complain to your local supervisory authority, including the Czech Office for Personal Data Protection.
Kagenami generates creative content; it is not offered for automated decisions about people with legal or similarly significant effects.
10. Children and policy changes
Kagenami is intended for adults aged 18 or older. We do not knowingly provide accounts to children. Contact denys@kagenami.com if you believe a child has provided personal data.
The revision date appears above. Material new purposes, recipients or tracking will be explained before applying, with consent obtained where required.