Kadence Privacy Policy

Most information in Kadence is information you give us on purpose. Depending on how you use the service, this may include:

• your account email address (and password credentials handled by our auth provider)
• optional profile information such as a display name, username, avatar image, and profile appearance choices
• display and interface preferences, including language and timezone settings
• the titles you follow and the release categories you follow for each title
• notification preferences, including per-title notification toggles and reminder timing
• email digest (newsletter) consent and its unsubscribe state
• release-tracking preferences such as calendar sync categories
• your Kadence+ membership status and related preferences
• anything you send us in support or account correspondence

Avatar images you upload are stored privately and are shown only through short-lived links generated for your session. Kadence does not scan avatars automatically, but an administrator can remove an uploaded avatar that breaches the Terms of Service (for example unlawful, abusive or infringing images); removal deletes the file and resets the profile to initials.

Kadence does not ask for your real name, phone number, home address, or payment card details. Kadence does not collect your contacts, photos library, or precise device location.

Like most web and mobile applications, Kadence and its infrastructure providers record basic technical information when you use the service:

• device and browser characteristics, including a general device class (mobile, tablet, desktop) and platform
• which pages and features are opened, and general interaction events
• referral / traffic-source information where the browser provides it
• request metadata handled by our hosting and database providers, which necessarily includes your IP address and can include IP-derived general location (such as country)

Product analytics are first-party. Kadence does not embed a third-party analytics SDK in the website or the app. Analytics records store the page path with any query string or fragment removed, a coarse device class, the platform, a country code where our host provides one, and a session key — and they are written without an account identifier, so an analytics event is not linked to your Kadence account. Kadence does not store raw IP addresses or raw browser user-agent strings in those analytics records.

The session key is a one-way hash of request metadata (including IP address and user-agent inputs) combined with a secret and the current UTC day. Because the day is part of the input, the key changes daily and cannot be used as a persistent or cross-day device identifier; it exists so Kadence can count sessions and unique visitors for a reporting window. It is not an advertising identifier. Records of clicks through to external services where you can watch, read or buy a title are not linked to your account.

Diagnostics. Ordinary operational and server logs may contain error messages, request information and other diagnostic detail needed to run, debug and secure the service. Kadence does not use a third-party crash-reporting or error-analytics product.

Push notifications are optional. On the iOS app, when you allow notifications, Apple issues an app-specific push token for that installation and Kadence stores it so releases you follow can be delivered to that device. For each registered device Kadence may store:

• the Apple-issued app-specific push token for that app installation
• the platform and the push environment (production or sandbox)
• the app bundle identifier and app version
• the device name the operating system reports
• whether the registration is currently enabled or disabled
• registration and last-seen timing information

Notification preferences — whether notifications are on at all, which titles you want alerts for, and reminder timing — are associated with your Kadence account, and push registrations are linked to the account signed in on that device. Notification content is prepared and localised by Kadence from release information. To deliver a notification, the device token and the notification payload are transmitted to Apple Push Notification service, which performs the delivery. Kadence does not intentionally include your email address or your Kadence account identifier inside the notification payload sent to Apple. The push token is an app-specific delivery address for that installation; it is not an advertising identifier and Kadence does not use it for advertising.

Signing out. When you deliberately sign out on the native app, Kadence attempts to disable that device's push registration for the account you are signing out of before the session ends, so that device stops receiving notifications for the account. Other devices signed in to the same account are not affected, and your account-level notification preferences are left as they are. Signing back in on the device can register it again through the normal registration flow. As with any network operation this attempt can fail, and neither delivery nor the timing of Apple's own token handling is something Kadence can guarantee. You can also turn notifications off in Kadence's notification settings or in the operating system's own settings for the app.

You can create a Kadence account with an email address and password, which is handled by Kadence's managed authentication provider. Where offered, you can instead choose Google sign-in or Sign in with Apple. Social sign-in is a convenience, not a requirement — email and password works on its own.

If you choose a social provider, that provider processes the sign-in request on its own side and returns to Kadence the identity information needed to create or access your Kadence account — typically a stable account identifier and, where available, an email address. Apple lets you hide your address, in which case Kadence receives an Apple private relay address instead of your personal one, and that is the address Kadence uses for your account. Kadence does not receive your password for a social provider.

