Privacy
Respect and scope
Respect for privacy is part of the care for our neighbors that guides deepzoe. This policy describes the current blog and administration area. Articles are public and require no reader account. There is currently no reader registration, comments service or newsletter signup. Deepzoe’s administration is operationally responsible; the formal controller’s identity still needs to be published before public launch. Privacy requests can be sent through the contact form.
Browsing information
Your browser transmits technical information needed to deliver pages, such as IP address, browser type, language, requested address and request time. Infrastructure may log some of this information for operation, troubleshooting and security. Search terms are part of the requested URL and may appear in technical logs. Avoid including personal or confidential information in searches.
Language and functional cookies
The blog reads your browser language to suggest an initial version. Choosing a language stores the deepzoe-language cookie for up to one year. It contains no name or email address and is not used by the blog for behavioral advertising. You can delete or block cookies in your browser; doing so may prevent your preference from being remembered.
Administrative access
Only the administration area uses Supabase authentication. It processes email addresses, user identifiers, authentication credentials and session information needed to check access. Session cookies keep administrators signed in. Passwords are not stored as plain text in post tables. Publication changes produce audit records containing the article identifier, responsible user, action, status and time.
Contact and sensitive information
The contact form collects your name, email, country, subject and message, plus an optional phone or WhatsApp number. These details are stored in Supabase and are accessible only to authorized editors to handle your request. Submitting does not subscribe you to marketing. A limit of three messages per email address per hour reduces repeated submissions. Do not send passwords, unnecessary documents, other people’s details or unnecessary intimate accounts. Religious beliefs and health information can require special protection. The blog does not request such information to grant reading access or build belief profiles from viewed articles.
Purposes and legal grounds
Information necessary to deliver pages, protect the service and control access is processed for those purposes. The legal ground must match the operation and applicable law, potentially including appropriately assessed legitimate interests, legal obligations or a relevant contractual relationship. Optional functions requiring consent must request it specifically and allow withdrawal. Simply visiting does not provide blanket consent for unrelated uses.
Providers and international processing
Supabase supplies the database and authentication. Vercel hosts the website, and images uploaded by editors are stored in Cloudflare R2. These images can be delivered through the blog’s domain, with storage access handled on the server. Providers may process technical data according to their roles and configurations. The Supabase project is in a United States region. Before launch, the administration must document actual providers, international transfer conditions and applicable safeguards; this policy does not claim that review is complete.
Advertising and external services
The advertising space at the top of the homepage uses Google AdSense. Google and its partners may process IP addresses, browser information, identifiers and cookies to deliver ads, measure results and prevent fraud, according to applicable consent choices and settings. Contact details are not sent by this ad unit code. Advertising consent choices are managed by the consent platform configured in AdSense; the administration must keep it enabled for regions where it is required. You can manage browser cookies and consult Google’s advertising policies and controls. External links lead to services with their own policies.
Retention and security
Language preferences last up to one year. Administrative data is kept as needed for access management; audit records support publication integrity. Log and backup retention depends on provider settings and still needs a formal production schedule. We do not promise immediate deletion of every record on request. Access controls and database policies restrict information, but no system can guarantee complete protection against incidents.
Your rights
Depending on applicable law, you may request confirmation, access, correction and, where provided, erasure, objection, portability or withdrawal of consent. Legal conditions and exceptions apply. Only information necessary to verify identity and locate records should be requested. You may also contact Brazil’s ANPD or the competent authority in your jurisdiction. Use the contact form for privacy requests and identify the topic in the subject. Do not send identity documents unless requested.
Children and policy changes
Families may read our content together, but there is no child-focused registration or intentional collection of children’s information for marketing. Guardians should supervise minors’ sharing of information. Material changes in processing must be reflected here and communicated appropriately. Until the formal responsible party and operational details described above are completed, this remains a policy being prepared for launch.