ZTNZero Time Network
Home About Us
All Services Fiber Internet Business Internet Dedicated Internet Enterprise Solutions
Coverage Areas Network Infrastructure Support Contact Us
Get Connected
Home About Us
All Services Fiber Internet Business Internet Dedicated Internet Enterprise Solutions
Coverage Areas Network Infrastructure Support Contact Us Get Connected
Home/Privacy Policy
Legal information / ZTN

Privacy Policy

Understanding How Information Is Handled When You Visit ZTN.

This document explains how information may be handled when you browse the ZTN website or submit an inquiry through it. It distinguishes possible website practices from arrangements that must be verified before publication.

Effective Date: [Insert Effective Date]Last Updated: [Insert Last Updated Date]
Contents
  1. 01 Introduction and Scope
  2. 02 Information We May Collect
  3. 03 How Information May Be Used
  4. 04 Legal Bases for Processing
  5. 05 Contact Form and Inquiries
  6. 06 Cookies and Similar Technologies
  7. 07 Analytics and Measurement
  8. 08 Advertising and Third Parties
  9. 09 How Information May Be Shared
  10. 10 Data Retention
  11. 11 Data Security
  12. 12 International Transfers
  13. 13 User Privacy Rights
  14. 14 Children’s Privacy
  15. 15 External Websites and Links
  16. 16 Policy Updates
  17. 17 Privacy Contact
  18. 18 Additional Legal Resources
  19. 19 Policy Summary
Review required before publication.

This policy must be reviewed and customized against the deployed website, its actual technologies, business practices, and applicable law before publication. Bracketed text is an editable placeholder, not a verified fact. This document is informational; it is not legal-compliance advice and does not guarantee compliance with any law.

01. Introduction and Scope

This Privacy Policy describes the categories of information that may be handled in connection with the website at https://ztn.agency/ and relevant interactions initiated through that website. In this document, “ZTN,” “we,” and “our” refer to the website operator identified by the ZTN — Zero Time Network brand, subject to confirmation of the appropriate legal entity before publication. “You” refers to a visitor or a person who communicates through the website. The policy is intended to help you understand possible collection, purposes, disclosures, choices, and limitations, rather than to imply that every described practice is active on every version of the site.

“Personal information” means information that identifies, relates to, describes, or can reasonably be linked to an individual, as understood under applicable law. Depending on the circumstances, a name, contact detail, device identifier, or combination of location and inquiry details may qualify. Information that has been irreversibly anonymized so that an individual cannot reasonably be identified may be treated differently under applicable law. Terminology and statutory definitions vary between jurisdictions; the meaning applicable to a particular visitor must be determined under the relevant law.

The policy concerns people who browse public pages, follow links, submit website inquiries, or otherwise interact with website functions. It includes the browsing and inquiry activities described below only to the extent they actually occur in the deployed website. A service description on another ZTN page is not itself a statement that a telecommunications service has been supplied, that a visitor has become a customer, or that an account or network-service relationship exists. Separate contracts, service notices, or operational policies may govern a service if one is actually arranged.

Information supplied through an independent communication channel, a third-party site, or an offline business process may be subject to different notices or agreements. This policy does not automatically extend to those contexts merely because the ZTN name appears in a discussion. Similarly, links to an external website do not incorporate that website’s practices into this policy. Where this document says a technology “may” be used, the statement identifies a possible category that must be checked against the actual deployed configuration before it is represented as active.

Before this document is published, the operator should identify the correct responsible business entity, confirm the available contact route, inspect the live website, and reconcile this policy with any agreements and notices that apply to actual inquiries. If a feature or data flow described here does not exist, its description should be removed or revised; if a material practice exists but is omitted, an accurate description should be added. Visitors should not be expected to infer undisclosed practices from a general list of possibilities.

02. Information We May Collect

2.1 Information you provide directly

When an inquiry form is available and you choose to complete it, the fields actually implemented on that form determine what is requested. Potential fields include your full name, business or organization name, email address, phone number, country, city, intended service location, inquiry type, preferred service, subject, and message content. The presence of a category in this policy does not mean that every deployed form requires it or that information is collected merely because a possible field is listed here. Optional and required fields should be identified on the form itself.

