Privacy Policy

Effective date: May 15, 2026  ·  Applies to: Carspel mobile applications, related web experiences where offered, and this marketing website (carspel.ca / linked domains).

We are committed to protecting the privacy and security of your personal information. We collect, use, and process your data lawfully, transparently, and only for legitimate purposes related to operating Carspel. We do not sell your personal information and share it only as necessary to provide our services, while supporting your rights to access, correct, or delete your data.

Agreement when you use Carspel. By installing Carspel from an app store, creating an account, or continuing to use our mobile apps or related web services, you confirm that you have read this Privacy Policy and agree to the general privacy practices described here. If you do not agree, do not install or use Carspel. Where mandatory local law provides you additional rights or requires different disclosures, those rights apply to you as described in the regional sections below; nothing in this global Policy is intended to limit non-waivable protections.

This Privacy Policy describes how Carspel (“Carspel,” “we,” “us,” or “our”) collects, uses, discloses, and protects personal information. Carspel is developed by FundaMedia. Where laws such as the EU and UK GDPR or California privacy laws apply, supplemental disclosures appear below.

This Policy is not legal advice. Please review it alongside your product roadmap (billing, analytics toggles, optional AI/redaction workflows). Update disclosures whenever vendors or processing materially change.

1. Who is responsible?

For privacy inquiries and requests described in this Policy:

If we designate an EU/UK representative or US postal address for privacy notices in the future, we will publish it here.

2. Scope

This Policy applies when you:

Third-party websites or stores (for example Google Play) have their own policies for checkout flows they operate. Where purchases occur via Google Play billing or similar platforms, payment validation may be handled by the store, subject to its policies.

3. Categories of information we collect

Depending on how you use Carspel, we may collect or receive:

3.1 Account and identity information

3.2 Vehicle and operational records

3.3 Photos, videos, audio, documents

3.4 Derived safety / recall context

3.5 Payments and subscriptions

3.6 Communications and diagnostics

3.7 Marketing website usage data

3.8 Optional cloud-assisted receipt/document workflows

Where Carspel offers optional sanitization/redaction or analysis that sends user-selected documents through managed cloud infrastructure (for example documented Cloud Run workflows referencing Google Gemini), those documents are processed transiently for the stated purpose (such as detecting sensitive regions before display/storage). Such processing occurs only when you explicitly invoke the feature where implemented.

4. Sources

5. Why we use information (purposes)

6. Legal bases (EEA/UK/Switzerland)

Where GDPR-like laws apply, we rely on appropriate lawful bases such as:

You may withdraw consent where processing is consent-based without affecting prior lawful processing.

7. How we share information

We disclose personal information only as described below:

We do not sell personal information for money as traditionally understood under California law, and we do not “share” personal information for cross-context behavioral advertising unless we explicitly notify you and offer applicable controls.

8. International transfers

We operate primarily from Canada with processors that may store or process data in the United States or other regions. Where GDPR/UK GDPR applies, we implement appropriate safeguards such as Standard Contractual Clauses or other mechanisms recognized by regulators, supplemented by technical and organizational measures.

9. Retention

We retain personal information only as long as necessary for the purposes above, including legal, accounting, or reporting requirements. Vehicle logs or attachments remain until you delete them or delete your account subject to backup/cache latency and lawful holds. Diagnostics retention follows vendor/project configuration (review your Sentry organization retention).

10. Security

We implement administrative, technical, and organizational safeguards appropriate to risk—including TLS for data in transit and least-privilege access patterns enforced via backend policies where engineered (for example Row Level Security concepts highlighted in internal engineering docs). No online service is perfectly secure; please protect your credentials.

11. Your privacy rights

Deleting your account and associated data

To delete your Carspel account and the data tied to it:

Deletion removes your account profile and associated data we control, subject to brief backup or cache latency, lawful retention requirements, and other exceptions noted in this Policy. For step-by-step instructions (including deleting specific data without closing your account), see our data deletion request page.

11.1 EEA, UK, Switzerland

You may request:

Contact hello@carspel.ca. We respond within timelines required by applicable law (typically within one month for GDPR requests, subject to extensions).

11.2 California residents (CPRA)

California residents may exercise rights under the California Consumer Privacy Act as amended (“CCPA/CPRA”), including:

Submit requests via hello@carspel.ca. We verify requests commensurate with risk (typically confirming control of your email/account). Authorized agents may submit requests with appropriate proof.

11.3 CPRA metrics

If legally required to publish annual metrics covering consumer requests, we will host them here or link from this section.

12. Children

Carspel is intended for adults managing household vehicles. We do not knowingly collect personal information from children under 13 (or higher age where required). If you believe a child provided information, contact us so we can delete it.

13. Automated decision-making

We do not perform automated decisions producing legal or similarly significant effects under GDPR Article 22 unless we introduce such features with separate transparency.

14. Changes

We may update this Policy by posting a revised version with a new effective date. Material changes may require additional notice where mandated.