Privacy Policy

Summary: Presentempo stores talks, sections, optional notes, cue choices, timer states, and rehearsal results primarily on your devices. There is no Presentempo account, proprietary app backend, advertising, or activity-tracking SDK. Data leaves the phone only through operating-system backups you use, watch sync, export/sharing, a support message, or technical processing of an optional Pro purchase by Apple or Google and RevenueCat.

1. Controller

2. App data processed locally

Presentempo processes the content you enter to plan, run, and review a talk. This content is kept in the app sandbox and is not made automatically accessible to the provider.

• Talks: titles, optional notes, total duration, sections, section names, and planned timing.
• Cues: visual, haptic, and audio cue choices and related local settings.
• Runs: active timer checkpoint, pauses, section changes, overtime, and crash-safe resume state.
• Results: planned and actual section timing, rehearsal results, history, and local statistics.
• Settings: language, appearance, onboarding, review counters, and a local cache of confirmed Pro status.

Presentempo does not require access to your microphone, contacts, calendar, location, or health data. The active database is not additionally encrypted by Presentempo; it is protected by the operating system's app sandbox and device security.

3. Timer, cues, and system permissions

To support an active timer when the app is not visible, Presentempo uses local system functions depending on the platform. These functions do not transmit talk content to Darkstone.

• notifications and ongoing activities for local timer cues,
• vibration or haptics for deliberately selected discreet cues,
• wake and foreground functions on Android so an active run is not ended unnecessarily,
• Exact Alarm or AlarmKit only where the platform and chosen feature provide for it.

Focus, Silent Mode, power saving, permissions, and operating-system limits can affect cue delivery. Presentempo stores no push token and operates no push backend.

4. Apple Watch and Wear OS

When you deliberately start watch sync, Presentempo transfers an immutable snapshot of the selected talk, timer state, commands, and the eventual result through the paired platform service. The watch stores enough data locally to continue a run when disconnected.

On Wear OS, the Data Layer normally uses Bluetooth. When Bluetooth is unavailable, Google may automatically route the end-to-end-encrypted payload through Google Cloud as a technical intermediary. Retention for such transport follows platform rules; talk content is not sent to Darkstone.

A connected watch receives deletion and update commands. A disconnected watch may keep its copy until it reconnects; alternatively, you must clear the app data on that watch yourself.

5. Device backups, export, import, and sharing

If you enable system backups, the database and local settings may be included in a device or cloud backup under the rules of your Apple or Google account. Darkstone can neither read nor manage these backups.

• Presentempo export: a versioned file containing selected app data that you explicitly create.
• CSV export: a readable report requested by you.
• Import: a selected file is checked for format and content before local replacement.
• Sharing/saving: the operating system passes the file only to the destination you choose.

Externally stored exports, operating-system backups, and email attachments are then governed by the selected service. Presentempo cannot delete those copies remotely.

6. Presentempo Pro, Apple/Google, and RevenueCat

Presentempo Pro is intended as an optional, non-consumable one-time purchase. Apple App Store or Google Play handles payment, store account, and refunds. Presentempo uses RevenueCat (RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA) for offering, validating, unlocking, and restoring the purchase.

• a randomly generated, pseudonymous RevenueCat App User ID,
• product identifier, store, purchase history, and entitlement status,
• Apple receipt or Google purchase token, price, currency, and transaction time,
• technically necessary information such as IP address, platform, app/OS version, locale, and store country.

Talk titles, sections, notes, timer states, and results are not sent to RevenueCat. Automatic advertising identifiers and RevenueCat diagnostics are disabled in the Presentempo code; advertising, attribution, and third-party usage analytics are not included.

The legal basis is Article 6(1)(b) GDPR for purchase, access, and restoration and Article 6(1)(f) GDPR for reliable entitlement state and abuse prevention. RevenueCat may process data in the United States and provides, among other safeguards, EU Standard Contractual Clauses in its Data Processing Addendum. More information: RevenueCat Privacy Policy.

7. Website and hosting

The pages at darkstone.app are static, set no cookies, and contain no analytics, advertising, social-media, or tracking services. Your IP address is technically required to deliver the page over HTTPS. The web server and upstream proxy keep no regular access logs; security-critical technical messages may be processed briefly.

The server is hosted by Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany. The legal basis is Article 6(1)(f) GDPR; our interest is secure and reliable operation. More information: Hetzner Privacy Policy.

8. Support contact

If you email us, we process your sender address, message, and information you provide voluntarily only to handle the request. Google provides our email service, which may involve processing by Google Ireland Limited and affiliated companies. More information: Google Privacy Policy.

Do not send real confidential talk content, passwords, complete store receipts, payment data, or device identifiers. App version, device model, operating system, and a description of the observed cue behaviour are normally enough for diagnosis.

9. Legal bases, recipients, and transfers

• Contract performance, Article 6(1)(b) GDPR: app function, pre-contractual or contractual support, purchase, and restore.
• Legitimate interests, Article 6(1)(f) GDPR: secure website operation, error handling, and reliable purchase entitlement.
• Your deliberate action: watch sync, export, sharing, import, and support contact start only when you initiate them.
• Recipients: Apple, Google, RevenueCat, Hetzner, and email providers only for the task described.
• Third-country context: Apple, Google, or RevenueCat may process data outside the EEA; their safeguards, contracts, and privacy notices apply.

Where providers act as processors on our behalf, they are contractually bound to documented purposes, confidentiality, appropriate security measures, and applicable data-protection duties. Apple and Google process some store and account data as independent controllers under their own terms.

10. Retention and deletion

• Local phone/tablet data: until individual deletion, “Delete all local data”, operating-system app-data deletion, or uninstall.
• Watch data: until update/deletion after reconnection or manual clearing of app data on a disconnected watch.
• Device backups: according to your platform and account settings and Apple or Google rules.
• Exports and email attachments: until you delete them at the external destination you selected.
• Purchase and entitlement data: according to legal obligations and store or RevenueCat retention rules; the purchase remains restorable.
• Support messages: until the request is complete and no statutory or legitimate evidence need remains, normally no longer than three years after closure.

“Delete all local data” stops an active run, removes the local database, settings, cache, and local Pro display state, and sends a watch deletion command. It cannot reach files already exported, external backups, provider mailboxes, store records, or a currently disconnected watch. Local deletion does not cancel a store purchase, which remains restorable.

11. Your rights and changes

Subject to the GDPR, you may have rights of access, rectification, erasure, restriction, portability, and objection. Where processing is based on consent, you may withdraw it for the future. Contact: darkstone.app@gmail.com. We may require reasonable proof of identity before disclosing or deleting information tied to a support request or RevenueCat identifier.

You may complain to a data-protection authority, particularly the Austrian Data Protection Authority. This policy will be updated if features, providers, or applicable law change materially; the current version remains available at this URL.