Privacy Policy

1. Controller

Sergej Weber, P.O. Box 1123, 64355 Mühltal, Germany. Email: info@paradaq.com.

2. Canonical policy source

This page is the canonical privacy policy for Paradaq's website, waitlist, backend APIs, support and feedback channels, and iOS/Android app. Repository markdown files, app-store drafts, and other local policy files are non-canonical implementation copies unless they link back to this page or are expressly marked as the current public policy. The Data Processing Inventory and DPA and Subprocessors pages explain the same data flows in more operational detail.

3. Scope and current release stage

This policy applies to the Paradaq website, waitlist pages, feedback and bug-report forms, support communication, internal issue tracking, and Paradaq mobile application for iOS/Android, including the founder initial release. Even during early release, Paradaq may process account data, waitlist data, uploaded work content, AI extraction requests, voice transcription requests, analytics, diagnostics, subscriptions, calendar data, notifications, support requests, feedback and bug reports, issue-tracking records, and local app storage described below.

4. Data we process

• Account data: email, Supabase user id, authentication/session tokens, login metadata, profile fields, plan tier, entitlement status, support and privacy request history, and security records needed to create, authenticate, support, and protect your Paradaq account.
• User-uploaded content: screenshots, images, shared text, documents, filenames, MIME type, voice/audio input, transcripts, client names, messages, task and calendar details, meeting links, locations, project context, source platform hints, extraction payloads/results, and other content you explicitly submit or store in Paradaq. This may include third-party or client content that you choose to provide.
• Waitlist and email data: email, optional first name, use case, roadmap interest, preferred platform, alpha tester flag, source page, UTM metadata, locale, newsletter language, consent version, consent timestamp, and unsubscribe metadata.
• Feedback, bug-report, and support data: name or email if provided, message content, bug description, feature request, reproduction steps, screenshots or attachments, device/app/browser information, operating system, app version, logs or diagnostic details voluntarily submitted, source form metadata, timestamps, and follow-up history.
• Technical, security, and abuse-prevention data: IP-derived request metadata, user agent, device/app metadata, request ids, rate-limit state, server logs, crash/error diagnostics, traces, and operational security records.
• Analytics data only after consent where required: page/app events, route names, CTA and waitlist events, consent state, PostHog distinct id, and limited product usage metrics. We do not intentionally send raw intake content to analytics.
• Subscriptions and payments: RevenueCat customer id, Supabase user id mapping, product identifiers, entitlement state, subscription status, restore-purchase metadata, and app-store transaction references.
• Calendar, notifications, media, files, and local storage: native calendar ids/event ids, reminder times, notification identifiers, local inbox media, local cache/outbox data, SecureStore/Keychain/ Keystore session storage, AsyncStorage preferences, speech capability cache, cloud transcription preference, and downloaded local model files where supported.

5. Controller and processor roles

Paradaq is the controller for account administration, authentication, billing entitlement, waitlist/email, website consent, analytics, diagnostics, security, support, feedback and bug-report handling, issue triage, legal requests, and product reliability records.

For professional users who upload client, customer, or work content, the user or customer may be the controller for that content and Paradaq acts as processor when it processes the content to provide the requested app workflow.

When users submit feedback, bug reports, screenshots, or support messages to Paradaq, Paradaq is normally the controller for handling that request and improving the product. If a professional user includes client/customer content in a support or bug report, the user remains responsible for having a lawful basis to share that content.

6. Purposes and legal bases

• Account, app access, synchronization, AI extraction, voice transcription, calendar sync, subscriptions, and transactional waitlist/early-access communication: Art. 6(1)(b), performance of a contract or steps you request before entering a contract.
• User-uploaded content and professional client/work content: Art. 6(1)(b) for requested app features, processing under the user or customer's instructions where Paradaq acts as processor, and the user's separate legal basis for any third-party or client content they submit.
• Feedback, bug reports, support requests, issue triage, and product reliability work: Art. 6(1)(b) where needed to respond to your request or provide support; Art. 6(1)(f) legitimate interests in fixing bugs, improving reliability, preventing abuse, and documenting support history.
• Optional marketing email, optional analytics cookies/storage, and consent-gated mobile analytics/diagnostics where required: Art. 6(1)(a), consent.
• Security, abuse prevention, fraud prevention, reliability, basic server logs, and legal claim preservation: Art. 6(1)(f), legitimate interests.
• Tax, accounting, app-store, and statutory record keeping where applicable: Art. 6(1)(c), legal obligation.

7. Processors and recipients

Current processors and recipients include:

• Supabase: authentication, database, storage, and consent logs.
• Vercel: website and backend API hosting, request processing, and operational logs.
• OpenAI API: AI extraction through chat/completions and cloud voice transcription through audio/transcriptions for content you explicitly submit. OpenAI's current platform data-controls table states that these API endpoints are not used for training; endpoint retention and abuse-monitoring rules can still apply under OpenAI's terms and project settings.
• PostHog EU: optional website and product analytics after consent.
• Sentry: crash, error, performance, log, trace, and masked replay diagnostics where configured and consent-gated where required.
• RevenueCat: subscription entitlement, purchase infrastructure, restore purchases, and subscription support.
• Brevo: waitlist contacts, transactional/pre-launch email workflows.
• Tally: feedback forms, bug-report forms, early tester forms, and structured user-submitted feedback where enabled.
• Linear: internal issue tracking, bug triage, feature-request management, and product reliability workflows where feedback, bug reports, support summaries, screenshots, reproduction steps, or diagnostic details are copied or synced into Paradaq's issue tracker.
• Apple and Google: app distribution, platform checkout, refunds, app-store records, optional sign-in where enabled, OS calendar, notification, backup, and device services under their platform terms.
• Support mailbox provider: support, privacy, deletion, billing, and legal requests sent to info@paradaq.com.

