Privacy | YieldPivot

What we collect

Account information you provide, including email.
Profile and usage data you enter while using the service.
Billing status and subscription identifiers from Stripe.
Limited request, security, and service-performance information processed by our hosting, database, and email providers.

How we use data

To operate YieldPivot features and secure the service.
To support subscriptions, billing state, and plan access.
To communicate important service and account information.
To protect, troubleshoot, and understand the reliability of the service.

Service providers and analytics

YieldPivot uses Supabase for account and application data, Stripe for billing, Cloudflare for hosting, traffic delivery, and security, and Resend and other email providers for service messages.

Optional browser product analytics and marketing-attribution collection are currently disabled by default. Cloudflare browser performance analytics is also disabled. Cloudflare still processes network requests needed to deliver and protect the service and may provide aggregate traffic counts. Those counts are not treated as individual people or customers.

Eligible links into the application use fixed page and button codes. The application counts accepted navigation requests without cookies, browser storage, account identifiers, IP addresses, full URLs, or free-form referral values in the measurement record. These counts are not unique people or confirmed clicks; request headers can be forged or replayed. They are not linked to an individual account.

Separately, the application records a first actionable recommendation event for an authenticated account to assess whether the tool is useful. It stores only approved minimal event properties; optional PostHog delivery remains disabled. This account event is not joined to the public navigation count.

Payments

Billing data is processed through Stripe. YieldPivot does not store full payment card details.

Data retention

Account and product data is kept while your account is active and as needed to operate the service, resolve disputes, meet legal obligations, and maintain security. Provider logs and billing records follow the applicable provider plan, contract, and legal requirements.

Internal daily-report artifacts expire after 45 days. Resend states that production backups are kept for 30 days. Aggregate transition data follows Cloudflare Analytics Engine's documented three-month retention. Some historical user-linked application-event or attribution records currently follow the account lifecycle rather than a separate time limit.

Contact