Your message may contain additional information you decide to include, such as a general description of a workplace, a connectivity question, or the location for which you are seeking information. Free-text fields can also contain information that the form did not ask for. Please limit what you submit to details relevant to the inquiry. The operator should inspect actual form submissions and handling processes when finalizing this policy, including whether any submitted data is copied into correspondence or other operational systems.

2.2 Automatically generated technical information

Depending on hosting, security, and website configuration, a visit may generate technical records. These could include an IP address, browser type and version, device type, operating system, referring URL, pages requested, approximate access time, general usage events, diagnostic details, and server-log entries. Such records may be generated to deliver a page or diagnose a problem even when you do not submit a form. The actual categories, precision, access permissions, and retention depend on deployed infrastructure and should be verified rather than assumed.

An IP address can reveal an approximate network location, but it does not reliably establish a person’s precise address or identity. Usage events may be associated with a session, device, or browser identifier if the website uses such mechanisms. Some technical information may be personal information under applicable law even where it does not contain a name. A website owner should assess the information available from server logs, security tools, and scripts together rather than assuming that each item is anonymous in isolation.

2.3 Cookies and similar technologies

A browser may store small files or other identifiers if a deployed feature uses cookies, local storage, pixels, or comparable technologies. Those mechanisms can maintain a session, remember a preference, help prevent misuse, or support measurement, depending on what is installed. The presence of this explanatory section does not establish that any particular cookie or tracking category is active. Section 6 explains the potential categories and the importance of checking the live website’s actual behavior.

2.4 Information from third-party sources

If the website uses external hosting, embeds, scripts, integrations, or analytics, an external service may receive information about a visit or provide information to the website operator under its own technical and contractual arrangements. A visitor may also follow a link from another website and arrive with referral information. No particular external provider is identified here as currently integrated. The operator should document actual providers and data flows, including any information received from them, before making a final disclosure.

Information can become more revealing when categories are combined. For example, a technical event associated with an inquiry may reveal the timing or source of that inquiry. The operator should consider whether such association actually occurs, whether it is necessary, and whether notice or a choice is required. This policy does not authorize collection beyond what applicable law and the website’s genuine purposes permit.

03. How Information May Be Used

Information submitted in an inquiry may be used to understand the question, identify the requested service category, review a coverage-related question, and communicate about the visitor’s stated business or connectivity requirements. A name and contact detail can help distinguish correspondence and provide a way to respond where an actual response process is available. A city or service location can help frame a location-specific question; it should not be treated as proof that service is available at that address.

Technical information may be used, where appropriate, to deliver pages, understand whether the website functions correctly, troubleshoot errors, monitor performance, identify abuse or spam, and maintain website security. General usage information could be used to understand how visitors move between pages and which content needs improvement, if suitable measurement is installed. These purposes should be matched to the data actually collected, rather than used as a blanket justification for collecting information that the website does not need.

Information may also need to be handled to comply with a legal obligation, respond to a valid legal process, maintain appropriate records, or establish, exercise, or defend a legal claim where applicable. The existence and scope of such a purpose depend on the relevant facts and law. This section does not imply that a particular inquiry has become a contractual transaction, that every log is retained for legal purposes, or that any specific regulatory regime applies universally.

Uses should be proportionate to the context in which information was supplied. For example, providing a service-location question does not by itself mean a visitor has agreed to unrelated marketing or extensive behavioral profiling. If a new purpose is materially different from the purpose originally explained, the operator should assess whether an additional notice, a different lawful basis, or consent is required before proceeding. The appropriate assessment varies with the jurisdiction, data category, and proposed activity.

Where aggregated statistics are produced, the operator should consider whether the underlying events remain capable of identifying someone and whether a genuinely anonymous result has been achieved. Labels such as “aggregated” and “pseudonymous” do not automatically remove information from privacy law. Any internal access to inquiry details should be limited to personnel or authorized service providers with a relevant need, subject to actual operational arrangements established before publication.

04. Legal Bases for Processing

