Q 行事曆

Privacy policy

This privacy policy applies to the Q Calendar app (the “Application”) for mobile devices and its product website, provided by Regnum Digital Company (the “Service Provider”).

Q Calendar is designed to be a local-first calendar. Your calendar content, stickers, and most app data are stored on your device.

Account deletion: Delete your Q Calendar account, for versions that offer accounts. Requests are available in the app or by email without reinstalling it.

Analytics and crash reporting

Q Calendar uses Google Analytics for Firebase and PostHog for Product Analytics, and Firebase Crashlytics for Crash Reporting, to improve reliability and understand broad product use. Product Analytics and Crash Reporting are enabled by default. You can turn either one off on the first-launch privacy notice or later in Settings > Privacy.

The information sent may include an app-install identifier, app and device information, named screens, feature actions, crash diagnostics, and coarse location inferred from an IP address.

Your calendar and sticker content is never included in Product Analytics or Crash Reporting. This means we do not send event titles, notes, dates, attendees, sticker images, filenames, or imported file contents to these tracking services. Q Calendar may record that a feature was used, such as saving an event or importing a sticker, but not the content involved.

This information is not anonymous because it may use an app-install identifier. Q Calendar does not enable advertising, remarketing or personalised-ad integrations, and does not send advertising identifiers. The Application does not collect precise location data.

Turning off Product Analytics stops collection by both Google Analytics for Firebase and PostHog and resets their local analytics identities. It cannot recall events already queued or in flight, or delete information Google or PostHog has already processed. Turning off Crash Reporting disables future collection and deletes reports that have not yet been sent. Q Calendar does not use PostHog session replay.

Optional accounts and private cloud backup

This section applies only to app versions that offer accounts and cloud backup. You can use the local calendar without an account; versions without these features continue to store calendar content locally.

If you choose to create or sign in to an account, Supabase processes your account identifier, email address, authentication/session information and any identity or profile information shared by your chosen Apple or Google sign-in provider. Resend delivers account confirmation and recovery emails. Session tokens are kept in the device’s secure storage; Apple sign-in may also require an encrypted provider token on the server so sign-in permission can be revoked during account deletion.

Signing in to an account for the first time does not upload your calendar until you explicitly set up backup. Signing back in to an account whose backup was already configured can resume foreground uploads. Backup sends calendar records, including event content, dates, recurrence, reminders and deleted-event records, plus sticker library information, assignments and private image files to Supabase and Cloudflare R2. The app can read an existing account backup for setup or restoration. After setup, saved changes upload while the app is open; offline or interrupted uploads are retried when it next runs or resumes. This content storage is separate from content-free analytics, and the app’s analytics switches do not control cloud backup.

Your current cloud records, record-change and deletion history used by backup, and private uploaded images remain associated with the account until account deletion. Removing an event or sticker does not immediately erase its old recovery copies or uploaded image. Maintenance rotates recovery copies to seven daily and four weekly points, which may overlap, and retries failed cleanup; these are retained points rather than a fixed deletion deadline for inactive accounts. Temporary restore snapshots expire after one hour and are removed during later snapshot preparation or account deletion. Shared bundled and official sticker artwork is retained separately from account-private files.

Signing out stops account backup and keeps your local calendar and stickers. It does not delete your account or cloud content. Uninstalling the app also does not request cloud account deletion.

Delete your Q Calendar account

Request without reinstalling the app. For versions that offer accounts, email Q Calendar account deletion support and tell us your registered account email address. If you used Apple's Hide My Email, include the private relay address registered to Q Calendar. We verify account ownership before deleting your account, private cloud records, backups and uploaded images. Your local calendars and stickers stay on your devices. Do not send passwords or calendar contents.

不用重新安裝 App 即可申請。 此方式適用於提供帳戶功能的版本。請寄信申請刪除 Q Calendar 帳戶，並告訴我們帳戶登記的電子郵件地址。如果使用 Apple「隱藏我的電子郵件」，請提供 Q Calendar 登記的私密轉寄地址。我們會先驗證帳戶所有權，再刪除帳戶、私有雲端資料、備份及上傳的圖片。裝置上的本機行事曆與貼紙會保留。請勿寄送密碼或行事曆內容。

