Privacy Policy

1. Operator and privacy contact

PROGY is the public brand used by the service operator based in Germany. Contact the operator about personal data at:

PROGY
Dümmlinghauser Str. 60
51647 Gummersbach, Germany
hello@progy.tech

2. Information processed

• Account and authentication information: email address, authentication records and profile display name; password authentication is handled by the authentication service. Google sign-in is available as an alternative.
• Saved watchlists, notification preferences, community-analysis preferences, plan entitlements, credit balances and credit activity.
• Community message text, author association and timestamps. Public community history can display message bodies and display names to visitors.
• AI request records, requested market and explanation type, generated explanations, usage information and, for some insights, a requester association.
• Technical error and operational records, administrative review records and information you send in support communications.

The reporting implementation is designed to process the selected message, report category, reporter association, time and review status when submission is available. A failed submission is not evidence that a report was stored. PROGY does not currently offer payments or collect payment-card details through a checkout.

3. Purposes and legal bases

Account creation, authentication, requested watchlists and preferences, requested AI explanations and credit accounting support service delivery. Where necessary to perform our agreement with you, the intended legal basis is Article 6(1)(b) GDPR.

Public display of messages you choose to post is part of the community service. Security, fraud prevention, troubleshooting and proportionate moderation serve legitimate interests under Article 6(1)(f), subject to a balancing of those interests against your rights. Processing required by a specific legal obligation relies on Article 6(1)(c) where applicable.

Community topic analysis is intended to support service improvement under legitimate interests, with a user exclusion control; you may object using that control or the contact address. Consent is not treated as a blanket basis for all processing. Where consent is required for an optional activity, it must be obtained for that activity before it is enabled.

4. AI explanations and community topic analysis

AI requests pass through Lovable’s AI Gateway. The code is configured for an OpenAI model by default; the model can be changed by server configuration. For market explanations, the constructed request contains market questions, descriptions, categories, outcomes, sampled probability history and related signals. It does not add your account email, display name or user ID to that constructed market context.

Separately, the community-analysis job can send batches of community message bodies to the AI service to identify recurring topics and questions. Account associations are used locally to exclude opted-out users; usernames and user IDs are not added to that payload. Pattern-based filtering removes email-like text, URLs, handles and phone-like strings and shortens messages, but cannot guarantee removal of every identifying detail. Avoid posting personal or sensitive information.

Results are stored as topic summaries for administrator review and potential guidance updates for later explanations. This application implements prompt-guidance improvement, not external model retraining. You can exclude your future messages from analysis through the community-analysis preference. Exclusion does not make existing public messages private or automatically remove previously produced summaries.

The AI request includes a setting asking the provider not to store the response. That setting alone is not a guarantee about provider logs, retention or training. No promise is made here that OpenAI or an intermediary never retains submitted data or never uses it for training.

5. Services and recipients

PROGY uses Lovable Cloud for its managed backend, with Supabase software and services configured for authentication, database access and real-time community updates. AI requests use Lovable’s AI Gateway and its configured model provider. Authorized administrators access information necessary for moderation and service operations.

Market catalogue and search requests go to Polymarket’s public API; a search sends your query text to that provider. Google handles Google sign-in if you choose it. The site also loads fonts from Google Fonts, creating requests from your browser that reveal connection information such as an IP address to Google. Authentication emails are sent through the managed authentication service.

These descriptions identify application data flows, not a guarantee about provider processing locations, contractual roles or onward processing.

6. Browser storage and technical records

The authentication client persists sign-in sessions using browser storage. The site stores your theme preference under progy-theme and, when acknowledged, the community-guidelines version and acknowledgment time under progy-community-guidelines-v1. The acknowledgment is not privacy consent. Clearing browser storage can sign you out and reset these preferences.

The application records operational errors and AI usage events. The AI request-event code omits user identifiers, but other account and insight records may contain user associations. No optional advertising or audience-tracking integration is intentionally added by this notice. Browser storage descriptions are not a claim that infrastructure or third parties use no cookies or other technologies.

7. Retention and account deletion

Account records support your use of the service. Your own community messages can be removed through available controls. Account deletion requires identity verification; the cleanup implementation removes watchlists, messages, preferences, credit records, entitlements and roles, removes matching early-access records, unlinks requester and administrative-history associations, and then deletes the sign-in identity and associated profile.

Cleanup is sequential. An interruption may leave partial cleanup and require a retry. Shared market information, generated insights and aggregated topics are not all deleted with an account. The pending reporting design removes linked reports when a message or reporter profile is deleted; this is not a guarantee of a functioning reporting workflow.

The background AI-improvement job includes cleanup of request events older than 180 days. This applies to that event table, not to all logs, insights or community records, and depends on the job running successfully. Cache durations are reuse settings, not a general deletion schedule. No promise is made of immediate deletion from all providers, logs or backups.

8. International processing

External services may process data outside your country. Processing locations and any required international-transfer safeguards depend on the applicable service arrangements. This notice does not assert a specific hosting region, adequacy decision or contractual transfer mechanism. Contact us for information about applicable arrangements.

9. Your rights

Where applicable, you may request access, correction, erasure, restriction and portability of your personal data, and object to processing based on legitimate interests. If processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. Rights can be subject to legal conditions and exceptions; we may need to verify your identity.

Send requests to hello@progy.tech. You also have the right, where applicable, to lodge a complaint with a competent data-protection supervisory authority, including in the place of your habitual residence, workplace or alleged infringement. No Data Protection Officer or privacy representative is designated by this notice.

10. Changes

This notice may be updated as the service and verified processing arrangements change. Paid subscriptions are not active; payment-provider processing and relevant disclosures will need to be added before payments launch.