Some privacy laws require an organization to identify a lawful basis for each processing purpose. The basis that may be available depends on the visitor’s jurisdiction, the relevant organization, the information involved, and what processing actually occurs. This section describes possible grounds for evaluation; it does not claim that one ground applies to every visitor or that listing a ground establishes its validity. The final policy should connect each real processing activity to the appropriate basis under applicable law.

Consent may be relevant when a person makes a sufficiently informed, specific, and voluntary choice about a particular activity. In some jurisdictions, non-essential cookies or certain communications require consent. The existence of a form submission or an acknowledgment of this policy should not automatically be treated as valid consent to unrelated processing. Where consent is relied upon, the operator should provide an appropriate way to withdraw it and address the effect of withdrawal on future processing.

Legitimate interests may be a possible basis under laws that recognize it for activities such as operating a functional website, responding to a relevant business inquiry, or detecting abuse. Reliance on this ground may require an assessment of necessity and the impact on the individual, including available safeguards and reasonable expectations. A business preference alone does not establish that an interest overrides a visitor’s rights. Some jurisdictions do not use this basis in the same way or at all.

Contractual necessity may be relevant where processing is objectively necessary to take steps requested by a person before entering a contract or to perform an actual contract with that person. A casual visit to a public page should not be characterized automatically as a contract. A general inquiry can also be broader than a request to enter a contract. The operator should distinguish these situations instead of assigning a contractual basis to all website interactions.

Legal obligations may require handling particular records where an applicable law actually imposes such a duty. Other lawful grounds may be recognized by the relevant legislation in particular circumstances. Each must be evaluated against a concrete activity and legal requirement, not asserted in the abstract. Where multiple jurisdictions are involved, their rules may differ in terminology, notice requirements, consent standards, and rights. The website owner should obtain appropriate jurisdiction-specific review rather than presenting this general discussion as a compliance determination.

05. Contact Form and Inquiry Information

The Contact Us page may offer an inquiry form. Where that form is enabled, its actual fields may request name and contact details, business or organization information, inquiry type, country, city, service location, preferred service, subject, and message. The form’s displayed requirements should be consulted at the time of submission. Details entered in a message are provided voluntarily, but they may still become part of the inquiry record even if they are not separately requested in a labeled field.

A service-location entry can be useful to distinguish a general coverage question from a question concerning a particular premises. Please identify only the level of location detail reasonably necessary for the question. If you provide an approximate area rather than an address, any resulting discussion may remain preliminary. Business details may help explain the scale or nature of a requirement, but you should not submit confidential internal documents simply to initiate a conversation.

If a follow-up communication process exists, inquiry information may be used to clarify the request and provide relevant information. A submission is not a confirmation of coverage, acceptance of a service order, scheduled appointment, or promise of a response within a particular period. The actual routing, authorized recipients, response practices, and systems used to maintain inquiry records must be checked by the operator. This policy should be revised if the deployed form delivers data to a specific channel that requires additional disclosure.

Please make reasonable efforts to provide accurate contact and location details. An incorrect email address may prevent a response, while an inaccurate location may make a coverage discussion misleading. If you submit information on behalf of another individual, consider whether you are authorized to do so and whether that individual should receive an appropriate notice. Do not include information about other people unless it is relevant and you have an appropriate basis to share it.

Do not submit passwords, one-time passwords or OTPs, payment card information, account security credentials, unnecessary government identification details, or confidential information unrelated to your inquiry. A general web form is not an appropriate channel for these materials. Avoid adding medical, financial, or similarly sensitive information unless a verified and suitable process specifically requires it; this website inquiry form does not request such information. If such details are submitted inadvertently, the operator should assess how to limit access and handle them in accordance with applicable obligations.

Before publication, the website owner should test what happens after submission, identify where records are stored, determine who can access them, and ensure that the visitor-facing confirmation accurately describes the outcome. A form that has no working submission destination should not present a success message. The policy should describe the real process, not an assumed email, support-ticket, or sales workflow.

06. Cookies and Similar Technologies

