Ma Table Halal Halal registry

Privacy policy

How Ma Table Halal collects, uses and protects your personal data.

Last updated: 14 July 2026

1. Identity of the data controller

The Ma Table Halal website and application are published on a non-professional basis by a private individual, who is the data controller. Contact: hello@matablehalal.com.

2. Data collected

Ma Table Halal is designed to work without account creation, without login, without collecting any name, e-mail, address or phone number. The only data processed is that strictly necessary for the features described below.

2.1 Geographic location

The application asks for permission to access your location in two situations:

You can refuse or revoke the location permission at any time in your phone's settings. The application remains functional (browsing, filters, search by name) without geolocation.

2.2 Anonymous device identifier (UUID)

When you vote on the halal nature of a restaurant or add a restaurant to the directory, an anonymous UUID is generated and stored on your device. This identifier is sent to our servers to:

This UUID is not linked to any personal data (no e-mail, no name, no phone number). If you use neither voting nor restaurant addition, no UUID is generated or transmitted.

2.3 Search queries

When you type text in the search bar to add a restaurant, your query is relayed by our server to Google Places API to retrieve the matching results. The query is not kept on our servers beyond the duration of the response.

2.4 Server logs

2.5 Crash and diagnostic reports (Sentry)

If the mobile application crashes, a technical report is sent to Sentry GmbH (hosted in Germany) to allow us to identify and fix bugs. This report contains:

We have explicitly disabled the sending of your IP address to Sentry. No personal data (name, e-mail, location) is attached to the report.

2.6 Restaurant data

Restaurant listings come from public sources (Google Places API, halal certification registries such as ACHAHADA and AVS). No personal data of third parties (customers, restaurant employees) is processed.

2.7 Sworn declaration by a restaurant owner

When an owner signs a halal sworn declaration from the mobile application (see article 5 of the Terms of Use), the following information is collected and kept in order to identify the author of the declaration and make it publishable:

The full text of the declaration, together with the owner's identity, the company name, the SIRET, the list of suppliers and any attached certificate, is made public on the corresponding certificate page (URL matablehalal.com/declarations/MTH-…) and shown on the restaurant's listing. The owner is explicitly informed of this and consents to it at the time of signing (checkbox in the application's form).

The technical audit information (IP, UUID, user-agent), on the other hand, is never published: it is accessible only to the publisher, and where applicable to a judicial authority that requests it in accordance with the law.

2.8 Anonymous audience measurement (Plausible)

We use Plausible Analytics, an anonymous audience measurement tool self-hosted on our European infrastructure (Hetzner, European Union). No cookie is set, no data is transferred to a third party, and collection is strictly limited to aggregated statistics. This configuration complies with the consent exemption provided by article 82 of the French Data Protection Act (loi Informatique et Libertés) and by CNIL deliberation no. 2020-091 on strictly anonymous audience measurement.

For the technical detail of how Plausible works, see their data policy.

3. Legal basis

The processing relies on:

4. Recipients (processors and third parties)

Your data is never sold or transferred for commercial purposes. The recipients are:

5. Retention period

6. Your rights

In accordance with the GDPR and the French Data Protection Act, you have a right of access, rectification, erasure, restriction and objection.

You can also lodge a complaint with the CNIL (cnil.fr).

7. Security

Communications between your device and our servers are encrypted (HTTPS / TLS 1.2 minimum). Requests to Google Places API and OpenStreetMap tiles also use HTTPS.

8. Changes

This policy may be updated. The date of last update appears at the top of this page.