Kadence+ is a paid membership. Kadence does not receive or store full payment card numbers.

On the web, Kadence+ subscriptions are processed by Stripe. Checkout, card details and payment processing happen on Stripe's side. So that a payment can be matched to the right membership, Kadence provides Stripe with your account email address and a Kadence account/customer reference, and receives back subscription and checkout information such as the subscription and customer identifiers, the plan, the status and the current period dates. Kadence uses that to grant and maintain your membership, and stores billing event records for accounting and support purposes.

On iOS, a Kadence+ purchase is processed by Apple through the App Store. Apple handles the purchase, the payment method and the billing relationship; Kadence receives transaction and subscription identifiers and status information needed to verify the purchase and keep your entitlement current. A membership bought through the App Store is managed and cancelled in your Apple subscription settings, not by Kadence.

Connecting Google Calendar is entirely optional. Kadence works fully without it, and nothing about your Google account is accessed unless you explicitly start the connection and grant permission on Google's own consent screen.

Kadence requests a single, narrow Google OAuth scope:

https://www.googleapis.com/auth/calendar.app.created

In plain language, this permission allows Kadence to:

• create a separate, secondary Google Calendar for your Kadence releases
• create release events on that Kadence-created calendar
• update those events when release dates or times change
• delete or otherwise manage those Kadence-created events as needed to keep the calendar accurate

This scope is limited by Google to calendars that Kadence itself created. Kadence does not read, edit or delete your existing personal or work calendars, and does not request access to your Google profile, contacts, email or files. Google Calendar access is used solely to provide the calendar-synchronisation feature you asked for.

Kadence's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

How credentials are handled. Because synchronisation must continue while you are not using the app, Google issues Kadence a refresh token in addition to a short-lived access token. These tokens are held only on Kadence's servers, encrypted at rest, in storage that ordinary application users and the browser cannot read. The browser and mobile app never receive your Google tokens — they only see a connection status. Tokens are used exclusively to maintain the Google Calendar connection you requested. Kadence also stores the identifier of the calendar it created and the identifiers of the events it created, so that a later sync can update the right event instead of duplicating it.

Disconnecting. You can disconnect Google Calendar at any time from Kadence's calendar sync settings. When you disconnect, Kadence asks Google to revoke the authorisation, deletes the stored credentials, and removes future Kadence-created release events from the Kadence calendar; events already in the past are left in place. Future synchronisation stops. If your Kadence+ membership lapses, synchronisation stops as well and existing events are not deleted. You can also revoke Kadence's access directly from your Google Account's third-party access settings.

Apple Calendar on iOS is different. When you add a single eligible release to your calendar through the native iOS flow, Apple's own EventKit interface opens on your device with the event details filled in, and you save it yourself. That is an on-device action: Kadence does not connect to an Apple Calendar account, does not receive or store Apple Calendar credentials, and does not read your existing Apple calendars through it. There is nothing to disconnect afterwards, and removing such an event is done in your own calendar app.

• to provide and operate Kadence
• to create and maintain your account and sign you in
• to remember your preferences, language and timezone
• to keep track of the titles and release categories you follow
• to show you release information and personalised release feeds
• to send notifications and email digests you have asked for
• to synchronise releases to Google Calendar when you enable it
• to provide Kadence+ features to members, and to process and verify memberships
• to answer your support requests
• to prevent abuse and protect the service and its users
• to detect, diagnose and fix errors
• to understand aggregate product usage and improve Kadence
• to comply with legal obligations

On the Kadence website, the free tier may include advertising served by Google AdSense. Where an ad is shown, Google's advertising script is loaded from Google and may set or read cookies and similar storage on your device to deliver, limit and measure ads. Kadence loads no advertising script at all for Kadence+ members, and none inside the iOS app, where the app's own advertising is used instead. Google processes the information it collects this way under its own privacy policy and terms. Until the required regional consent controls are in place, web advertising is limited to non-personalised, contextual ads.

In the iOS app, the free tier includes advertising served by Google Mobile Ads (AdMob), and Google's User Messaging Platform is used to gather and record the advertising consent choices required in your region. Kadence's own app code does not read Apple's advertising identifier (IDFA). Whether Google's advertising SDK can access an advertising identifier, and whether ads are personalised, depends on your device settings, the consent choices you make in that prompt, and Apple's app tracking permission where applicable. Where the consent state means personalised advertising is not available, Kadence's ad integration requests non-personalised, contextual ads rather than dropping ads. Google processes the information it collects through that SDK under its own privacy policy and terms.