Cookies are small pieces of information a website or related service may ask a browser to store. Similar technologies can include local storage, embedded identifiers, pixels, or other browser-based mechanisms. A cookie may be set by the website itself or, where an external service is integrated, by another party. Whether any category below is used depends on the technologies actually deployed; this list is explanatory and must not be read as a declaration that every category is active.

6.1 Possible categories

Essential cookies may support a function needed to provide a requested page, maintain a session, or protect basic website operation. Preference cookies may remember a visitor’s choice, such as a selected setting or language, if such a setting exists. Functional cookies may support optional website features or embedded functionality. The boundary between essential and optional functionality must be assessed against the actual feature and applicable law rather than decided solely by the label assigned to a cookie.

Analytics cookies may help measure page visits, interactions, or technical performance if a measurement service is installed. Advertising cookies may be used by an advertising integration to understand campaign activity or deliver relevant advertising if such an integration is actually enabled. Neither category is asserted to be present merely because it is described here. Some measurement or advertising mechanisms use identifiers other than conventional cookies and may require similar consideration.

Session cookies generally expire when the relevant browsing session ends, although browser behavior can affect session restoration. Persistent cookies remain for a specified lifespan or until removed. These terms describe duration rather than purpose: a preference cookie, for example, might be persistent, while another feature might use a session cookie. Actual names, providers, purposes, and lifespans should be identified through an inspection of the live site before a final cookie disclosure is published.

6.2 Choices and deployment review

Browser settings may allow visitors to remove or block cookies, although doing so can affect functions that depend on them. Browser controls may not govern every related technology or every use of information already collected. If non-essential cookies or comparable technologies are deployed, applicable law may require an appropriate consent or preference mechanism, disclosures before activation, and a method for changing choices. The required approach depends on jurisdiction and implementation.

The operator should audit the website in a fresh browser session, including mobile views and any embedded content, to determine what is actually stored and when. An accurate final disclosure should identify active categories and explain controls that genuinely work. It should not suggest that a visitor can change preferences through a control that has not been implemented. This page does not itself place a consent banner or claim that one is unnecessary.

07. Analytics and Website Measurement

If a website measurement tool is installed, it may gather information about page views, traffic sources, device categories, browser characteristics, general interaction patterns, and performance diagnostics. Such information can help identify broken pages, understand which content visitors use, or assess whether a site works across devices. Depending on configuration, events may be aggregated, linked to a browser identifier, or pseudonymous rather than anonymous. The actual collection and identifiability must be assessed from the tool’s settings and data flows.

This policy does not state that any named analytics platform, tag manager, pixel, or advertising measurement tool is installed. No provider should be added to a final policy merely because its product is common on other websites. If measurement is implemented, the operator should check whether scripts load before a visitor has made any choice required by law, whether IP addresses or other identifiers are processed, which events are recorded, and whether any event includes information submitted through a form.

Measurement data can sometimes be combined with information from other services, depending on account configuration and provider terms. The operator should verify whether that occurs rather than assuming that a dashboard’s aggregate display means its underlying data is anonymous. Access to reports, provider-side retention, export features, and deletion settings may also affect the disclosure. An accurate notice should describe the deployed tool and the relevant choices without overstating what is known about a provider’s independent processing.

Where applicable law requires consent or another mechanism for optional measurement, that mechanism should work before the relevant technology is activated. A disabled tool should not be described as actively collecting data, and a planned installation should not be represented as current. Changes to the measurement configuration may require a revised policy and renewed review of notices and visitor choices.

08. Advertising and Third-Party Services

A website can rely on external services for hosting, infrastructure, security, spam prevention, analytics, embedded media, external fonts, scripts, or advertising. Which, if any, of these services operate on the deployed ZTN website must be confirmed through technical and contractual review. This document does not identify a particular provider as active, claim that advertising is used, or imply that every listed category receives personal information.

Where an external component loads in a visitor’s browser, the provider may receive technical information such as an IP address, browser details, or the page from which the request originated. An embedded feature might also set or read identifiers according to its configuration. A service supporting the website behind the scenes may instead process information under instructions from the website operator. These situations can have different legal roles and disclosure requirements; calling every provider a “processor” or every transfer a “sale” would be inaccurate without examining the arrangement.

