Firstly, I want to offer my sincere apologies for how we mishandled this. You are absolutely right: we should have done a better job communicating how this change was rolling out.
For background (and for anyone else reading): what is being referenced here is that Reclaim is, by definition, a product that can straddle two or more Google or Microsoft accounts. It can do things like block out your work calendar when your personal calendar gets busy.
The issue is: some companies have come to us and told us they will no longer approve of Reclaim's access to their calendars unless we enforce certain restrictions, such as only allowing authentication to an account that contains their calendar data (ex: Reclaim!) via their SSO provider, and no other authentication is allowed.
It isn't quite accurate that they have "taken over" your account. In fact: if you disconnect their corporate Google/Microsoft account from your Reclaim account, you are free to use it how you want. For example, their regular calendar sharing allows you to connect to your work account via your personal Google calendar, you could do that and not avoid any disruption in service. But most companies don't permit more than "free/busy" level of sharing, which isn't quite enough for this workaround.
If you need help disconnecting your company's account from your Reclaim account, we can walk you through how to do that.
We are exploring more sophisticated (but much more expensive) solutions, such as allowing you to authenticate with your non-company credential but not show you any information that is associated with your company calendar (ex: data masked). But it's unclear if your employer (and similar) would accept this. It's also still a degraded experience for the end-user, so it's tough to say if this is ultimately better or worse than the current situation.
That all said: I am sorry we didn't roll out this change to you. I hope you will give us the benefit of the doubt and consider working with us on ways to meet your employer's requirements as well as yours. You are welcome to email me directly at patrick@reclaim.ai if you'd like to discuss this further.
For background (and for anyone else reading): what is being referenced here is that Reclaim is, by definition, a product that can straddle two or more Google or Microsoft accounts. It can do things like block out your work calendar when your personal calendar gets busy.
The issue is: some companies have come to us and told us they will no longer approve of Reclaim's access to their calendars unless we enforce certain restrictions, such as only allowing authentication to an account that contains their calendar data (ex: Reclaim!) via their SSO provider, and no other authentication is allowed.
It isn't quite accurate that they have "taken over" your account. In fact: if you disconnect their corporate Google/Microsoft account from your Reclaim account, you are free to use it how you want. For example, their regular calendar sharing allows you to connect to your work account via your personal Google calendar, you could do that and not avoid any disruption in service. But most companies don't permit more than "free/busy" level of sharing, which isn't quite enough for this workaround.
If you need help disconnecting your company's account from your Reclaim account, we can walk you through how to do that.
We are exploring more sophisticated (but much more expensive) solutions, such as allowing you to authenticate with your non-company credential but not show you any information that is associated with your company calendar (ex: data masked). But it's unclear if your employer (and similar) would accept this. It's also still a degraded experience for the end-user, so it's tough to say if this is ultimately better or worse than the current situation.
That all said: I am sorry we didn't roll out this change to you. I hope you will give us the benefit of the doubt and consider working with us on ways to meet your employer's requirements as well as yours. You are welcome to email me directly at patrick@reclaim.ai if you'd like to discuss this further.