1. Who controls your data
For this deployment, the VeloTechLog service operator is the data controller for data processed through this service. The operator’s identity and contact details must be provided in the service’s contact channel before production use. This policy does not invent those details.
2. Data we process
- Intervals.icu account identifiers and profile information returned during OAuth.
- OAuth credentials or tokens needed to maintain the authorized connection.
- Activity metadata retrieved from Intervals.icu, such as activity ID, date/time, activity type, distance, duration, and gear.
- Bicycle details, maintenance records, inspections, discrepancies, component records, and fit configurations entered into VeloTechLog.
- Session and operational security data needed to authenticate and operate the service.
VeloTechLog does not intentionally collect payment information, precise location history beyond activity data returned by the provider, or special-category data.
3. Why we process it and legal basis
We process data to authenticate you, synchronize and display ride history, calculate mileage, maintain your technical records, secure the service, and respond to privacy requests.
The legal basis is performance of the service you request and, where applicable, legitimate interests in securing and operating the service. Where consent is required, it is obtained through the provider authorization flow and may be withdrawn by revoking authorization.
5. Retention
Account data and workspace records are retained while your account remains active or until deletion is requested, subject to legal obligations and protected backups. OAuth sessions expire according to server configuration. Deletion requests are handled without undue delay and normally within one month; complex or numerous requests may require an extension permitted by GDPR.
6. Your GDPR rights
Subject to applicable limits, you may request access, a portable copy, correction, deletion, restriction, objection, and information about automated decision-making. VeloTechLog does not make decisions based solely on automated processing that produce legal or similarly significant effects.
Use the in-app export function for a current workspace copy. For account-level export or deletion, contact the service operator using the contact details below and include the account identifier shown after login. We may verify identity before completing a request.
You may also complain to your local data protection supervisory authority.
7. Security
Access tokens are stored server-side, accounts are isolated by authenticated account key, and sessions use server-issued cookies. The operator must maintain least-privilege access, HTTPS, protected database backups, and timely security updates. No internet service can guarantee absolute security; report suspected incidents promptly.
8. International transfers
The service may involve infrastructure or provider processing outside your country. The operator must document the applicable transfer mechanism and safeguards for the actual hosting and provider arrangement. This policy does not claim a safeguard that has not been configured.
9. Changes
We update this policy when processing changes. The version and date above identify the current text.
10. Contact
Privacy, access, correction, and deletion requests should be sent to the VeloTechLog service operator through the contact channel published with this deployment. Replace this placeholder with a monitored controller email or address before treating the service as production-ready.