Privacy Policy

1. Introduction

This policy covers the information processed through the Services. Third-party services that you connect to PDD Cloud have their own privacy practices. Your organization may also control information submitted through an organization-managed account or repository.

2. Information We Collect

A. Account, Profile, and Authentication Information

PDD Cloud uses Firebase Authentication and may support GitHub, Google, or email-based sign-in, depending on the available sign-in flow. We receive account identifiers and profile information such as your user ID, name, email address, username, profile image, and authentication-provider information. Authentication providers manage the credentials used with their services; PDD Cloud does not receive your GitHub or Google password. You may also provide profile information such as a display name, biography, and avatar.

B. Employment Applicant Information

When you apply for a role, we collect the contact information you provide (including name, email address, and phone number), your resume, GPA and education information, LinkedIn and GitHub profile links, and your answers about the role, AI coding tools, and our repository. We use this information to receive, review, and communicate about your application and recruiting process.

Employment applicant information is available to personnel involved in recruiting and may be processed by secure service providers that host, store, or support the application process, including Google Cloud and Firebase as described below. We retain it for as long as reasonably necessary for recruiting, recordkeeping, security, and legal purposes. You may request deletion, but some information may be retained where necessary for those purposes or as required by law.

C. Applications, Assessments, and Event Information

• Waitlist applications: Your reason for applying, intended use, project description, organization, additional information, application status, and review notes.
• Migration assessments: Contact and company information, role, current and target technologies, architecture, cloud and database choices, usage and spending ranges, timeline, goals, traffic, and other details you submit for assessment.
• Hackathon and event information: Registration role and status, participant or volunteer applications, profile links, team membership and invitations, project descriptions, repository URLs, submission checklists, compliance results, judging scores and feedback, and communications.
• Carpool matching: For events that offer this feature, the selected transit hub, travel role, departure time, available seats, and the name and email copied from your registration.

D. Prompts, Code, Marketplace, and GitHub Information

We process prompts, messages, code, tests, configurations, input and output data, generated results, errors, quality measurements, model choices, token or cost information, and examples that you submit or generate through the Services. Marketplace records may include a listing's title, description, tags, visibility, price, quality metrics, purchase records, creator share, and platform share.

If you install or use the GitHub App, we process information available under the installation and repository permissions you grant. This can include your GitHub identity and avatar, installation and repository identifiers, repository content and source snapshots, repositories, issues, pull requests, comments, labels, workflows, project-board information, job instructions, generated changes, job status, logs, feedback, and results. The Service may create or update branches, commits, pull requests, comments, labels, workflows, issues, and project items when you request or configure those actions.

E. Billing, Credit, and Usage Information

We process PDD Credit balances, purchases, bonuses, marketplace transactions, model and compute usage, creator sales, and account ledger entries. For card purchases, Stripe processes the card details and returns identifiers and limited payment-method information. PDD Cloud may store a Stripe customer ID, payment-method ID, payment or checkout ID, amount, currency, and card brand, last four digits, and expiration. We also store auto-buy settings such as whether it is enabled, its balance trigger, purchase amount, monthly limit, and selected payment-method ID.

F. AI Connection and Credential Information

If you connect your own AI provider account, API key, or subscription credential, we process the authentication material and connection metadata needed to route requests. User-facing status responses use credential identifiers, fingerprints, health information, allowed models, and similar metadata rather than returning the reusable secret.

G. Contact and Communications Information

Our contact-management tools may process names, email addresses, Discord identifiers, GitHub usernames, contact sources, labels, funnel stages, interests, summaries, interaction counts, sentiment, notes, message content, timestamps, and unsubscribe status. This information may come from communications you send, product account, waitlist, or migration records, authorized inbound webhooks, or contact lists imported by authorized administrators.

H. Information Collected Automatically

We collect service and diagnostic information such as pages and features used, timestamps, browser and device information, network identifiers, referring information, authentication and job events, errors, and performance data. Google Analytics also measures visits and interactions on PDD Cloud pages.

3. How We Use Your Information

We use the information described above to:

• Authenticate users, maintain profiles, administer access, and review waitlist applications and migration assessments.
• Run requested prompt, code-generation, testing, marketplace, GitHub, migration, hackathon, judging, and carpool features.
• Route requests to the selected AI provider, retrieve relevant marketplace examples, measure quality, and return generated results.
• Process card payments, maintain credit balances and transaction records, store auto-buy settings, and calculate marketplace pricing and creator shares.
• Operate events, teams, submissions, compliance checks, leaderboards, judging, and participant communications.
• Secure, monitor, debug, audit, and improve the reliability and usability of the Services.
• Send transactional messages, event updates, service notices, and communications consistent with your available email preferences.
• Manage contact relationships, record communication history, classify contacts and interests, draft communications, deliver email or Discord messages, and honor unsubscribe preferences.

