Your data, plainly explained

At a Glance

Sells your data

Never

Advertising

None — we do not run ads or cross-context behavioral advertising

Tracking cookies

None

Analytics

Optional PostHog page views and feature events; UK/EU/unknown: no script or storage until Accept; US: Privacy choices + GPC, no European banner; no replay, heatmaps, or autocapture

AI features

Only run when you request them; notes and quotes require the relevant feature choice. We do not invent your 1–5 score.

Identity

Clerk account when signed in; optional opaque PostHog id; check-in content is score + optional note; managers do not see names

Anonymous use

Supported without an account; signed-out history is tied to a random device ID

Export

You can export your own record from Settings. Logs are not public unless you choose to share selected fields.

Deletion

Individual entries can be deleted; account deletion starts a 30-day purge process

Organization data

Workspace-linked records are de-linked and may remain as anonymized aggregates

Minimum age

18 and older only; no child or teen accounts

Transfers

US-based infrastructure and sub-processors with safeguards where required

Contact

privacy@proudnotproud.com

Change optional analytics any time on this device.

Data controller

Who We Are

ProudNotProud is operated by Clamp Studios LLC, a California limited liability company. For the purposes of the UK GDPR and EU GDPR, Clamp Studios LLC (operating as ProudNotProud) is the data controller responsible for your personal data. If you have questions about this policy or your data, contact us at privacy@proudnotproud.com.

Categories of personal data

What We Collect

We collect what is needed to provide the features you use. Some data comes from you, some is created by the service, and optional data is collected only when you enable the relevant feature.

• Device identifier — a randomly generated ID stored on your device. When you are signed out, it is used to associate check-ins with that device without your name or email.
• Account data — if you sign in, Clerk provides your account identifier, email address, display name, profile settings, and optional profile fields such as username, company, title, and avatar. That account identity is separate from check-in content (score plus optional note). Employers and managers do not see names on default Team aggregates.
• Check-ins and sessions — the 1–5 work-pride score you enter (we do not invent that score), timestamps, optional encrypted notes, session start/end data, source, tags, channels, variables, and any workspace or organization code attached to a check-in.
• Location data — only when location is enabled, a browser location, saved home location, or location override can provide coordinates and place names. You choose no location, country, state, or city display in Settings.
• Career and workspace data — career entries, clients, channels, friends, team memberships, shared notes or quotes, and other records you choose to create or join. Friend sharing is opt-in and mutual; either person can end the connection.
• Connected-service data — depending on what you connect, this can include Google Calendar selections and prompts, optional Slack link status, Clockify context used by the extension, and voice or automation tokens.
• Product analytics — where allowed, PostHog receives limited page-view and feature-event data. Signed-in events use an opaque account ID, not your name or email. We do not send notes or typed entry content to analytics. This optional identifier is not a check-in score.

Purposes and legal bases

How We Use Your Data

We process your data for the purposes below. The legal basis depends on the feature and your location, including the contract necessary to provide the service, consent for optional features, legitimate interests for security and operation, and legal obligations.

• Provide and secure the service — store check-ins, maintain sessions, show history, operate community and workspace features, prevent abuse, and keep the platform reliable.
• Run optional features you turn on — location display, community profile visibility, reminders, notifications, integrations, voice logging, and exports.
• Provide AI features you request — process the relevant check-ins to generate an AI Brief, answer a Studio question, parse a voice check-in, or run another feature you actively start.
• Measure product use — where optional analytics is allowed, process limited page views and explicit feature events. Analytics is never used for advertising or to make legal or similarly significant decisions about you.
• Meet legal obligations — respond to valid legal requests, maintain records where required, and handle rights requests.
• We do not use your data for automated decision-making or profiling that produces legal or similarly significant effects.

Third parties and sub-processors

Who We Share Data With

We do not sell your data or share it for cross-context behavioral advertising. We share data only when needed to operate a feature, when you choose to share it, or when the law requires it.

