1. Information a future approved release may handle
This notice draft covers only the public website source in the web/
tree. It does not cover a deployed domain, product workspace, future customer
runtime, support system, or third-party infrastructure. In the source reviewed on
13 October 2026, the public account-registration and role-request forms are
unavailable, and optional analytics is configured off. No browser, network,
hosting-provider, or production-log inspection was performed.
- No verified public privacy/support mailbox or deletion-request form is configured in this draft. Do not send personal data, credentials, payment-card data, government identifiers, or confidential customer records until an intake route and response procedure are verified.
- A future separately approved account or service may require account identifiers, security records, a defined business brief, and the permissions needed for its specific scope. The actual fields, controller/processor roles, and legal basis must be approved before collection begins.
- The inspected public HTML loads no remote script or stylesheet SDK. That static source finding does not establish what a deployed host, CDN, browser extension, or future application may process.
- Hosting, network, and security infrastructure may process technical request information such as an IP address, timestamps, request identifiers, and errors. The actual providers, locations, retention, and access controls remain unverified for a deployment-specific build.
2. Why we use it
A future approved service may use information only for its disclosed purpose, such as responding to a request, protecting an account, providing the contracted service, preventing abuse, or meeting a legal duty. Optional first-party site analytics is disabled in this pre-release build. If later enabled, an analytics visit identifier may still be personal or pseudonymous data. Any later analytics or marketing use requires a separate, affirmative choice where required by law and must remain optional for access to the service. No marketing email service or newsletter sender was found in this public source review. Before any marketing email is sent, the sender must use a separate recorded opt-in and include a clear, working unsubscribe route in every message.
The model-training, reuse, and customer-content rules for a future service are not settled by this website draft. Before customer data is accepted, the actual service and provider terms must state whether content is processed, retained, transferred, or used for training, and any exception needs separate written approval and a lawful basis.
3. Service providers and transfers
The provider and subprocessor list, hosting regions, access roles, transfer bases, and retention terms have not been verified for the current deployment. No provider name or data location is asserted by this draft. Before any personal or customer data is collected through an approved service, identify the actual seller, controller and processors, document each transfer and retention setting, and obtain the required professional review for Israel, the United States, Australia, each of the 21 Eurozone states, and every additional country where orders may be accepted.
4. Retention and isolation
No deployment-specific retention schedule or clean-deletion procedure has been verified. The public source configures optional analytics off. A future service must state the retention period for each data class, including logs, account data, customer content, backups, and audit records, and explain any legal hold or delayed deletion. A retention schedule must be tested before the relevant data is accepted.
Public registration and third-party social sign-in are not enabled in the inspected website source. No third-party account-deletion callback is part of this source review.
6. Access, correction and deletion
A privacy or deletion request intake route is not available in this draft. The owner intends hello@atacsys.com for these requests but has said the mailbox needs setup. Do not send a request or personal information there until the mailbox, access controls, response owner and deletion workflow have been verified. No form is provided because there is no approved collection and storage path for request data.
The owner-reported preparation scope is initial testing in Israel, the United States and Australia, with intended site purchases from all 21 Eurozone states. This does not confirm deployed accessibility, order acceptance, or approval to sell in any country. Buyer type (business or consumer) is not settled; both legal branches require review. Canada is not in the current first-market list, and future acceptance is unknown. The law, deadlines, authorized representative, appeal, regulator, and cross-border transfer rules that apply to an actual person and data flow require dated professional review for the real seller, product, and every intended jurisdiction before collection. This draft makes no legal-eligibility or rights-deadline determination.