This notice explains how ownz handles account, page and billing information for its hosted service. Public pages are visible to other people and may be indexed or copied by third parties.
We handle account identity and contact details, protected authentication credentials, session and optional two-factor authentication records, page content and uploads, domain settings, and purchase identifiers, amounts, currencies and payment status. Server and security logs can include IP addresses, browser information and request times. We do not receive cryptocurrency wallet private keys or store full card details.
We use this information to provide accounts, publish pages, manage storage and domains, confirm purchases, provide support and prevent abuse. Where applicable law requires a legal basis, these purposes rely on performing our contract, legitimate interests in operating and securing the service, legal obligations, or consent where required. Buying an add-on does not by itself authorise unrelated marketing.
Authentication cookies keep you signed in. Browser local storage remembers settings such as language and theme. The marketing website uses Umami for usage analytics. Published pages send a cookieless, same-origin page-load event that ownz aggregates by page and day; it is a load count, not a unique-person count. A brief in-memory IP-and-page check limits abuse and is not stored with those totals. We do not sell or rent personal data or insert cross-site advertising trackers into published portfolios.
Hosting, storage and delivery providers, including Cloudflare, process information needed to operate and protect ownz. Payment providers handle transaction data under their own notices. Public media and external embeds can cause a visitor’s browser to contact services such as YouTube or Vimeo, and opening external links takes you to the linked provider. Those services apply their own privacy rules. We may disclose information when required by law or needed to protect legal rights and investigate abuse.
Current add-on purchases use OxaPay. If Paddle checkout becomes available and you choose it, Paddle will act as reseller and merchant of record and process billing, payment, identity, device and fraud-prevention data under its Privacy Notice. ownz and Paddle generally act as independent controllers for their respective billing purposes. We would receive information needed to fulfil and support the purchase. Paddle is not currently integrated, and deleting an ownz account does not erase records a payment provider must retain.
We keep data for as long as needed for the account and service, security, handling disputes and applicable legal obligations. Removing content or an account does not promise immediate deletion from backups, operational records, public caches or payment-provider systems. Providers may process information in other countries; legally required transfer safeguards apply where relevant. Retention depends on the type of record and the reason it is needed.
You can edit or delete your pages in the service. Depending on the law that applies, you may request access, correction, deletion, a portable copy, restriction or objection to processing, and withdraw consent where consent is the basis. These rights can have legal exceptions; we may need to verify identity securely. You may complain to the competent data-protection authority. Use the contact route below to ask for a private channel; do not put personal information in a public report.
Contact the ownz maintainers through GitHub. Ask for a private channel before sharing account or payment details. Do not post passwords, payment credentials or personal documents in a public issue.