[Q] [Q, APP] obfuscate calendar data topic

gday folks

intro

i'm planning an app that will hide valid/ private calendar data within a larger body of fake data, such that any calendar u.i could be used to view & edit these data, and any of the standard android synch tools would also function as expected

the design would work in such a way that any copy of the calendar data could be de-obfuscated by any implementation of the algo combined with the shared secret

this must work without root, and would be nice to appear to the casual observer as a valid calendar


tech. specific

my limited understanding is that a custom calendar provider would act as a suitable intermediary between the stored data and the de-obfuscated data that should be displayed in the (/ any) calendar u.i.

android api: calendar-provider

• i envisage a bunch of patsi... err, notable people's names could also be scraped from wikipedia on a per-key basis which maybe a grand datasource for 'attendees'


• phone numbers could be scrambled to uselessness if the data model's allowance for string length isn't too restrictive


• times could be stretched and skewed


• the number of events could be increased by a factor of 3 or more to give enough junk data without raising any eyebrows, or imposing too excessively on synch adaptors or service providers

wikipedia: steganography

please share any thoughts you might have, from the thoughts on using 'calendar provider', to the security, to any existing functionality like this or even just answer the poll!