Notre site utilise des informations liéss à la connection pour assurer son fonctionnement :
Joomla Core Capabilities
All requests to a Joomla website start a session which stores the IP address in the session data and creates a session cookie in the user's browser. The IP address is used as a security measure to help protect against potential session hijacking attacks and this information is deleted once the session has expired and its data purged. The session cookie's name is based on a randomly generated hash and therefore does not have a constant identifier. The session cookie is destroyed once the session has expired or the user has exited their browser.
Joomla's logging system records the IP address of the visitor which led to a message being written to its log files. These log files are used to record various activity on a Joomla site, including information related to core updates, invalid login attempts, unhandled errors, and development information such as the use of deprecated APIs. The format of these log files may be customised by any extension which configures a logger, therefore you are encouraged to download and review the log files for your website which may be found at `/var/www/vev/logs`.
When a network connection is available, a Joomla installation will attempt to communicate with the joomla.org servers for various capabilities, to include:
Checking for updates for the Joomla application
Help screens for core Joomla extensions
The Install from Web service (opt-in)
The statistics collection server (opt-in)
As with all HTTP requests, the IP address of your server will be transmitted as part of the request. For information on how Joomla processes data on its servers, please review our privacy policy.
Authentification - Cookie
In conjunction with a plugin which supports a "Remember Me" feature, such as the "System - Remember Me" plugin, this plugin creates a cookie on the user's client if a "Remember Me" checkbox is selected when logging into the website. This cookie can be identified with the prefix `joomla_remember_me` and is used to automatically log users into the website when they visit and are not already logged in.
CAPTCHA - reCAPTCHA
The reCAPTCHA plugin integrates with Google's reCAPTCHA system as a spam protection service. As part of this service, the IP address of the user answering the captcha challenge is transmitted to Google.
Event Gallery
Cookies: No additional cookies are set. For session handling Event Gallery uses the session handling of Joomla!.
Google Photos:
Serving images from Google Photos will make users load content from Google servers.
Managing Google Photos in the Event Gallery backend will call Google services as well. Your backend users data will be used to call those services like the Album Selector.
Picasa Photos:
Serving images from Google Photos will make users load content from Google servers.
Managing Google Photos in the Event Gallery backend will call Google services as well. Your backend users data will be used to call those services like the Album Selector. If you use private albums, a Google Auth Token is necessary. To create this token, your browser will use Google services as well as calling www.svenbluege.de. To fetch album data with that Google Auth Token, a connection to www.svenbluege.de is made as well. That is necessary to obtain an temporary additional access token for Google Photos.
Flickr: Serving images from Flickr will make users load data from an external service. Furthermore will your server communicate with Flickr services. This communication does not involve data of your users.
S3 Serving images from Amazon S3 will make users load data from an external service. Furthermore, your server will communicate with the Amazon S3 service. This communication does not involve data of your users.
Checkout
Before a user can create an order, he collects items in his cart. During the checkout, this cart gets completed with address data. After submitting the order, the order gets created as a copy of the cart. Besides the item information, address data of the customer as saved. The amount of data depends on the components configuration.
Address data exists in three places: cart, order and the Joomla! user object. While this can't be changed for the cart and the order, you can configure that the user object is not used for storing data in the components options.
For some payment methods, external services are used. Event Gallery does not store direct payment data. Instead a generated token is used to identify the transaction created by the external payment provider.
The back end of Event Gallery allows clearing carts which are older than 30 days by clicking a simple link.
Payment // Stripe: To initiate a payment, Event Gallery submits the email address and the order-id to Stripe. The Stripe-UI in the checkout will include JS/CSS in your website. This includes the transfer of the IP and cookies.
Payment // PayPal: To create a Paypal transaction, Event Gallery needs to transfer the orderid to Paypal. The payment process will redirect your customer to Paypal so they are able to collect user data.
Payment // Braintree: To create a Braintree transaction, no user data is transfered to Braintree. The transaction is handled on your server. The braintree UI will include JS/CSS in your website. This includes the transfer of the IP and cookies.
Social Sharing: Event Gallery only uses passive sharing options. It is up to the user of the front end to trigger the sharing options of the different services. There are no JavaScript SDKs in place which transmit data before any interaction.,
Logs: Event Gallery writes some log files. They contain the IP-adress of the website user. In addition to processing tasks like for Google Photos/Flicker/Amazon S3 it writes logs for payment transactions. You can find those logfiles in your log folder. They contain user data and need to be handled with care.
YouTube: To provide an easy start and some help, the backend embeds some Youtube videos.
Kunena
Adresse de courriel.
Adresse IP : Si l'option de configuration est réglée sur Oui l'adresse IP sera stockée sur le site web.
Toutes les informations du profil de l'utilisateur sont stockées dans la base de données.
Tous les messages des utilisateurs sont stockés dans la base de données.
Les résultats de l'évaluation de l'utilisateur sont stockés dans la base de données.
Les statistiques des utilisateurs peuvent être affichées sur le forum.
Les préférences de l'utilisateur sont enregistrées dans le cookie. Exemple : Masquer les annonces, filtrer par, session de connexion utilisateur.
Coté administration :
Journal d'erreurs utilisateur.
Journaux des actions de l'utilisateur. (Lorsqu'elle est activée lors de la configuration)
JS Socials (option du template : partage social) collecte et envoie des données aux plateformes des réseaux sociaux. (L'utilisateur peut également désactiver cette fonction dans les paramètres du forum)
Privacy
In order to process information requests, information about the user must be collected and logged for the purposes of retaining an audit log. The request system is based on an individual's email address which will be used to link the request to an existing site user if able.
Vercors Envol
Club de parapente du Vercors