• Infrastructure and email providers — cloud, database, authentication, transactional email, and telephony providers process data on our behalf to host the service and send account-related messages.
• Product analytics provider — when analytics is allowed, PostHog processes pseudonymous page views and feature events. Session replay, heatmaps, autocapture, and console-log capture are disabled.
• AI providers — Anthropic processes check-ins for the AI Brief and Studio features; OpenAI processes voice audio, transcripts, or requested insight/voice content. Notes and quotes are included only when the feature requires them and, for private career insights, only when you enable the notes-and-quotes option. These providers are not authorized to use this content to train their models for this service. Google’s Gemini receives your headshot photo when you generate AI avatars.
• Community feed — if you enable community sharing, the fields you choose, such as username, avatar, company, title, pride level, and selected location granularity, can be visible to other users.
• Teams and workspace administrators — by default they see anonymous aggregates only (minimum 5 contributors), not names or individual entries. A specific note or quote is visible to a workspace only when you deliberately share that entry. Organization-linked entries can remain in anonymized aggregate records after account deletion.
• Connected services — Google Calendar, Slack, Clockify, and voice or automation services receive only the data needed for the connection or action you request. Their own privacy policies also apply.
• Payment providers — Stripe processes card subscription payments. Some legacy subscription records may involve PayPal. We receive billing and subscription identifiers and status, not your full card number.
• Law enforcement — we may disclose data if required by valid legal process. Where permitted, we will notify you before complying.

Retention and deletion

How Long We Keep It

We keep data only as long as needed for the service, the purpose for which it was collected, or a legal obligation. Retention differs between an individual record, an account, and an anonymized organization aggregate.

• Individual check-ins and account data — retained while your account is active. You can delete individual entries from the product.
• Account deletion — deletion starts immediately, cancels active subscriptions, and schedules an irreversible hard purge after a 30-day grace period. The grace period supports recovery and cleanup jobs; it is not a promise that the account remains available.
• Organization-linked check-ins — when you delete an account, entries associated with a workspace are de-linked immediately so they can remain only as anonymized organization data. They are not restored to your personal history.
• Anonymous check-ins — signed-out entries are tied to a random device ID, not an account. Clearing browser storage changes the device ID but does not delete records already received by our servers. Anonymous users do not have the authenticated export and deletion controls; contact us for a privacy request.
• Server logs, session tokens, and integration records — kept for the period needed for security, authentication, reliability, or the connected feature, then expired, revoked, or deleted according to those operational needs.
• Legal retention — limited records may be retained longer when required to establish, exercise, or defend legal claims or comply with law.

What we store on your device

Cookies and Local Storage

We use a small amount of functional browser storage to make ProudNotProud work. Clerk session cookies, the anonymous device ID, preferences (including levels and reminders), and extension state are necessary-service storage. They are disclosed here and are not sold as analytics.

• Authentication cookie — Clerk uses an HttpOnly, Secure session cookie to keep you signed in. It is not readable by page JavaScript.
• Anonymous device ID — local storage holds the random ID used to associate signed-out check-ins with your device.
• Preferences — local storage holds settings such as reminder choices, location granularity, custom level labels, colors, team codes, and other product preferences.
• Connection state — the web app and browser extension may store local connection or session state needed to complete a sign-in, integration, or workspace flow. Sensitive tokens are handled by the relevant authenticated flow and can be revoked from Settings where supported.
• Analytics storage — when PostHog is allowed, it keeps a random browser identifier in local storage. For UK, EU, and unknown-region visitors, the PostHog script is not loaded and no PostHog storage is written until you Accept. US visitors do not see a European Accept/Reject banner; they may disable analytics from Privacy choices, and GPC keeps it off.
• Privacy choice — your analytics choice is stored on this device with a version and timestamp. It can be changed from the Privacy choices control.
• No advertising or social trackers — we do not load ad networks, advertising cookies, or social-media pixels.

CCPA / CPRA and GPC

California Privacy Choices

California residents can control optional analytics from Privacy choices. We do not sell personal information or share it for cross-context behavioral advertising.

• Global Privacy Control is treated as an opt-out of optional analytics. When GPC is active, PostHog stays disabled.
• Privacy choices can disable optional PostHog analytics at any time. This choice applies on the device where it is made.
• To exercise other California rights, email privacy@proudnotproud.com with “CCPA Request” in the subject line. We will verify and respond within the period required by law.
• We do not discriminate against you for exercising privacy rights.

Where your data goes

International Data Transfers

Our infrastructure and service providers may process data in the United States and other countries where they operate. If you are in the UK or European Economic Area, this can involve a transfer to the US.

