Skip to main content
Version 1.0 · Draft · Effective date: [to be filled: date]
The Portuguese (Brazil) version prevails in the event of any divergence.
Plain-language summary. Version 1.0 is a draft recorded on 2026-11-07. That date does not establish publication, effectiveness, or acceptance.

1. What this history records

A version identifies an edition; a draft remains under review; publication makes an approved text available; effectiveness identifies when its stated effects begin; acceptance is the required manifestation of agreement for a particular relationship. These events are not interchangeable. This is the editorial record requested for this edition, not confirmation that the center has been deployed or accepted. Version 1.0 does not mean earlier documents shared the same number or date.

2. Version table

No other published edition is confirmed here. The date is November 7, 2026, in year-month-day format. The responsible entity, effective date, and transition conditions must be confirmed before publication. This record does not retroactively change purchases.

3. Previous texts and their replacements

The center is prepared to replace the scattered presentation of the following texts. Actual replacement requires approval, publication, and appropriate communication; it does not erase evidence, accrued rights, or conditions governing earlier events. The consulted combined page displayed February 28, 2026 as its update date; that belongs to the earlier presentation, not this center’s effectiveness. A complete public archive of earlier editions has not been confirmed. Ask support about a text relevant to your purchase, specifying the product and approximate date; availability must be checked and retrieval is not guaranteed.

4. Numbers and effective dates

Read 1.0 together with its status and date. A draft may change before publication; the number alone does not prove accepted content. Future updates should identify the affected document, publication and effective dates, and a summary of material changes. Editorial corrections should not conceal changes to obligations or processing purposes. The legal map explains general terms, product conditions, and policies. A Hub update does not automatically alter a Scripts purchase. For earlier transactions, consider the offer, text presented at the time, event date, and mandatory law.

5. Acceptance and existing records

Existing general acceptance uses a browser-held record. Hub has its own versioned acceptance stored by the service. These mechanisms differ: clearing browser data can remove local records without removing service records; another device does not prove that no contractual relationship exists. Conversely, a local value alone does not establish a person’s identity or every detail of the text shown.
This center’s connection to acceptance flows has not been confirmed. Publishing these files does not collect acceptance, migrate earlier records, or prove agreement with version 1.0.
Before renewed acceptance is requested, the applicable document and material changes should be identified. Where express agreement is required, a general presumption based on visiting a page is not a substitute. Consequences of declining should be explained by product, preserving statutory rights, data requests, and handling of existing charges. Accepting terms does not authorize every data-processing purpose. Brazil’s LGPD (Law 13,709/2018) requires an appropriate basis for each operation; consent-based processing must meet statutory requirements, including withdrawal. Cookie preferences are separate from contractual acceptance. For people in the European Economic Area, the GDPR applies when its requirements are met. Consumer rights under the CDC (Law 8,078/1990), including article 49 where applicable, survive document updates. Article 15 of Brazil’s Internet Civil Rights Framework (Law 12,965/2014) requires covered providers to retain application access logs for six months. That is not a general rule to retain every acceptance record or all content for the same period. Contractual records and personal data require their own grounds and retention analysis.

7. Asking about a version

1

Identify the context

Give the product, approximate date, and relevant document or notice. For a charge, include only the necessary reference.
2

Describe the issue

Explain whether you need an earlier text, change details, or acceptance information. Redact third-party data and credentials from screenshots.
3

Choose a channel

Use email or a support ticket. Do not publish identity documents or financial information in an open community.

8. How we notify you of changes

Material changes should receive appropriate notice, such as email or a dashboard message, before effectiveness when necessary. Existing Spaces conditions include at least 30 days’ notice in the situations specified there; this center does not reduce those commitments. Notices should distinguish editorial and material changes and explain when renewed acceptance is required. Urgent legal or security changes should be explained according to the circumstances and applicable rights, without indiscriminate retroactivity.

9. Contact

Email dogly.tdc@gmail.com or open a dashboard support ticket for version or purchase questions. For personal data relating to acceptance or officer details, see Data protection officer and contact. Responsible party: the DoglyTdc Team. Do not send passwords or authentication codes.