Privacy and Cookies

1. Who we are and the site's purpose

aggiornati.ch è un’agenda di formazione e incontri rivolta ai professionisti della salute, gestita da SSMIG-TI — Società Svizzera di Medicina Interna Generale del Canton Ticino, la stessa associazione che gestisce amiti-med.ch. Medici e organizzatori possono proporre corsi, congressi e altri appuntamenti. La redazione li valuta prima della pubblicazione, per informare altri professionisti.

We process data to provide the calendar, receive and assess submissions, communicate their outcome, publish event information and protect the service against abuse.

2. Controller identity and contact details

The data controller is the association SSMIG-TI — Società Svizzera di Medicina Interna Generale del Canton Ticino.

The contact person handles the association's data-related requests; they do not replace the association as controller.

The association is still confirming these initial contact details.

3. Technical data collected while browsing

To deliver pages and maintain security, the server receives connection data including IP address, date and time, requested address and information sent by the browser. The hosting service may record these in technical logs according to its service settings.

The application records errors with a date, technical code and request identifier. To limit form and login abuse, it stores counters linked to identifiers derived using a private key from the IP address and, for the form, the email address. These identifiers are not the plain addresses, but do not guarantee anonymity.

This site's code does not integrate analytics, behavioural advertising or visitor profiling tools. This does not exclude the technical processing by hosting and antispam services described below.

4. Data received through Suggest an event

The form requires the sender's name and email, event title and description, dates and times; it may receive an image and PDFs. It also records a submission reference, receipt date, review state and link to any event created. It uses a session and technical identifiers to handle submissions and temporary attachments, prevent duplicates and verify antispam checks.

Sender contacts are stored separately from event content and are accessible to authorized editors. Do not include patient data or other personal health information in text or attachments. Anyone submitting an event must be entitled to communicate the data of other people mentioned.

5. Reviewing and publishing submissions

Editors may accept, change or reject a submission. Sending it does not automatically publish it. Approved revisions become public only when the site owner authorizes activation.

Approved information may appear in event pages, lists, calendars, RSS feeds, search results and public attachments, and may be indexed or copied by third parties. Names and emails entered in the private sender fields are not published as such; data in text, images or PDFs may become part of published material.

When email delivery is enabled, operational notifications are sent to editors and possibly a confirmation to the sender. Application notifications contain submission references, without repeating text or attachments. Any subsequent correspondence is processed to handle the request.

6. Technical cookies and administrative sessions

The application uses the session cookie __Host-colbe_session for administrative login and public form functions, including request protection, receipts and attachment handling. Ordinary calendar pages do not start this session themselves. An existing cookie may still be sent by the browser with requests to the same site.

The application does not set a persistent expiry for this session cookie; browser rules apply. The application session expires after 30 minutes of inactivity or at most 8 hours; technical files are not necessarily deleted at that exact moment. In HTTPS the cookie uses Secure, HttpOnly and SameSite=Lax. The text editor may use local technical memory or preferences for its functions.

We do not use application cookies for marketing or visitor statistics. No consent banner is displayed for the necessary technologies described here. You can block or delete cookies in your browser settings; the form and administration login may then work incorrectly.

7. Cloudflare Turnstile

The form may use Cloudflare Turnstile, provided by Cloudflare, Inc., United States, to distinguish people from automated submissions. When enabled, it loads on the form, not on ordinary calendar pages. Cloudflare receives signals such as IP address, connection and browser characteristics and site origin. The server verifies the token with Cloudflare; it does not send the sender's name, email, submission text or attachments to that service.

Cloudflare states that it also processes signals to improve bot detection, acting as an independent controller for that purpose. Data may be processed in the United States and other countries in its network. Provider statements on processing, transfers and safeguards are described in the Turnstile privacy notice and the Cloudflare privacy policy. The application does not determine the provider's retention periods.

Turnstile normally produces a token; the potential technical cookie cf_clearance depends on enabling pre-clearance or other Cloudflare protections. This site's code does not set it. It is therefore incorrect to assume Turnstile does not process data or cannot use cookies.

8. Hosting and security

Hosting is provided by cyon GmbH, Switzerland. The association also uses technical services necessary to operate the site and, if enabled, the email transport configured for notifications. For the hosting provider's processing, see Cyon data protection information.

The software distinguishes owner and editor access, protects form requests, checks uploaded files and keeps unpublished drafts and attachments private. These measures reduce risks; they do not guarantee absolute security. Hosting location does not imply all processing, including email and Turnstile, occurs exclusively in Switzerland.

9. Data retention

• Sender contacts: after acceptance or rejection of a submission, an expiry is set after 30 days. Deletion occurs in batches at the next maintenance run. For pending submissions, this expiry has not yet been set.
• Unlinked temporary attachments: may be removed by maintenance after 24 hours if not linked to submissions or revisions. Rejected submission attachments that remain linked are not automatically deleted by this rule.
• Submissions, events and history: content, revisions, linked attachments, operation records and published versions have no general automatic deletion deadline in the software. Withdrawal from the site or removal from active management does not delete history or retained copies. The association must reassess the need to retain them, including on the data subject's request.
• Logs, backups and correspondence: retention depends on the operational rules of the association and services involved; expiry of database contacts does not delete these copies. No single duration is promised that the software does not enforce.

10. External links

Links to organizers, registration and other sites lead to third-party services. Their notices and terms apply when following them. A link does not transfer management of those services to the association. Recipients of published material may also retain copies outside our control.

11. Data subject rights

You can contact the association using the details above to ask whether it processes your data, request access or corrections and, within applicable law, request deletion or cessation of processing. We may need to verify your identity and consider legal obligations or legitimate retention interests. Public withdrawal cannot guarantee removal of third-party copies.

For information on rights and reporting options, contact the Federal Data Protection and Information Commissioner (FDPIC). For Cloudflare's processing as an independent controller, you can also use the contacts in its privacy notice.

12. Updates to this notice

This page may be updated when the service, contacts or processing change. The date at the top identifies the last update of published text or contacts. Changes become visible when the new site version is published. Please consult this notice when sending a new submission.