Calendar invites
The service that sends the invitation for every meeting on the calendar, as mail that genuinely comes from this domain.
What it does
It watches Marco Ferra's Google Calendar for events that are new or changed, and sends each attendee the invitation as a standard iCalendar message fromhello@marcoferra.com. Every meeting is covered, however it was made: through this site, through cal.com, through Calendly, or by hand in the calendar.
Why it exists
Google sends calendar invitations signed as googlemail.com, which does not align with this domain and so fails its strict DMARC policy. Mail that fails is rejected rather than delivered. This service is the single aligned path an invitation takes, so invitations arrive instead of disappearing.
Google data it uses
Read-only access to the calendar owner's own calendar, and nothing else. It lists events, subscribes to change notifications, and cancels that subscription when it is no longer needed. It cannot create, edit or delete anything in the calendar, and it reads no contacts and no mail.
Where it runs
A Rust service on Google Cloud Run. Sync state lives in Firestore, the Google refresh token in Secret Manager, and the mail itself leaves through this domain's own SMTP provider. Attendee addresses are used to address the invitation and for nothing else.
What is kept
Only what a resumable sync needs: the calendar's sync position and the identifiers of events already sent, so an invitation is not sent twice. No message bodies are retained, and there is no mailing list.
Use of Google user data
Use of information received from Google APIs adheres to theGoogle API Services User Data Policy, including its Limited Use requirements. Calendar data is used only to send the invitation for the meeting it describes. It is not sold, not used for advertising, and not shared.
Full detail is in theprivacy policyand theterms of service. Questions go tohello@marcoferra.com.