Website request data
Like nearly every website, the systems that deliver and protect this site create basic request logs. These logs are used to deliver pages, maintain reliability, investigate problems, prevent abuse, and protect Getracked and its users.
| Information | Purpose | Typical recipient |
|---|---|---|
| IP address | Route the request, apply security controls, diagnose faults, and investigate abuse | Getracked and its hosting, network, or security providers |
| Date, time, requested URL, and response status | Deliver the page, maintain logs, troubleshoot, and measure system reliability | Getracked and its hosting or security providers |
| Browser or user-agent information | Return compatible content and identify automated or malicious requests | Getracked and its hosting or security providers |
| Referring page, when supplied by your browser | Security investigation and troubleshooting | Getracked and its hosting or security providers |
For abuse prevention, the application may place an IP address on a temporary or permanent block list with a reason and expiry time. An administrator may also add a trusted IP address to an allow list that overrides application IP blocks and IP-based request limits. These access-control addresses are encrypted at rest, matched using a one-way identifier, and available only to authorized administrators. Allow-list status never bypasses passwords, consent, CSRF controls, form validation, email restrictions, or injection protection.
Request logs are used for delivery, reliability, troubleshooting, and security. Optional interaction analytics are stored separately and require your choice.
Contact form
The contact form collects your name, email address, optional telephone number, selected department, subject, message, and confirmation that Getracked may use the information to answer your enquiry. Those fields are sent through Getracked’s authenticated SMTP service to the selected team. We use them to respond, prepare or administer a service, keep necessary business records, and protect against fraud or abuse.
To prevent automated abuse, the form uses a hidden anti-bot field, a signed time-limited token, same-origin checks, and per-source request limits. Its ordinary rate-limit and submission records use an HMAC-pseudonymized source address. If the source exceeds a request limit, the application may also create a temporary encrypted IP block with the reason and expiry time shown to authorized administrators. The operational submission log contains the time, outcome, department, request identifier, and pseudonymized source and email identifiers—not the message body. Its configured retention period is 30 days; rate-limit timestamps expire after 24 hours. The hosting or security provider may separately keep ordinary access logs containing an IP address under its own configured retention schedule.
Please do not send passwords, full payment-card numbers, private keys, health information, or other sensitive credentials through the form. Contact-form content is delivered to Getracked’s email provider and retained according to the business and legal requirements described in the Privacy Policy.
Live chat
Live chat starts only when you submit your name, email address, opening message, and consent confirmation. The system stores those fields, later messages, the conversation status and times, message-read times, recent typing timestamps, the last page path, and HMAC-pseudonymized source-address and user-agent identifiers. Read times provide receipts to each side, and typing timestamps provide the live typing indicators. Authorized administrators can read and answer the conversation in the protected admin panel.
The server validates email syntax and checks that the domain has mail or address records when that control is enabled. It rejects domains on an administrator-managed disposable-email list and rejects plus-coded addresses for configured consumer email providers. These automated checks reduce abuse but do not prove who controls a mailbox. Chat creation is limited per pseudonymized source and email address, and visitor messages are rate-limited.
After a chat starts, getracked-chat-session-v1 in local browser storage holds the random conversation identifier and credential, open or minimized state, selected queue, and the last administrator message seen. This functional storage keeps the chat available across pages. It is separate from optional analytics and is not created merely by visiting the site. Selecting End chat closes the conversation and removes the local credential; it does not immediately erase the server record.
Chat records default to 365 days of retention and may be configured from 30 to 730 days. An authorized administrator can permanently delete individual chats or all retained chat records sooner. Injection-attempt records default to 90 days and store metadata and a one-way hash of the rejected value—not the submitted text. Do not send passwords, full payment-card numbers, private keys, health information, or other sensitive credentials in chat.
Customer panel
The customer-panel link opens a separate account service at panel.getracked.ca. The panel may use necessary authentication and security cookies and collect account, login, service, support, and transaction data. The Getracked Privacy Policy applies, together with any additional notice presented when a specific panel feature collects information.
Your choices and questions
- You can configure your browser to restrict cookies, although necessary customer-panel functions may not work without them.
- You can contact Getracked by telephone instead of using the web form.
- You can end a live chat and remove its credential from this browser from inside the chat window.
- You can request access to or correction of personal information, subject to legal exceptions.
- You can ask the Privacy Officer for current details about service providers and processing locations relevant to your account.
Contact the Privacy Officer through the privacy contact form with the subject “Privacy Request.”