# Providing Trusted Data Sign your content and avoid sending unnecessary or inaccurate information. ## Discussion To avoid cluttering the user’s calendar, use [`Siri Event Suggestions Markup`](/documentation/SiriEventSuggestionsMarkup) only for events that the user has booked. The system also protects the integrity of reservation data by employing security measures to ensure that no one can impersonate your domain to put events on the user’s calendar. ### Provide Reliable Events in Webpages Only provide markup with a [`reservationStatus`](/documentation/SiriEventSuggestionsMarkup/reservationStatus) of `ReservationConfirmed` on a webpage that includes a confirmed reservation. For example, a page that prompts the user to select their seat before your service finalizes the transaction should use a different `reservationStatus` or not include markup at all. Similarly, a promotional page that advertises a booking the user could make shouldn’t include markup with a `reservationStatus` of `ReservationConfirmed`. Use HTTPS for connections to your service so that Siri can provide trusted information to the user. ### Provide Reliable Events in Emails Provide markup with an accurate [`reservationStatus`](/documentation/SiriEventSuggestionsMarkup/reservationStatus) in emails confirming, updating, or canceling a reservation. Don’t provide reservation markup in other emails from your service, such as advertisements. Your reservation emails must comply with these security measures: - Provide a static email address in the From field of the email. - Sign your emails with DKIM. The DKIM key must be at least 1024 bits and hashed with SHA-256. - Ensure the top-level domain hosting the public key used for the DKIM signature matches the top-level domain of the email address in the From field of the email. --- Copyright © 2026 Apple Inc. All rights reserved. | [Terms of Use](https://www.apple.com/legal/internet-services/terms/site.html) | [Privacy Policy](https://www.apple.com/privacy/privacy-policy)