No third-party website analytics at launch
The current website does not use a third-party analytics service or advertising tracker and does not currently set analytics or advertising cookies.
Trust · Security and privacy
Ask which system, data, and responsibility a security answer covers.
The public website has documented privacy practices. Product security and customer-service data handling depend on the selected architecture, providers, workflow, and contract and require service-specific answers.
Public website practices
How this website handles visitor information.
These facts apply to Heritage’s current public website and business communications as described in the Website Privacy Notice. They do not automatically describe every customer service.
Answers remain in the visitor’s browser
System Planner answers stay in browser local storage unless the visitor separately chooses to send or discuss them. Resetting the planner or clearing browser storage removes them from that browser.
Heritage does not sell personal information
Mobile numbers and text-messaging consent are not shared with third parties or affiliates for their marketing or promotional purposes.
Requests use a monitored address
Privacy questions, correction requests, and deletion requests may be sent to hello@heritagetel.com. Identity verification or permitted retention may apply.
Do not collapse distinct systems
A website answer is not a product-security answer.
The relevant evidence changes with the selected phone service, messaging platform, reporting or recording workflow, AI provider, integration, customer destination, endpoint, local network, and contractual scope.
Website inquiries, browser-stored planner answers, server requests, transactional delivery, and the published privacy notice have their own data path.
Calling, messaging, reporting, recording, AI processing, integrations, and customer-designated storage may involve different providers, data, controls, and responsibilities.
Users, credentials, endpoints, local networks, destinations, retention choices, and internal policy remain part of the complete answer.
Product-specific questions
No blanket control claim applies to every service.
Useful answers require the actual service, operating model, data, limitations, and contractual requirements.
Who can do what?
Administrative access, customer roles, authentication, authorization, credential handling, account lifecycle, and provider human access require service-specific answers.
What data exists and where?
Encryption in transit or at rest, data location, isolation, backups, retention, deletion, export, and end-of-service behavior are not stated generically.
How is activity observed?
Logging, monitoring, alerting, vulnerability handling, changes, failures, availability, and support responsibilities depend on the configuration.
Who responds and communicates?
Subprocessors, vendor management, incident response, notification, status communication, escalation, and contractual duties depend on the selected service and agreement.
Evidence-led review
Bring a concrete service and requirement.
A useful answer identifies the data, source, destination, people, access, lifecycle, providers, failure modes, and contractual requirement in scope.
- Name the service and workflow.Identify the selected product, provider, customer destination, and intended use.
- Map the data path.Identify collected data, processing, storage, delivery, access, retention, and deletion.
- Assign responsibilities.Separate Heritage, provider, customer administrator, user, endpoint, and local-network responsibilities.
- Verify the requirement.Review current evidence and limitations before making a security, privacy, legal, or contractual commitment.
Shared responsibility
Customer choices affect the complete trust answer.
Customer policy, authorized users, credential administration, endpoints, local networks, recording notice and consent, selected destinations, retention and deletion choices, integrations, and acceptable use can materially change the result.
Safe inquiry boundary
Describe the requirement without sending secrets.
Do not send passwords, API keys, tokens, credentials, sensitive customer information, medical information, recordings, or urgent support requests through the public sales form.