4. Cookies and Tracking Technologies

PDD Cloud and its service providers use cookies, browser storage, and similar technologies. Firebase and browser storage help maintain authentication state. PDD Cloud sets a presence-only __session cookie that indicates whether a signed-in session is present; it does not contain your Firebase credential. Local storage may remember language and theme preferences, popup dismissals, and GitHub request or job identifiers. Google Analytics uses measurement technologies to understand page visits and interactions.

You can clear or block cookies and local storage through your browser. Doing so may sign you out, reset preferences, or prevent parts of the Services from working as expected.

5. Data Sharing and Third-Party Services

We disclose information to the following parties when needed to operate the features you use:

• Google Cloud and Firebase: Authentication, application hosting, databases, object storage, server functions, task and message processing, logging, and protected credential storage.
• Authentication providers: GitHub and Google exchange authentication and profile information when you choose their sign-in methods.
• GitHub: The GitHub App reads and writes information within the repositories and resources covered by the permissions and repository access you grant.
• AI providers: Prompts, messages, code, repository context, issue or pull-request information, examples, settings, requested output formats, and account, credit, or transaction context used by account-aware assistant features may be sent to OpenAI, Anthropic, Google, or another configured provider. Contact dossier and interaction context may also be sent for contact classification or communication drafting. The provider varies based on the model, feature, Service configuration, and any provider connection you supply.
• Stripe: Stripe receives card and checkout information to process purchases. Checkout may prepare a card for potential future off-session use. PDD Cloud receives transaction and limited payment-method details as described above and stores the auto-buy preferences you configure.
• Google Analytics: Google receives measurement information about page visits and interactions.
• Brevo: We send recipient addresses, message content, templates, and personalization fields to deliver email communications and manage suppression preferences.
• GitHub CRM: Separate from a user-installed GitHub App, PDD's configured CRM repositories and projects may receive contact names, email addresses, Discord identifiers, GitHub usernames, labels, funnel stages, summaries, interests, interaction counts, sentiment, notes, and communication history in issues, comments, and project metadata.
• Discord: Discord receives recipient, channel, and message information when PDD sends direct messages or processes inbound Discord communications.

Information may also be shared with people using the collaborative or public features you choose. Public marketplace listings and event galleries may display creator, team, project, repository, submission, compliance, score, feedback, or leaderboard information. Team members, event administrators, and assigned judges can receive information needed for their roles. Matched carpool participants receive the names, emails, travel roles, and shared transit-hub and departure information of other members in their match.

6. Data Retention

No single retention period applies to every category of information. Retention depends on the feature and record, including whether information is needed to maintain an account or listing, complete a requested job or event, preserve billing and transaction records, secure and audit the Services, resolve disputes, or meet legal obligations. Some operational records use automated expiration or deletion controls, while other account, content, transaction, and audit records remain until they are deleted or no longer needed for those purposes.

Uninstalling the GitHub App or revoking a provider connection stops new access through that authorization, but may not automatically delete job, transaction, audit, or content records already stored by PDD Cloud. Withdrawing from event carpool matching removes the current carpool preference from that feature. Contact us about a specific record or deletion request.

7. Data Security

We use measures designed to protect information, including authentication and role-based access checks, server-side authorization, input validation, redaction of selected sensitive fields, restricted credential systems, and controls that limit GitHub, event, team, and administrative actions to authorized users. No method of electronic transmission or storage is completely secure, so we cannot guarantee absolute security.

8. Your Rights and Choices

The Services provide controls that let you edit supported profile and account settings, choose whether a marketplace contribution is public, disable saved auto-buy preferences, withdraw from event carpool matching, uninstall the GitHub App, revoke an AI provider connection, sign out, and clear browser cookies or local storage. Communication preferences and unsubscribe controls are available for supported email programs.

You may contact us to request access, correction, or deletion of personal information or to ask how a request applies to your account. We may need to verify your identity. Some information may remain where needed for transaction records, security, abuse prevention, dispute resolution, or other legal obligations. Any rights required by applicable law may vary based on your location and the circumstances of the processing.

9. Children’s Privacy

General account eligibility is described in our Terms of Service. If PDD offers a specific event that permits participation by a minor, that participation must follow the event-specific participation documents and any required parent or guardian consent process. If you believe a minor's information was submitted outside an authorized event process, please contact us.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the “Last Updated” date. If a change is material, we may also provide notice through the Services or by email.

11. Contact Us

If you have questions, concerns, or a privacy request, contact us at legal@promptdriven.ai. For the rules governing the Services, see our Terms of Service.