01 / Privacy contact
CamPro is responsible for the personal data processing described in this policy. For privacy, access, deletion or security requests, contact help@campro.ai.
This policy covers CamPro services. Payment providers, vehicle manufacturers, operating systems and linked websites apply their own policies to information you provide directly to them.
02 / Visiting this website
This public website needs no account or login. It does not request location, camera or contacts permissions and does not use advertising trackers, third-party analytics, marketing cookies or cross-site profiling. Images, icons and scripts are served with the site. Servers receive the IP address, request path, time, browser information and error records needed to deliver pages and address security or availability issues.
Email links open your own mail client. Messages you actually send are handled by the relevant mail services. We do not collect form submissions or automatically subscribe visitors to marketing. Any future optional analytics or marketing tools will be disclosed with choices as required.
03 / App data and purposes
| Category | Data and purpose |
|---|---|
| Account and devices | Email, verification and sessions, device/vehicle identifiers, model, software version, association and authorization status: login, security, vehicle ownership and feature access. |
| Subscription and payments | Plan, amount, currency, billing country, quotes, order/provider references, renewal, cancellation and refund status: delivery, reconciliation, support and legal obligations. Full card numbers and security codes do not enter CamPro servers. |
| Camera and media | Views, recordings, event times and snapshots: enabled driving views, recording, parking monitoring, clips and remote preview. Footage can contain people, number plates and surroundings. Originals primarily stay on your head unit. Cloud event mode uploads event details and snapshots; requested clips are transferred on demand, rather than all original footage continuously. |
| Optional location | Location needed for a feature you actively enable and authorize. If regional offers become available, precision, upload scope and retention are explained when requested. Installation and standard-price purchases do not require location. |
| Support and diagnostics | Submitted issues, replies, screenshots, attachments, app logs, version and device diagnostics: investigation and support. Remote diagnostics follow in-app authorization, stop controls and execution limits. |
| Help conversations | Questions you submit, necessary conversation context and related help material: generated help responses. Authorized support analysis can use relevant issue and diagnostic material. |
| Operations and security | Request times, IP, connection and error details, authorization and administrative actions: maintenance, troubleshooting, abuse prevention and auditing. |
Only submit information you are authorized to provide. Avoid unrelated personal information, login codes, full card numbers and other unnecessary sensitive material.
04 / Location, offers and data contribution
Browsing the website, installing the app, signing in and buying at the public standard price do not require device location. We do not collect driving locations just because you install the app or prepare to pay. The three standard USD plans are public and remain available without location.
Regional offers are not available yet. If a “Get regional offers” option is introduced, it will explain the purpose and request location only after you choose it. Approximate location will be preferred where sufficient to determine country. System results may contain coordinates, accuracy and capture time; any fields sent to the server will be disclosed before the request. Location will be used for the country and offer-eligibility check, not a continuous trip history. Any retained eligibility results and their retention period will be disclosed. Failed, refused or withdrawn location access leaves standard prices available.
New location features, such as traffic-light prediction, will disclose purposes, foreground/background collection, upload scope and retention before activation. Uploading observations for training or data contribution will have a separate switch, off by default, with its data, recipients, retention and withdrawal process explained. Location permission is not consent to contribution or training. These unreleased features are not sold as delivered subscription benefits.
You can withdraw location permissions in Android settings and contact support to access or delete relevant data or withdraw related consent.
05 / Processing grounds and choices
Where applicable law permits, account access, vehicle association, subscription delivery and media you request are processed to perform the contract or provide the requested service. Necessary accounting, tax and lawful regulatory requirements are based on legal obligations. Security and troubleshooting may rely on legitimate interests while considering your rights. Sensitive device permissions and processing requiring separate consent require the corresponding authorization; a system permission does not authorize every future use.
You can stop using features, withdraw permissions, object or request restrictions where applicable. Withdrawal does not affect processing lawfully completed before withdrawal. We do not sell personal data or use it for cross-site targeted advertising. Your private recordings and location observations will not be used for training organized by us without separate, explicit consent.
07 / Storage and retention
| Data | Production retention rules |
|---|---|
| Local recordings and exports | Kept on your devices according to capacity, loop settings and deletion choices. Uninstalling or clearing data may affect local files. Save important footage yourself. |
| Cloud events and snapshots | Up to 7 days, also subject to capacity limits of 512 events per device. Capacity, deletion or ownership changes can make them unavailable earlier. |
| Requested cloud clips | Up to 24 hours after completion, deleted earlier after the phone confirms durable saving. |
| Optional location | No trip history is created for installation or standard-price purchase. Regional offers, new location features and contribution will each disclose fields, storage and periods before availability. Location no longer necessary for its purpose is deleted. |
| Account and non-financial data | Used while the account is active. Unnecessary data is deleted or anonymized within 30 days after verified account closure. Cancelling renewal does not close the account. |
| Support tickets and attachments | Ticket text and replies: 180 days after closure. Diagnostic attachments: deleted within 30 days after closure. Material needed for unresolved disputes or legal retention is held separately with restricted use. |
| Help and general logs | Help conversations, access and general diagnostic logs: 30 days, then deleted or anonymized. |
| Security audit | 180 days. Records of confirmed incidents may be held until investigation and related disputes finish. |
| Payments and refunds | As required by applicable tax, accounting, payment-provider and dispute obligations; deleted or anonymized after the required period. Only necessary records are retained. |
| Backups | Restricted backups roll over on a 30-day cycle. Confirmed deletion requests are reapplied after restoration. Legally retained records have restricted access and purpose. |
These rules apply from the production launch. Permission withdrawal, subscription cancellation and data deletion are separate actions. Export files before requesting deletion. If a legal requirement or dispute prevents deletion, we explain the category, reason and handling.
08 / Security
Cloud APIs use HTTPS/TLS, account and device authentication, vehicle-ownership checks and access restrictions. Sensitive configuration has restricted access, and media access depends on account authorization and entitlement. Do not send login codes, passwords or payment security codes in support messages.
If a security incident affects personal information, we contain, investigate and remediate it and notify affected people and authorities under the applicable conditions and deadlines. Where the GDPR supervisory reporting rule applies, its 72-hour requirement is followed.
09 / Your rights and requests
Depending on applicable law, you can request information, access and a copy, correction, deletion, restriction, portability, objection and withdrawal of consent. You may complain to an appropriate data-protection authority. We do not discriminate against you for exercising lawful rights.
Send requests from your registered email to help@campro.ai, describing the action and relevant vehicle or order identifiers. Additional sensitive identity documents are requested only when necessary. We normally respond within 30 calendar days, or the shorter period required by law. If a permitted extension is needed, we explain the reason and timing. Verification, legal retention and other people's rights may limit requests.
Android permissions can be withdrawn in system settings. Before account closure, cancel renewal and save footage; we can help identify still-renewing subscriptions.
10 / Age, notices and changes
CamPro is for people aged 18 or older who are authorized to use the vehicle. It is not directed to children. Contact us about unauthorized collection from a minor. Recordings may incidentally contain others, and users must lawfully control recording and sharing.
We do not currently run profile-based marketing email subscriptions. Verification, billing, security and support communications are necessary service messages. Future optional marketing, data contribution and new location purposes will be separately explained with appropriate choices.
Material policy changes will be notified at least 14 days ahead on the website, in the app or by registered email. New processing that requires consent will not rely solely on a policy update or continued use. Historical versions are kept in site maintenance records. The update date appears above.