Privacy Policy

1. Who this policy covers

This policy applies to Ducelis Answer, including the Ducelis Answer web product at ducelis.pro and the Android application published by LoomStack. Ducelis Answer is not an advertising product and does not sell personal data.

2. Beta access identity

During the invitation-only web beta, Ducelis Answer uses Google Sign-In to confirm whether a Google account is on the tester allowlist. Google provides a signed identity token containing a stable Google account identifier and the verified email address associated with the sign-in. Ducelis uses those fields only to verify the sign-in, enforce invited access, and maintain the signed browser session.

The current beta implementation does not create a separate Ducelis Answer account profile or account database. The invited-email allowlist is maintained as an operator-controlled server configuration, and the browser receives a Secure, HttpOnly session cookie after an approved sign-in. Removing an email from the allowlist invalidates that account's access after the service reloads the updated configuration.

The current Android closed-test bundle does not implement this web Google sign-in session as native app identity. Server-backed beta APIs remain unavailable to native requests unless a reviewed native identity path is added.

3. Rehearsal content and evaluation

You may enter scenario context, goals, answers, retry wording, or other text needed for a rehearsal. Text you type remains in the local client unless you choose an action that requires server processing, such as requesting reviewed evaluation feedback.

For an evaluation you request, Ducelis transmits the necessary scenario context and your answer to the Ducelis Answer evaluation service. The current reviewed Manager Conversations evaluator uses a Google Gemini model as a processing provider to propose structured candidate feedback; Ducelis applies its own evidence, calibration, risk, confidence, and fail-closed gates before showing a report. Do not include confidential, regulated, or highly sensitive information unless it is necessary for the rehearsal and you are permitted to provide it.

Full rehearsal text is not intentionally copied into Ducelis product-improvement telemetry. An evaluation request is separate from optional telemetry consent.

4. Data stored on your device

Some product state may be stored locally on your device or browser, for example whether you completed the first rehearsal and, when you explicitly choose local saving, a practice snapshot. During the web beta, the browser also stores the secure session cookie used to maintain approved access. Local state remains on that device unless a feature expressly tells you it will be sent elsewhere. You can remove local state using the product controls where provided, by signing out, by clearing site/app data, or by uninstalling the app.

5. Optional product-improvement telemetry

Product-improvement telemetry is off by default and requires an explicit opt-in where enabled. The bounded telemetry contract is designed for structured events such as feature events, opaque session identifiers, version references, retry outcomes, and structured feedback fields. It excludes raw source text, raw answers and retry answers, supplemental context, and free-form dispute notes.

For the current bounded beta design, opted-in product-improvement telemetry uses a 30-day rolling retention window. A user can provide the opaque session reference shown by the product to request deletion of already-sent telemetry.

6. Purchases and entitlements

When paid features are enabled, purchases are processed through Google Play and RevenueCat. These services may process product identifiers, transaction or entitlement status, a pseudonymous app user identifier, device/app information, and related purchase metadata needed to complete and restore purchases. Ducelis does not receive your full payment-card number from Google Play or RevenueCat.

7. Notifications and return reminders

When event-time reminders are enabled and you explicitly ask for one, Ducelis may use OneSignal to obtain and use a push-subscription identifier and the minimum routing data needed to return you to the selected reviewed scenario. Notification permission is not requested merely because the app starts. Ducelis does not put your transcript, retry answer, score, confidence, gap details, or user-authored reminder copy into the provider routing payload for this reminder flow.

8. Technical and security data

Hosting and security infrastructure can generate ordinary technical records such as request timestamps, network addresses, HTTP headers, response status, and security or operational logs. We use these records to deliver the service, prevent abuse, diagnose failures, and protect the service. Personal and sensitive data is transmitted over encrypted HTTPS connections where it leaves the device.

9. Service providers

Depending on the feature and build you use, data may be processed by:

• Google for Google Sign-In identity verification in the invitation-only web beta, Google Play distribution/purchases, and Google Gemini evaluation processing.
• RevenueCat for purchase and entitlement infrastructure when billing is enabled.
• OneSignal for push-notification delivery when reminders are enabled.
• Hosting, network, and security providers needed to operate ducelis.pro securely.

Third-party processing is also governed by the applicable provider terms and privacy practices. We remain responsible for configuring our integrations and disclosures consistently with the features we ship.

10. How we use data

• Verify invited web-beta access and maintain an approved sign-in session.
• Provide the rehearsal, evaluation, retry, and return experience you request.
• Maintain purchase entitlements and restore access when paid features are enabled.
• Protect the service, prevent abuse, debug failures, and maintain reliability.
• Improve Ducelis Answer only through product-improvement data for which the required consent has been obtained.
• Comply with applicable legal obligations and enforce our rights where necessary.

11. Retention and deletion

We retain data only for the purpose and period reasonably needed for the feature, security, legal, or operational requirement involved. Local device data remains until you delete it or the device/app removes it. The current invitation allowlist remains in protected server configuration while beta access is authorized; the web session expires automatically and can also be cleared by signing out. Opted-in bounded product-improvement telemetry uses the 30-day rolling retention described above. Purchase and notification records may be retained by the relevant providers as required to operate those services or meet legal obligations.

The current web beta uses an external Google identity for access but does not create a standalone Ducelis Answer account profile. The current Android closed-test build does not enable account creation or external account sign-in. Before a released Android build enables account creation or sign-in, Ducelis Answer will provide the applicable account-deletion method and update this policy and the Google Play Data safety disclosures as needed.

12. Children

Ducelis Answer is designed for adults practicing important professional and other consequential conversations and is not directed to children under 18.

13. Changes to this policy

We may update this policy when product features, providers, or data practices change. We will update the date above and, when a change materially affects how personal or sensitive data is handled, provide additional notice or consent where required.

14. Privacy contact

Developer: LoomStack
Product: Ducelis Answer
Privacy inquiries and deletion requests: privacy@ducelis.pro