Ctrlavana

Privacy Policy

How Ctrlavana collects, stores, and protects user information.

Last updated: September 16, 2024

1. Information we collect

Ctrlavana collects information that is essential for the app to function properly and provide the best possible experience.

1.1 Third-party information

  • Information provided by external tools to improve our services.
  • Integration with communication APIs such as WhatsApp and email to make it easier to contact passengers.
  • Use of analytics tools to monitor app performance.

1.2 Information you provide

The data you provide to create caravans, locations, and passengers is used so Ctrlavana can organize your trips efficiently. This data is not sent to any service or server and remains stored locally on your device.

2. What personal information we collect and how we collect it

The data we collect includes:

  • Passenger personal information such as name, email, and phone number that you add in the app.
  • Trip information, including origin, destination, and notes related to your caravans.

This data is used exclusively to help you manage excursions and keep all the necessary information organized. It is not sent to any service or server.

2.1 Third parties we collect information from

Some information is collected by third parties, such as Google Crashlytics, which helps monitor crashes and improve the user experience.

Third partyPurpose
Google CrashlyticsCrash monitoring and app performance improvements

3. Your rights as a data subject

As a data subject, you have the right to:

  1. Access the information collected about you.
  2. Request deletion or modification of information stored in the app.
  3. Ensure your personal information is not shared with third parties without your consent.

Ctrlavana is committed to respecting all data subject rights established by applicable law.

4. How we store and protect collected information

Information collected by Ctrlavana is stored locally on the user's device. This means the data stays under your control and is never sent to external servers, except crash information used for performance improvements.

We apply reasonable security practices to reduce the risk of unauthorized access.