• Where required, transfers to US sub-processors use Standard Contractual Clauses or equivalent UK safeguards.
• We assess recipient protections and apply contractual and technical measures appropriate to the data and service.
• If a transfer mechanism changes, we will take additional measures or stop the transfer where required.

Permissions and supported sites

Browser Extension

The ProudNotProud Chrome extension provides quick check-ins and optional integrations without requiring you to open the web app. Its permissions are used for the features described below.

• Permissions — the extension requests storage, activeTab, tabs, alarms, and idle. It also declares host access to ProudNotProud endpoints and statically declared content scripts on supported pages. It does not request the Chrome scripting permission, and chrome.scripting is not used.
• Supported-page scripts — the extension reads page content on Clockify (timer DOM) and, where those scripts inject, on Timely pages (timer DOM). Where applicable, it also reads LinkedIn post text. It also shows check-in and badge UI, including on pages matched by <all_urls> in the live Store 3.0.14 build. There is no scripting permission. The extension is not a general-purpose browsing-history collector.
• Check-in data — a check-in level and optional note submitted through the extension are handled like a web check-in and sent to ProudNotProud servers.
• Local extension storage — authentication and recent check-in state can be cached in the browser so the popup and supported integrations work.
• No advertising analytics — the extension build does not initialise the web app’s PostHog analytics bootstrap. Requests to ProudNotProud endpoints still follow this policy.
• No remote code — extension logic is bundled with the installed extension and is not downloaded as executable code from a remote server.
• You can remove the extension at any time. Removing it does not delete check-ins already sent to ProudNotProud; use the account controls or contact us for those requests.

18 and older only

Children’s Privacy

ProudNotProud is for people 18 and older. We do not knowingly collect personal information from anyone under 18, and we do not offer child or teen accounts.

• Age check — we ask for your date of birth at sign-up and do not create accounts for anyone under 18.
• If we learn that someone under 18 has an account or has given us personal information, we will close the account and delete the data.
• Questions or concerns — if you believe a person under 18 is using ProudNotProud, email privacy@proudnotproud.com with “Under-18 Concern” in the subject line.

Optional features and billing

Payments and Connected Services

Some individual and Teams features require a paid plan or an optional connection. We only activate those flows when you request them, and you can disconnect supported services from Settings.

• Billing — Stripe processes card payments and subscription renewals. We store plan, subscription, customer, and billing-period status needed to provide paid features and stop renewals. We do not store full payment-card numbers.
• Calendar — Google Calendar can provide selected calendars and today’s prompts when you connect it. Disconnecting removes the connection from ProudNotProud.
• Work tools — Slack and Clockify connections can send or receive the check-in context needed for the feature you enable.
• Voice and automations — voice tokens and personal API tokens support voice logging, Google Home, IFTTT, Siri Shortcuts, or similar direct check-in flows. Revoke tokens from Settings where available.
• Third-party terms — the provider’s own terms and privacy policy apply to data that remains with that provider. ProudNotProud does not control a connected provider’s independent processing.

Your Rights

Under UK GDPR and EU GDPR, you may have the rights below. To exercise a right, contact privacy@proudnotproud.com. We will respond within the period required by applicable law. There is no fee unless a request is manifestly unfounded or excessive.

• Right to Access Art. 15

  Request a copy of the personal data we hold about you.

• Right to Rectification Art. 16

  Ask us to correct inaccurate data or complete incomplete data.

• Right to Erasure Art. 17

  Request deletion where there is no compelling reason to continue processing it.

• Right to Portability Art. 20

  Receive eligible data in a structured, machine-readable format.

• Right to Restriction Art. 18

  Ask us to suspend processing while a dispute is resolved.

• Right to Objection Art. 21

  Object to processing based on legitimate interests, subject to applicable exceptions.

Complaints and Supervisory Authority

If you believe we are not handling your data in accordance with this policy or applicable law, contact us first at privacy@proudnotproud.com. You may also complain to the supervisory authority in your country. In the UK, this is the Information Commissioner’s Office (ICO).

Changes to This Policy

If we make a material change — such as collecting a new category of data, adding a new class of provider, or changing a legal basis — we will update this page and use an appropriate notice before the change takes effect. The effective date at the top of this page reflects the current version.