If advertising services are added, the operator should assess what events they receive, whether they use information for their own purposes, whether visitors can make legally required choices, and whether a separate notice is needed. If a spam-prevention tool is added to an inquiry form, the operator should check what information it gathers before and after submission. Similarly, externally loaded fonts or scripts may create a network request even when no visible form is submitted.

Third-party services may publish their own privacy notices and may process information according to their terms and applicable agreements. Those notices do not replace the website operator’s responsibility to explain its own use of a service where required. Before publication, the operator should maintain an inventory of live integrations, review data-sharing and access settings, and update this policy with verified information appropriate to the actual deployment.

09. How Information May Be Shared

Information may be disclosed to a limited set of recipients where a genuine operational or legal reason exists. Depending on the deployed arrangements, these could include service providers supporting website operation, hosting and infrastructure providers, security or abuse-prevention services, and analytics providers if measurement is enabled. A provider should receive only information appropriate to its function, subject to relevant permissions and agreements. This is a description of possible recipients, not confirmation of a specific current data-sharing arrangement.

Professional advisers may need access to relevant records when providing appropriate legal, accounting, or other professional advice, subject to applicable confidentiality and necessity considerations. Government, regulatory, or judicial authorities may receive information where disclosure is legally required or otherwise permitted under applicable law. A request from an authority should be evaluated in its context; the existence of this clause does not mean that all requests will result in disclosure.

If a lawful business reorganization, transfer, or transaction occurs, relevant information may need to be reviewed or transferred under safeguards appropriate to the circumstances. This paragraph does not claim that any such transaction is planned. The operator should assess notice, continuity of purposes, and other obligations if the situation actually arises. Information made public by a visitor through an external service is outside the control of a private inquiry form and should be considered separately.

Personal information should not be sold or disclosed for unrelated purposes without an appropriate legal basis or required consent. Whether a particular arrangement falls within a jurisdiction’s legal definition of “sale,” “sharing,” or another regulated activity depends on the law and actual technical arrangement. The operator should not make an unverified absolute statement about all possible disclosures; instead, it should identify real recipients and explain relevant choices in the final policy.

Where a service provider acts on the operator’s instructions, reasonable contractual and organizational measures may be appropriate to define purposes, protect information, and address return or deletion. Whether those measures have been put in place must be verified. Visitors should not interpret this section as a representation that every provider has been audited, certified, or subjected to a particular contract.

10. Data Retention

Personal information should be retained only for as long as reasonably necessary for the purpose for which it was collected, taking account of applicable legal obligations and legitimate recordkeeping needs. This principle does not specify a universal number of days or years. Actual retention periods, deletion triggers, backup behavior, and exceptions must be established from the operator’s systems and applicable law before a final policy is published.

Inquiry records may be needed while a question is being considered, while a relevant discussion remains active, or while an applicable dispute or legal obligation requires a record. An unanswered general inquiry may call for a different retention decision from a record that forms part of a later business relationship. The operator should distinguish these situations and avoid retaining every message indefinitely merely because storage is available. Relevant access and deletion procedures should be documented.

Technical and server logs may be kept for operational troubleshooting, security monitoring, or abuse investigation, depending on configuration. Security records may need a different period from routine page-request logs. Cookie preferences, where maintained, may be retained to remember a visitor’s choice, but the actual duration depends on the mechanism deployed. Legal and compliance documentation may be subject to separate obligations or defensible retention needs. Each category should be assessed separately rather than assigned one invented site-wide deadline.

Deletion from an active system may not immediately remove a copy from a backup or a provider-managed archive. Where such copies exist, the operator should understand restoration cycles, access restrictions, and eventual removal. If information has been genuinely anonymized so that it can no longer reasonably identify a person, its subsequent treatment may differ under applicable law; simply removing a name while preserving other identifiers may not achieve that result.

Before publication, the website owner must insert verified retention periods or clear, operationally accurate criteria where required. The final notice should also explain meaningful exceptions, such as legal holds, without implying that every possible exception applies to every visitor. A visitor requesting deletion should be given a response based on the actual records held and the law applicable to that request.

