Last updated: September 22, 2026
Censouk is a household calendar-sync service operated by Sardeis LLC. This policy explains how we access, use, store, and share information when you use censouk.com. For privacy questions or requests, contact [email protected].
We store your email address, display name, password hash, verification and account-security settings, household membership and role, and invitations. We use this information to authenticate you, manage household access, protect accounts, and send requested or service-related messages.
When you connect Google Calendar, Google asks you to authorize access. Censouk receives your Google account identifier and email address, calendar identifiers and metadata, and calendar-event data needed for the display and sync features you select. Event data can include titles, times, time zones, descriptions, locations, recurrence information, availability, visibility, attachment links, and other metadata returned by the provider.
We use this access to list calendars, read source events, show calendar information, and create, update, or remove Censouk mirror events in the destinations you choose. We also use encrypted OAuth tokens to maintain the connection and obtain new access tokens while authorization remains valid. Connecting Google Calendar does not give Censouk your Google password.
ICS/webcal source feeds are processed for the same calendar-sync purpose. A private feed URL can act as an access credential; do not share it with people who should not see that calendar.
Each policy reads its source calendar and writes its destination calendar. A calendar can have a different role in another policy. Depending on your settings, destination copies may include event details or a limited availability placeholder. We store connection metadata, policy settings, event identifiers and fingerprints, sync state, and operational logs to recognize mirror events, avoid duplicate copies, and investigate failures.
You control which calendars are connected and where copies are sent. A destination calendar's own sharing permissions determine who can see those copies. Only sync information you are authorized to share, including information about other people in your events.
Censouk's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We do not sell Google user data, use it for advertising, or use it to train generalized artificial-intelligence or machine-learning models. We use it to provide and improve the user-facing calendar-sync features you authorize. Human access to Google user data is limited to circumstances allowed by that policy, such as your affirmative permission for support, security investigations, or legal requirements.
Stripe handles Checkout and the Customer Portal. Stripe collects payment-method, billing-address, and tax information on its hosted pages. Censouk stores customer and subscription identifiers, subscription status, renewal dates, and cancellation state. We do not receive or store full payment-card numbers. Stripe's own privacy policy also applies to information you provide to Stripe.
We do not sell personal information.
We operate the application on Sardeis-managed infrastructure and use Cloudflare for website delivery and connectivity, Amazon SES for service email, and Stripe for payments. Connected calendar providers receive the requests and destination copies needed for your selected policies. These providers process information needed for their respective services; for example, email delivery requires a recipient address and message, while network delivery processes request and connection information.
We may also disclose information when required by law or when necessary to protect users, investigate abuse, or secure the service. Access and transfers of Google user data remain subject to the Limited Use commitments above. Information may be processed where we and our service providers operate, including the United States.
We use cookies and related request tokens for login sessions, security, and application operation. Censouk does not use calendar data for advertising. Operational records can include timestamps, request information, provider identifiers, error messages, and sync counts.
Passwords are hashed, provider credentials are encrypted at rest, and public website connections use HTTPS. Secret values are not displayed in the service-wide administration pages. Access to deployment secrets, operational data, and backups is restricted to authorized operators. No system can guarantee absolute security; please keep your account credentials secure and use the available multi-factor authentication options.
You can remove connected calendars and sync policies using the account controls. Censouk attempts to clean up its known destination mirrors when deleting the relevant policies or connections. Provider errors or revoked authorization may prevent cleanup; reconnecting or manually removing remaining destination copies may be necessary.
You can independently revoke Google's authorization in your Google Account's third-party connections. Revocation prevents future authorized access but does not automatically erase your Censouk account or copies already present in destination calendars.
We retain account, connection, and operational records while needed to provide the service, handle support and security issues, or meet applicable recordkeeping obligations. Successfully removing a calendar connection deletes its active credential record; account records and logs may remain separately. Contact us to request account or personal-data deletion. Historical backups and recovery exports are not immediately rewritten when an individual record is removed; we consider those copies when handling deletion requests and applying backup or record-retention procedures. Billing records may need to be retained separately for accounting or legal reasons.
You can update account details in settings. Depending on your location, you may also have rights to request access, correction, a copy, or deletion of personal information. Send requests to [email protected]; we may need to verify your identity and authority over the relevant account or household.
We will update this page when our practices change and use appropriate service notices for material changes. The date above identifies the current version.