Kadence+ members do not see advertising — the app does not load ads for members.

Information obtained through Google Calendar or any other Google API authorisation is never used for advertising, ad targeting, ad measurement, profiling for advertising, or for building marketing audiences, and is never sold or transferred to advertisers, data brokers or information resellers. Google API data is used only to provide the calendar-synchronisation feature you requested, to comply with applicable law, and where strictly necessary for security or abuse investigations.

Kadence's support page includes an assistant that answers questions from Kadence's own published help content. To generate an answer, the text you type into the support assistant, and the assistant's earlier replies in the same conversation, are sent to a third-party AI provider that processes them on Kadence's behalf and returns the answer. That processing happens through the Lovable AI Gateway, which routes the request to the underlying model provider (currently an OpenAI model). Kadence sends only the conversation text and Kadence's own help content; it does not send your email address, account identifier, followed titles or other profile data with the request, and the request is not used to identify you.

Assistant conversations are not stored by Kadence when you only ask the assistant a question. Because the message is processed by an external provider, please do not type passwords, payment details, verification codes or other sensitive information into it — the assistant will never ask for them.

If you choose to hand the conversation to a human, Kadence stores the request so the team can reply: the conversation transcript you send, your description of the problem, the topic you selected, and a contact email address (your account address when you are signed in, or the address you provide when you are not). Human support requests are readable by Kadence's authorised support administrators and are used only to answer and resolve your request. Support correspondence sent to us by email is handled the same way. Escalated support requests are not sent to the AI provider.

You do not need an account to reach human support. If you escalate while signed out, the request is kept as a guest request: it is not tied to any Kadence account, and it holds the contact email you give us together with whatever transcript and context you chose to submit with it. How long guest requests are kept is described under data retention below.

The assistant explains and hands off; it cannot change your account, your membership or your data, and it does not make automated decisions about you.

Kadence does not sell your personal information, and does not sell or transfer Google API user data. Kadence relies on a small number of providers that process information on its behalf, and only where they actually need it:

• Supabase / Lovable Cloud — application hosting and infrastructure, the managed database, authentication and file storage. This is where account information, authentication and session information, preferences, follows, support records and the other data described in this policy is stored and processed.
• The AI provider behind the support assistant — the Lovable AI Gateway and the underlying model provider (currently OpenAI), used for the support assistant only, and only for the conversation text described in the support section above.
• A managed email delivery service — sends Kadence's account and authentication emails and the weekly Kadence Digest. It receives the recipient address and the message content necessary to deliver the email.
• Apple — push delivery through Apple Push Notification service, App Store and StoreKit purchase processing and verification, and Sign in with Apple where you choose it.
• Google — Google sign-in where you choose it, the optional Google Calendar integration, and advertising and consent management in the mobile app through Google Mobile Ads and the User Messaging Platform.
• Stripe — web Kadence+ checkout, payment processing and subscription billing, as described in the payments section.

Information may also be disclosed where required by law, regulation, legal process or a valid government request; where necessary to investigate abuse, fraud, or threats to security or to our users; and in connection with a merger, acquisition or other business transfer, where legally permitted and subject to this policy.

Catalog and release sources are not sent your data. Kadence builds its release information from third-party catalog and evidence sources, which are listed on the data sources page. Those requests are made by Kadence's servers and ask for general title and release information; they do not carry your account, your email address, your follows or your Kadence user identifier. Those providers are not processors of your account data.

Some images and media shown in Kadence are not copied onto Kadence's own servers — your browser or app loads them directly from the host that provides them. Permitted artwork may be loaded from static.tvmaze.com or media.rawg.io, and if you choose to play a trailer, it is embedded from YouTube's privacy-enhanced domain (youtube-nocookie.com).

Loading content directly means your device necessarily makes a connection to that host, so that host receives the ordinary network and request information any web request carries — such as your IP address and browser or device characteristics — and handles it under its own privacy policy. Kadence does not send your account email address, your Kadence user identifier, or the titles you follow to those hosts.