11. Data Security

Reasonable security measures for website information may include HTTPS encryption in transit, secure hosting configuration, access controls, authentication protections for administrative systems, software updates, security monitoring, backups, spam prevention, and limits on administrative access. The appropriate combination depends on the information handled, the threat environment, the deployed infrastructure, and the resources and responsibilities of the parties involved. This list describes measures to evaluate; it does not verify that every measure is currently implemented.

Website security should be considered across the full path of information: the visitor’s browser, the form or application, storage, provider systems, administrative access, and any subsequent correspondence. Encryption in transit, for example, does not alone establish that stored records are encrypted, that a recipient’s mailbox is protected, or that submitted information is inaccessible to an authorized administrator. Controls should be described accurately and not confused with a certification or legal compliance status.

Access should be limited to people and providers with a relevant purpose, and permissions should be reviewed when roles change. Software maintenance and configuration review may reduce preventable vulnerabilities, while monitoring may help identify unusual activity. Backups can support recovery but also create additional copies that require appropriate protection and lifecycle management. A spam-prevention mechanism may help reduce automated abuse without eliminating every malicious submission.

No method of internet transmission or electronic storage can be guaranteed completely secure. Visitors should avoid putting secrets or unnecessary sensitive information into general inquiries and should use appropriate precautions on their own devices and networks. A statement about reasonable safeguards is not a promise that information cannot be accessed, lost, altered, or delayed under any circumstances.

Before publishing this policy, the operator should verify actual controls with those responsible for the deployed site and its providers. It should not claim a security certification, audit result, encryption standard, incident response commitment, or other specific protection without evidence. If a security incident affects personal information, any assessment, communication, or reporting should follow the facts and applicable legal requirements rather than a generic promise in this document.

12. International Data Transfers

Website information may be processed in different countries if hosting, infrastructure, analytics, or another external service is configured to operate across borders. The location of a visitor, the location of a website server, and the location from which authorized personnel access a record can be different. This section does not claim that a cross-border transfer currently occurs or identify any destination country. Actual data locations and access patterns must be verified before making a definitive statement.

Some jurisdictions impose conditions on transferring personal information outside their territory. Depending on the applicable law and the countries involved, an operator may need to assess the recipient, give notice, rely on an authorized transfer mechanism, use appropriate contractual safeguards, or take other protective steps. A mechanism suitable for one legal regime may not satisfy another. No particular safeguard or adequacy decision is claimed to have been implemented by this page.

A provider’s marketing statement that it operates globally does not by itself establish where website data is stored or accessed. The operator should review relevant service settings, contracts, support access, sub-provider arrangements, and backup locations. It should also distinguish a transfer necessary to deliver a requested feature from optional measurement or advertising activity, which may raise different choice and notice questions.

If international processing is confirmed, the final policy should explain it at a level of detail required by applicable law and describe any verified safeguards or available information about them. If no relevant international transfer takes place, this section should be revised accordingly. Visitors seeking information about an actual transfer should be directed through a verified privacy contact route rather than an invented office or officer.

13. User Privacy Rights

Privacy rights depend on the law applicable to the visitor, the organization, and the particular processing activity. The following are examples of rights recognized in some jurisdictions; they are not a promise that every right applies in every situation. A right may be subject to conditions, identity verification, lawful exceptions, competing rights, or restrictions where information cannot reasonably be linked to the requester. The operator should assess each request under the relevant law rather than assuming that a general list determines its outcome.

Access and information. Where recognized, you may be able to ask whether personal information about you is being processed and obtain access to it or related explanatory information. A response may need to protect the rights of other people, confidential material, or records subject to a lawful exception. The operator should search the systems it actually controls and should not promise access to records it does not possess.

Correction and deletion. You may have a right to request correction of inaccurate personal information or deletion of information in qualifying circumstances. An inquiry record may require contextual evaluation: an inaccurate service location might be corrected, while another record might need to be retained for a genuine legal obligation or claim. A deletion request does not always require removal of every copy immediately, particularly where lawful exceptions or backup processes apply.