アプリを再インストールせずに申請できます。 アカウント機能を提供するバージョンが対象です。Q Calendar のアカウント削除をメールで申請し、登録したメールアドレスをお知らせください。Apple の「メールを非公開」を利用した場合は、Q Calendar に登録されたプライベートリレーのアドレスを記載してください。本人確認後、アカウント、非公開のクラウドデータ、バックアップ、アップロードした画像を削除します。端末内のカレンダーとステッカーは残ります。パスワードやカレンダーの内容は送らないでください。

In versions with accounts, open Settings > Account & backup > More actions > Delete account and confirm. You may need to sign out and sign in again first; Apple accounts may require signing in with Apple again so its sign-in permission can be revoked.

After a deletion request is accepted, cloud access is closed while background cleanup removes the account identity, private cloud records, recovery copies and private uploaded files. Completion is not immediate: cleanup waits for in-flight work and retries service or storage failures. Your calendar and stickers remain on your device; copies on other devices or in files you exported are not remotely erased. Deletion does not recall analytics or crash reports already processed by their providers.

Website analytics

This website uses Google Analytics by default to understand page visits and selections of its App Store and Google Play links. Google may process a browser identifier, browser/device information and approximate location inferred from an IP address. This measurement is not anonymous. Website measurement is separate from the Application’s Product Analytics and Crash Reporting controls.

You can turn Google Analytics off using the Google Analytics checkbox in the website footer. The website saves that choice in your browser, stops future Google Analytics collection and removes its local Google Analytics cookies. Turning it off cannot recall requests already in flight or erase information Google has processed. If your browser prevents preference storage, the switch applies only to the current page; browser content blocking can provide a persistent block.

The website sends page addresses without query strings or fragments and reduces referrers to their origin. Store-link reports contain only the store platform, the link’s hero/footer placement and the page language. We do not send form entries or calendar/sticker content. Google Analytics cookies can last up to 180 days; saved preferences remain until changed or cleared in your browser. Google Signals, advertising personalization and enhanced measurement are disabled for this website.

The hosting infrastructure also provides Cloudflare Web Analytics by default for traffic and page-loading performance, including referrers, browser/device categories and approximate country. The Google Analytics checkbox controls only Google Analytics.

Cloudflare states that its Web Analytics does not use cookies or local storage for measurement, fingerprint visitors, or track individuals over time. See Cloudflare’s Web Analytics explanation. Your browser’s content-blocking controls can prevent the browser analytics script from loading; this does not prevent the processing of connection information needed to deliver and secure the website.

The website’s Google Analytics and the Application’s Google Analytics for Firebase use a Google Analytics account whose data-sharing settings are enabled for Google products and services, aggregate modeling and benchmarking, technical support, and business recommendations from account/sales specialists. Google can use shared analytics data to improve its products and services, including Google Ads tools. Under Google’s applicable sharing terms, Google acts as an independent controller for this product-improvement use. These account settings are separate from Q Calendar’s disabled advertising features. See Google’s data-sharing explanation.

Photos, files, and local access

When you choose to import stickers, the Application may access the photos or files you select, including images in its local /stickers folder. Imported images are copied into the Application’s local storage so they continue to work inside the app. They are not sent to Product Analytics or Crash Reporting.

Third-party services

Q Calendar directly uses:

Versions offering optional accounts and backup also use:

These services process information for the purposes described above under their applicable terms. The optional account/backup services process account content on the Service Provider’s behalf; Google’s separate Analytics data-sharing use is described above.

Data sharing and retention

The Service Provider does not sell your personal data.

Limited information may otherwise be disclosed only:

Google and PostHog retain the information they process according to their applicable policies and terms.

If you uninstall the Application, locally stored app data may be removed from your device, subject to your platform’s normal uninstall behavior.

Children

The Application is not directed to children under the age of 13, and the Service Provider does not knowingly collect personal information from children under 13.

If you believe a child under 13 has provided personal information, please contact the Service Provider so appropriate action can be taken.

Security

The Service Provider takes reasonable steps to protect information processed through the Application and to keep the Application’s data handling limited and practical.

Because much of the Application’s data is stored locally, the security of your device also matters.

Changes

This Privacy Policy may be updated from time to time. Updates will be reflected on this page.

This privacy policy is effective as of 2026-10-18.

Contact Us

If you have any questions about this Privacy Policy or the Application’s privacy practices, please contact the Service Provider at [email protected].