Kadence uses reasonable technical and organisational measures to protect your information: encrypted transport (HTTPS), database-level access rules so that account data is readable only by the account owner and authorised server processes, encryption at rest for Google Calendar credentials, and administrative access limited to authorised operators. No service can guarantee absolute security, and we do not claim to.

Information is kept only as long as reasonably necessary to operate Kadence, provide the features you have enabled, satisfy legal obligations, resolve disputes and prevent abuse. Account and preference data — including your follows, notification preferences and registered push devices — is retained while your account exists and is removed when you delete your account, as described below. Kadence does not set a separate fixed expiry for analytics records or notification and digest delivery history; they are kept as operational records for service, security and reporting purposes.

Google Calendar authorisation data is retained only while your connection is active. When you disconnect, or when authorisation is revoked, the stored credentials are deleted and Kadence retains only what is needed to reflect that the connection has ended.

Support requests. Support-assistant questions are not stored by Kadence. Human support requests made while signed in belong to your account and are removed under the account-deletion lifecycle described below. Human support requests made by a signed-out visitor are not tied to any account; as a matter of Kadence's own retention practice — not a legal requirement — a guest request that has been resolved or closed is automatically deleted more than 90 days after it was resolved, and deleting it also deletes its messages. Guest requests that are still open or waiting on a reply are not deleted by that rule, because they are still being handled. Kadence keeps no guest support portal, so there is no self-service way to look up or delete a guest request; you can raise privacy questions about one at the support address below.

Billing records may be retained after an account is deleted, or kept in a form detached from your account, where they are needed for accounting, tax and dispute purposes.

• update your profile, language, timezone and display preferences in Settings
• turn notifications off entirely, or per title, in notification settings
• unsubscribe from the weekly email digest in settings or from any digest email
• disconnect Google Calendar at any time from calendar sync settings, or revoke access from your Google Account
• unfollow any title from its page or from Following
• cancel a paid Kadence+ membership from Kadence+ settings, or through the store or payment platform used for the purchase
• permanently delete your account and its data yourself, from Settings → Account → Delete Account

Deleting your account

You can delete your Kadence account at any time, without contacting us, from Settings → Account → Delete Account. Deletion is permanent and cannot be undone. When you confirm it, Kadence:

• immediately cancels any active paid Kadence+ membership purchased on the web, so no further payment is taken
• asks Google to revoke Kadence's calendar authorisation and destroys the stored calendar credentials
• deletes any avatar image you uploaded from our storage
• deletes your profile, username, bio and favourites; your followed titles and tracked list; your notification, digest, language, timezone and appearance preferences; your notification and digest delivery history; your registered push devices; your Kadence+ subscription, grant and billing records; and your calendar connections, calendar preferences and Kadence-created calendar links
• deletes your sign-in identity, which ends all sessions on every device

Two things intentionally survive deletion. Usage analytics events are detached from your account by removing the account identifier, so they remain only as anonymous aggregate counts. Records of administrative actions taken on an account (for example a suspension), and payment records our payment processor is required to retain for tax and accounting law, are kept as required; they are not used to rebuild a profile of you.

Deleting your Kadence account does not delete events Kadence previously wrote into your own Google Calendar. Because the authorisation is revoked, Kadence can no longer reach that calendar; you can remove those events yourself in Google Calendar. If a paid membership was bought through an app store rather than the web, cancel it in that store's subscription settings — only the store can cancel it.

If you cannot sign in and therefore cannot use the in-app flow, email us from your account address at support@kadence.media with the subject "Account deletion" and we will verify the request and delete the account for you.

Kadence is a general-audience release-tracking service and is not directed to children. Kadence does not knowingly create accounts for, or knowingly collect personal information from, children under 13 years of age (or the higher minimum age required in your country). Kadence does not currently ask for a date of birth at sign-up. If you believe a child has created an account or provided information to Kadence, contact us at support@kadence.media and we will remove it.

Some titles listed in Kadence are intended for mature audiences. Adult-only records are excluded from public discovery surfaces.

This policy may be updated as Kadence changes. When we make material changes we will update the "Last updated" date above and, where appropriate, notify you in the application or by email. Continuing to use Kadence after an update means you accept the revised policy.

Kadence is operated by Nestify LLC. Questions about this policy, your data, or the Google Calendar integration can be sent to support@kadence.media, which is the contact address for privacy requests.

See also our Terms of Service and our data sources and verification page.