Featere request/offer: anonymisation to target

[viegelinsch]

Hi @ridafkih,

thank you for this project.
I have a use case currently not addressed: As user I want to synchronise my calendar to any supported target but the appointments must be anonymised so I can use public cloud services.

Context:
I work for an organisation which needs to keep some of there information private but would like to use specific public cloud services mainly for appointment booking. Currently that means, that we need to open our calendars to that respective cloud services with full read access. For internal and legal reasons - greetings from EU GDPR - that is a show stopper for using such public cloud services.

Intended solution:
Keep the uuid, timezone, times, ... of each event but anonymise summary, description, tags, ....
On recurring synchronisation the uuid is the central identifier whether the event has to be updated, delete or left alone.

Question to @ridafkih - would you accept such a contribution, well specified, tested, you set the rules, or is this too far out of your scope so you would rather not see that contribution.
And yes, I would develop that contribution by myself. My goal would be a contribution, tested and ready to merge until end of 2026 (hopefully earlier but you never know).

Any feedback, might it also be a rejection, welcome.

[ridafkih]

EDIT: @viegelinsch Yes, this looks fine! Feel free to implement this, if you want to configure destinations to be able to obfuscate or modify incoming event details, that sounds like a great feature to implement!

Feel free to use AI, just remember to keep code standards the same, do not let the AI use type assertions, and use arktype for validation. If you're modifying the UI, remember to use the composition pattern established throughout the codebase and try not to introduce redundant functions. 🫡 For migrations, ensure the AI does not attempt to manually create them by modifying the files in the @keeper.sh/database package - use the CLI!