Skip to main content
Skip to content
Browse
FeaturesBrowse the product capability guides.PricingCompare coach and workspace plans.For coachesIndependent, online and hybrid coaching.Teams & WorkspacesFor gyms and performance teams comparing coaching software.Client adminReview fragmented client administration.Nutrition visibilityReview nutrition context before client reviews.Client operating systemReview the client-workflow evaluation guide.
Start free

Privacy and analytics settings

Repit uses essential storage to provide the service. Optional analytics starts only after you accept it, and you can change that choice below.

Who is responsible

Repit is the controller for the analytics information described on this page. Questions and privacy requests can be sent to support@get-repitapp.com.

Supabase processes the server-side attribution and conversion records that Repit stores. PostHog processes optional product analytics events. Repit does not start PostHog analytics until you accept.

What is stored

The consent cookie is necessary to remember your choice. Attribution and conversion-attempt storage is optional and is cleared when you reject or withdraw analytics consent.

Analytics storage names, purposes, fields, and retention periods
NamePurposeFields stored in cookieRetention
repit_consentRecords whether you accepted or rejected optional analytics.Format version, analytics choice, and decision timestamp.180 days
repit_attr_prodKeeps first-touch attribution on production after analytics is accepted.Version, attribution_id, creation time, and expiry.30 days
repit_attr_stagingKeeps test attribution separate from production after analytics is accepted.Version, attribution_id, creation time, and expiry.30 days
repit_conversion_attemptLinks an accepted analytics journey to a server conversion-attempt record.An opaque random attempt identifier only.30 days for the cookie; server records are purged after 90 days

PostHog event

After consent, the immutable marketing_conversion_started event stores landing path, referrer class, and bounded UTM values in PostHog, along with audience, CTA location, and destination. These acquisition fields are not stored in the attribution cookies.

Durable server record

The conversion-attempt record stores attribution_id, audience, intent, auth method, selected plan, status, and timestamps. As the journey progresses, it can also store user_id, new_user, and organisation_id. This Supabase record is separate from the opaque identifier in the conversion-attempt cookie.

Scope and retention

On production, Repit scopes the consent and optional attribution cookies to .repit.coach so your choice applies across Repit subdomains. Local development uses host-only cookies.

Consent is retained for up to 180 days. Attribution cookies are retained for up to 30 days. Repit purges server-side conversion-attempt records after 90 days. Rejecting or withdrawing removes the optional browser state immediately and requests early deletion of the attempt cookie.

International transfers

PostHog states in its public DPA that it may process customer personal data outside protected regions, including in the United States. It lists the EU Standard Contractual Clauses, the UK transfer addendum, Swiss adaptations, and participation in the applicable Data Privacy Frameworks as transfer safeguards.

Supabase states in its public DPA that applicable transfers use the EU Standard Contractual Clauses and that the UK transfer addendum applies to transfers covered by UK data-protection law. Its privacy notice also identifies the United States and Singapore as possible processing locations.

Read the current public vendor terms in the PostHog DPA and the Supabase DPA.

Change your analytics choice

Rejecting analytics withdraws consent and clears optional analytics state. Accepting allows Repit to start optional analytics on this browser.