8. Feature-specific flows

• Supabase account and storage: account, app records, extraction history, intake jobs, image object paths, consent logs, and deletion audit records may be stored in Supabase.
• OpenAI/backend extraction: text, images, files, prompt context, candidate client/project context, and extracted fields are sent from Paradaq backend routes to OpenAI only when you submit them for extraction.
• Voice transcription: cloud transcription sends the uploaded audio file, filename/MIME type, language hint, and resulting transcript through the Paradaq backend to OpenAI. The current backend returns the transcript and does not intentionally store raw audio in the web route.
• Feedback and bug-report forms: if you submit a feedback or bug-report form, the form response may be processed by Tally and then reviewed by Paradaq. You should avoid submitting sensitive third-party content unless it is necessary for the support request and you have a lawful basis to share it.
• Internal issue tracking: Paradaq may create internal Linear issues from feedback, support messages, bug reports, crash details, screenshots, reproduction steps, or product requests. Paradaq aims to minimize personal data in issue titles and descriptions where possible.
• Calendar sync: accepted items can be written to the device calendar through OS calendar APIs. If your device calendar syncs to Apple, Google, or another calendar provider, that provider handles the calendar copy under its own terms.
• Notifications and reminders: local reminder state and notification ids can be stored on device. Remote push tokens are processed only if remote push is enabled for a feature.
• Media, files, and local storage: inbox media, drafts, local cache, outbox, preferences, session tokens, and model files may remain on device until you delete them, sign out, clear app data, delete your account, or uninstall the app.

9. International transfers

Some processors may process data outside the EEA. Where applicable, we rely on GDPR-compliant safeguards, including Standard Contractual Clauses and, where applicable, adequacy decisions such as the EU-US Data Privacy Framework. The current provider-by-provider transfer overview is available on the DPA and subprocessor page.

10. Retention

• Waitlist contacts: until launch cycle completion or unsubscribe/deletion request.
• Feedback and bug-report form responses: retained while needed to handle the request, improve the product, investigate bugs, or document product decisions, then deleted or minimized when no longer needed.
• Internal issue-tracking records: retained while the issue, feature request, reliability investigation, or related product decision remains relevant. Paradaq aims to remove or minimize personal data from internal issues when it is no longer needed.
• Consent logs: stored in Supabase for governance and compliance evidence, retained for 3 years from the date of creation.
• Account data: retained while your account is active, then deleted according to operational deletion windows.
• User-uploaded content: retained while needed to provide the requested app workflow, preserve records you choose to keep, sync accepted tasks/meetings, or meet legal, security, and operational requirements.
• Account deletion: account, profile, app database records, and user-scoped storage are deleted within 30 days of a verified deletion request.
• Local device data: account-scoped local cache, inbox media, reminders, and calendar sync state are cleared by account deletion, sign-out, app data clear, or uninstall; non-account preferences remain until changed or cleared.
• Native calendar events: remain in the device calendar until deleted, disabled/removed from sync, cleaned up during account deletion where tracked, or retained by the user's calendar provider.
• Analytics and diagnostics: optional analytics, replay, and error telemetry are disabled until consent where required and are retained according to provider project settings.
• Billing, legal, support, and backups: payment records, fraud/security records, support/legal audit records, and provider backups may be retained where required by law, platform rules, security needs, or backup expiry windows.

11. Your controls

• Review AI-suggested extraction results before accepting them into your workflow.
• Edit or delete tasks, meetings, clients, projects, inbox items, transcripts, and uploaded content where the app exposes those controls.
• Revoke OS permissions for microphone, speech recognition, calendar, photos/files, and notifications.
• Change cookie and analytics settings, withdraw marketing consent, unsubscribe from email, sign out, clear app data, uninstall the app, or request account deletion.
• Ask Paradaq to delete or minimize personal data contained in feedback, support, bug-report, or issue-tracking records where deletion is legally and operationally possible.

12. Your rights

You can request access, rectification, deletion, restriction, objection, and data portability. You can withdraw consent at any time. Contact: info@paradaq.com.

12a. Waitlist and email consent

The waitlist form separates emails needed to process your early-access request from optional marketing newsletter consent. You can unsubscribe or withdraw email consent at any time by using the unsubscribe link in the email or by contacting info@paradaq.com.

12b. Feedback and bug reports

If you submit feedback, a bug report, or a feature request, Paradaq uses the information you provide to understand the request, reproduce problems, respond where appropriate, improve the product, and document product decisions. Please do not include sensitive personal data, client secrets, passwords, payment details, or unnecessary third-party information in feedback or screenshots.

13. Cookies and consent

We use cookies and similar storage technologies to operate this website. Essential cookies are always active. Analytics cookies are optional and disabled by default until you opt in.

If a Tally form is embedded on Paradaq pages, Tally may process form-related technical data and submitted form content when you interact with or submit that form. If the form is only linked externally, Tally processes the form interaction on Tally's own form page.

You can change your cookie preferences at any time by clicking the cookie settings button in the bottom-right corner of any page. Under German TDDDG requirements, analytics storage is treated as optional and is disabled until you consent; strictly necessary and user-preference storage is used to provide the site and remember your choices.

14. Contact and complaints

For privacy requests: info@paradaq.com. You may also lodge a complaint with your competent supervisory authority.