This Privacy Policy defines and informs you of how Mr. Pascal BEN BIHI uses and protects the information you transmit, if any, when you use this website accessible from the following URL: https://icodeplugins.com.
1. Data Controller The controller for personal data is Mr. Pascal BEN BIHI, Sole Proprietor, residing at 10 RUE de la Barre, 66000 Perpignan. The Editor is committed to compliance with the General Data Protection Regulation (GDPR) and the French Data Protection Act (Loi Informatique et Libertés).
2. Collection of Personal Data When using the site, creating a customer account, or making a purchase, the following data may be collected:
- Last name and first name.
- Email address.
- Billing address.
- Connection data.
3. Purposes of Processing Data processing is necessary for the following purposes:
- Management and tracking of orders.
- Delivery of WordPress plugins.
- Access to technical customer support.
- Sending newsletters, subject to your express and prior consent.
4. User Rights In accordance with European regulations, you have the following rights regarding your personal data:
- Right of access and communication: You can access the data concerning you.
- Right to rectification: You can request the update or correction of your data.
- Right to erasure (right to be forgotten): You can request the deletion of your personal data.
- Right to restriction of processing: You can request to temporarily freeze the use of some of your data.
To exercise these rights, you can contact the Editor by sending a message with the contact form on the contact page.
5. Cookie Policy A “cookie” is a small information file sent to the User’s browser and stored within the User’s terminal. It allows the site to remember information about your navigation.
List of cookies used:
- Technical cookies: Essential for managing the shopping cart, maintaining the connection to the customer account, and secure navigation.
- Payment cookies: Deployed by third-party providers (e.g., Stripe or PayPal) to secure and validate financial transactions.
- Audience measurement cookies: Used to obtain anonymous traffic statistics to improve the user experience.
Browser Configuration: You can configure your browser software so that cookies are stored in your terminal or, conversely, that they are rejected. Note that disabling technical cookies may affect your ability to use the site’s purchasing features.
NotifReach managed notification service: Site owners who install the NotifReach plugin may choose a “managed” connection method. When they do, and only then, their site sends us the notifications it wants delivered and we pass them to Firebase Cloud Messaging on their behalf, using our own Google account. In that arrangement we act as a processor for the site owner, who remains the controller of their subscribers’ data.
What their site sends us, and when: the site address and the administrator’s email address when a licence is requested; the site address and the licence key when the site connects; and, for each notification sent, the message content (title, body, icon, image and link URLs, action buttons) together with the recipient’s Firebase device token. No other subscriber data reaches us — no email address, phone number, name or location of any subscriber. Device tokens are technical identifiers issued by the browser; they are used to route that one notification and are not used to profile anyone, enriched, or shared with third parties other than Firebase for delivery.
We keep the site address, the licence key, a hashed access token and a send counter for as long as the licence is active, in order to operate the service and enforce its limits. Notification content is not stored: it is forwarded and discarded. A site owner can disconnect at any time from their own WordPress admin, which stops all of this; a site that never selects the managed method never contacts us at all.
Google API access: To send web push notifications via Firebase Cloud Messaging, the service requests the Google https://www.googleapis.com/auth/firebase.messaging scope and securely stores OAuth tokens. It does not access any other Google account data (Gmail, Drive, Contacts, Calendar). The service’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.