Restriction, objection, and portability. Certain laws may allow you to ask for processing to be restricted, object to specified processing, or receive eligible information in a portable format. These rights often depend on the processing basis and technical context. Portability, for example, may not apply to all inferred information or all processing activities. An objection may call for an assessment of competing grounds rather than automatic approval or rejection.

Withdrawal of consent. If a particular activity genuinely relies on your consent, applicable law may allow you to withdraw that consent for future processing. Withdrawal ordinarily does not make earlier processing unlawful solely because consent was later withdrawn. A functional method for changing a cookie preference should be provided if the deployed technology and applicable law require it; this page does not claim such a mechanism is already installed.

Complaints. Where recognized, you may have a right to complain to a competent privacy or data-protection authority. The appropriate authority depends on the relevant jurisdiction and facts. This policy does not identify an invented regulator or imply that a particular supervisory authority has jurisdiction over every visitor. It may be helpful to raise a question through a verified privacy contact route first, but doing so should not be represented as a mandatory prerequisite where applicable law says otherwise.

To make a request, describe the right you wish to exercise and the website interaction or inquiry to which it relates. The operator may need enough information to locate relevant records and verify the requester without collecting excessive identification material. Do not send passwords, OTPs, or unnecessary government documents. Applicable response procedures and deadlines should be determined under the law that governs the actual request; this policy does not invent a universal response time.

14. Children’s Privacy

The website is not intentionally designed to collect personal information from children without appropriate authorization where required by applicable law. Its public descriptions and inquiry context are directed toward people seeking information about connectivity and related business questions. This statement does not establish a universal age threshold, because the applicable definition of a child and the required form of authorization can vary by jurisdiction and context.

A child may nevertheless reach a public page or submit information through a general form. The operator should consider whether any deployed feature is likely to attract children and whether additional safeguards, notices, or age-related controls are required. It should not assume that a general audience label eliminates obligations if the actual design, content, or usage indicates otherwise.

If a parent, guardian, or other authorized person believes that a child submitted personal information through the website, they should use the verified privacy contact route once published, or the Contact Us page, to explain the concern. They should provide enough non-sensitive context to help identify the submission without sending the child’s passwords, identification documents, or unrelated private information. The operator should assess the request, any necessary verification, and appropriate handling under applicable law.

If information was collected in a manner that requires parental or guardian authorization and that authorization was not obtained, the operator should determine what action the applicable law requires. Possible outcomes depend on the information, circumstances, and legal rules; this policy does not promise a particular outcome without that assessment. The child’s interests and the privacy of other people involved should be considered in any response.

15. External Websites and Links

The ZTN website may contain links to websites, applications, or services operated by others. An external link can be useful for context, but the external destination may collect information according to its own practices. Clicking a link may disclose technical details to the destination, such as a browser request and a referring page, subject to browser behavior and link configuration. Additional information may be collected after you interact with that destination.

ZTN does not control the privacy practices of independent external websites merely by linking to them. Their notices, cookie choices, security arrangements, and retention policies may differ from those described here. You should review the applicable privacy information and terms of an external service before submitting information to it, particularly if it asks for account credentials or sensitive details.

An external site’s presentation, availability, or content may change without a corresponding change to this policy. A link should not be understood as a guarantee of the third party’s handling of information or an endorsement of every activity on its website. If an external component is embedded directly into the ZTN website rather than reached through a normal link, the operator should separately evaluate whether that component begins processing information before a visitor chooses to interact with it.

To return to the public ZTN website, visit Home. Information submitted on a third-party destination should generally be addressed through that destination’s own privacy channels, unless the website operator also receives or controls a copy. The final policy should distinguish those roles based on the actual integration.

16. Privacy Policy Updates

This policy may need to change if website features, technologies, business practices, data recipients, or applicable legal requirements change. A new inquiry process, measurement tool, embedded service, or storage arrangement could require more than a cosmetic wording change. Before a revision is published, the operator should check whether the revised text accurately reflects the deployed website and whether visitors require additional notice or choices under applicable law.

