Privacy Policy for Crequence

Crequence is designed as a Local First app. Plans, tasks, ideas, notes, workflows and app settings are generally stored locally on the user's device. Crequence does not operate its own cloud database for this content.

Planning data and YouTube-derived working data are stored locally in SwiftData; channel avatars may also be held in a local avatar cache. Depending on how the app is used, this includes in particular:

• channels, videos and local planning information
• tasks, ideas, notes, publishing rhythms and production workflows
• reminders, display and app settings
• external YouTube channel and video identifiers, synchronization metadata and derived publication data
• channel and video names retrieved from YouTube where they have not been customized by the user

This data is not transferred to a Crequence server: Crequence operates no backend that receives or stores Google or YouTube user data.

Connecting YouTube is optional. Crequence uses Google OAuth so users can authorize access themselves through the Google interface. Crequence never receives the user's Google password.

Crequence currently uses only the Google OAuth scope https://www.googleapis.com/auth/youtube.readonly. This scope provides read only access to the authorized YouTube information.

When a YouTube account is connected, Crequence may read the following data from the YouTube API for its planning features: channel ID, channel name and channel thumbnail or image; video ID, video title, video description, video thumbnail, published date (publishedAt), scheduled publish date (scheduled publishAt), and privacy status where required to evaluate publication state.

Video descriptions and video thumbnails are read from the API but are not persisted by Crequence. Accessing a field does not mean that Crequence stores that field.

This data is used only for the channel overview, planning and publishing-status features visible in Crequence. Access is read-only: Crequence cannot upload, edit or delete YouTube videos or other YouTube content.

The app communicates directly with Google APIs when connecting and syncing. YouTube-derived working data is processed and stored locally where required. Crequence operates no backend that receives or stores Google or YouTube user data.

Authorization Data

OAuth access and refresh credentials issued by Google, as well as the connected account identifier, are stored in the Apple Keychain. They are not included in a Crequence backup and are not transferred to a Crequence server.

Disconnecting YouTube

Users can disconnect YouTube within Crequence. Access to Crequence can also be revoked at any time in the security settings for the relevant Google Account (opens in a new tab).

Disconnecting or revoking access removes OAuth credentials, the Google account or session identifier, external YouTube channel and video identifiers, YouTube synchronization metadata, remotely retrieved YouTube avatar data and its cache, YouTube-derived publication data, and channel and video names obtained from YouTube where they have not been customized by the user. User-created planning information, including tasks, ideas, notes, schedules, workflows and user-customized titles or names, may remain until the user deletes it.

Sharing Google User Data

Crequence does not sell, rent, disclose or transfer Google user data to advertisers, data brokers, analytics providers or unrelated third parties. Direct transfer to Google is required for OAuth and the requested API operations when connecting and syncing.

Google Privacy and Limited Use

Crequence's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements (opens in a new tab).

Further information is available in the Google Privacy Policy (opens in a new tab).

YouTube Terms of Service

Crequence uses YouTube API Services. Use of YouTube connected features is also subject to the YouTube Terms of Service (opens in a new tab).

Optional Crequence Pro purchases and subscriptions are processed through the Apple App Store and StoreKit. Crequence does not receive credit card details or complete payment information. Apple processes purchases under the terms and privacy policies applicable to the App Store.

The app receives from StoreKit only the information required to determine whether a valid Crequence Pro entitlement exists.

Crequence uses local iOS notifications when the user expressly enables them. Crequence does not operate its own push server for this feature. Permission can be changed at any time in iOS Settings.

Crequence allows users to deliberately export user-created planning data as a backup or CSV file. An export occurs only after an action initiated by the user. Crequence backups do not contain Google or YouTube-derived identifiers, synchronization metadata, titles or other YouTube-derived data; OAuth credentials, account identifiers and Keychain contents are also excluded. After export, the user decides where the file is stored or shared.

The Crequence app does not use advertising, advertising identifiers or its own analytics or tracking services.

Crequence provides features for deleting locally stored user data. Users can also disconnect YouTube and remove the app from their device. Removing the app deletes local data stored in its app container according to iOS mechanisms.

Access to Google or YouTube data can also be revoked in the Google Account settings (opens in a new tab).

You have the following rights regarding your personal data:

• Access under Art. 15 GDPR
• Rectification under Art. 16 GDPR
• Erasure under Art. 17 GDPR
• Restriction of processing under Art. 18 GDPR
• Data portability under Art. 20 GDPR
• Objection under Art. 21 GDPR

To exercise your rights, contact tshfm78@gmail.com.

You also have the right to lodge a complaint with a data protection supervisory authority. The competent authority is the State Commissioner for Data Protection and Freedom of Information North Rhine-Westphalia (LDI NRW), Kavalleriestraße 2-4, 40213 Düsseldorf, Germany. Further information is available from the LDI NRW (opens in a new tab).

This Privacy Policy may be updated if Crequence features, legal requirements or the use of external services change. The current version will be published on this page.