Privacy policy
Privacy terms written for operators, not lawyers alone
The privacy model follows the same principle as the rest of the product: keep the boundaries clear, keep the data paths narrow, and make it obvious who is responsible for what.
This page is a practical summary of how customer and support data is handled inside Raceline.
Privacy contact
Rights requests go to a real inbox
Access, correction, and deletion requests can be sent directly to the privacy contact below.
Privacy contact
Tenant-safe
data separation
Support data is scoped per customer environment rather than pooled into a shared free-for-all.
30 days
deletion target
After account deletion, customer data is removed within the stated window, including backups.
On request
rights handling
Access, correction, and deletion requests can be handled directly through the privacy channel.
At a glance
The essential privacy posture in four cards
These are the parts of the policy most operators need to understand first.
Policy detail
Operational detail behind the summary
The policy is still legal content, but it should remain readable enough for buyers and operators to evaluate quickly.
Overview
Raceline uses customer and support data to operate an AI support platform. This policy explains what data is collected, how it is used, and what rights are available to users and customers.
Data categories
Typical categories include account information, uploaded support content, support conversations, usage analytics, and standard technical telemetry such as IP address and browser details.
Service improvement
Operational and usage data may be used to improve service quality, but tenant isolation boundaries still apply. Customer data is not shared across tenants as training context for other customers.
Retention and deletion
Data is retained while the account remains active. When an account is deleted, data is permanently removed within 30 days, including backup material covered by the retention window.
Ready when you are
If your team needs privacy answers before procurement, bring them in early
It is easier to resolve privacy concerns in direct conversation than after they become a blocker late in the buying process.
Preferred next step
Keep the current page context intact and move directly into the next step.