The effective date and last-updated date shown above are editable placeholders. Before initial publication, they should be replaced with accurate dates using a consistent format. For later revisions, the last-updated date should reflect the relevant published change; the effective date should be managed in a way that does not obscure when a materially different policy begins to apply. The operator may also maintain an internal change record if appropriate.

Revised text can be published at this page’s canonical location. Publication alone may or may not be sufficient notice for a material change under applicable law. This page does not claim that individual emails, in-product messages, or other direct notifications will be sent, because no such system has been verified. If a direct notification process is later implemented or legally required, its description should reflect what actually occurs.

Visitors are encouraged to review the policy from time to time, especially before submitting a new inquiry. A change to this document should not be interpreted as retroactive permission to use previously collected information for an unrelated purpose without satisfying any applicable requirements. Where a proposed change affects consent-based processing, the operator should consider whether a new choice is required.

17. Contact Regarding Privacy Matters

For questions about this policy or requests concerning information submitted through the website, the verified privacy contact email should be published here after the operator confirms that it exists and is monitored. Until then, the following text is an editable placeholder, not a functioning email address:

[Insert Official Privacy Contact Email]

A useful request explains the privacy question or right you wish to raise, the approximate date and nature of the relevant website interaction, and a contact method for a response. If your question concerns an inquiry, its subject or the email address you used may help locate the relevant record. Provide only information reasonably necessary to identify the issue. Do not send passwords, OTPs, payment card data, account security credentials, or unnecessary government identification documents.

The operator may need to verify a requester’s identity before disclosing or changing personal information, but any verification process should be proportionate to the request and the risks involved. A request made on behalf of another person may require appropriate authority to be established. The availability of a right, applicable exceptions, and any response period depend on the governing law; the mere presence of this contact section does not make every requested outcome automatic.

For a general website inquiry, use the existing contact route. The Contact Us page should not be treated as a verified emergency privacy-incident channel or a substitute for a published official privacy email once one is established. Before publication, the operator should confirm which channel can genuinely receive privacy requests and update this text to match its actual handling process.

Contact ZTN

18. Additional Legal Resources

The following pages provide related website information. They should be read in their own context: a service description does not replace a privacy notice, and this policy does not itself establish service terms. Where a separate agreement applies to an actual service, the parties should review that agreement and any related notices for the specific relationship.

Terms & Conditions

Review the website’s published terms and conditions.

Contact Us

Find the website’s inquiry route for relevant questions.

About ZTN

Read the website’s introduction to Zero Time Network.

These links are provided for navigation, not as a statement that an unverified contact detail, company registration, or particular contractual relationship exists. If a linked page is revised, the operator should check that its description remains consistent with this document. Questions about how the pages relate to a particular situation should be directed through an appropriate verified contact route.

At a glance

19. Privacy Policy Summary

This is a summary only. The full Privacy Policy above takes precedence. The points below are a reading aid, not an independent description of every applicable practice, right, exception, or legal requirement.

  • Information may be collected when you voluntarily submit it through an implemented website form.
  • Technical information may be generated automatically, depending on the website’s actual configuration.
  • Relevant information may be used to respond to inquiries and maintain or protect the website.
  • Third-party technologies may process information if they are enabled on the deployed site.
  • Appropriate security measures should be maintained and accurately described after verification.
  • Retention should be limited to what is necessary for genuine purposes and applicable obligations.
  • Privacy rights and available choices depend on applicable legislation and the circumstances.
  • Visitors can raise privacy questions using the verified contact information once published.

The policy must be reviewed and customized against the deployed website, actual technologies, business practices, and applicable law before publication. It does not provide legal-compliance advice or guarantee that any particular legal requirement has been satisfied.

ZTNZero Time Network

Thoughtful internet connectivity for the places we live, the ways we work and the organizations we build.

Company

Home About Us Coverage Areas Network Infrastructure Contact Us

Services

All Services Fiber Internet Business Internet Dedicated Internet Enterprise Solutions

Help & information

Support FAQs Get Connected

© ZTN — Zero Time Network. All rights reserved.

Privacy Policy · Terms & Conditions