Privacy policy

AnalyticsBridgeGPT is operated by Didier Alfaro. For privacy requests, contact dalfaro7@gmail.com. Effective October 11, 2026.

Information we process

We store your account email, company name, membership, Google account identifier when you sign in with Google, and subscription and report usage records. Passwords created on our website are stored as password digests. Google authorization credentials are encrypted in our database.

Connected analytics

With your consent, we access your selected GA4 and/or Search Console property (at most one per source) for your company using read-only Google permissions. We store their identifiers and verification metadata. Reports retrieve aggregate analytics from Google when requested and send the requested results to your authorized ChatGPT connection. We do not provide tools for modifying Google properties.

Temporary report storage

Successful reports with a retry ID may be cached as encrypted responses for ten minutes so a retry does not consume another free report. Expired responses are cleared when report requests run and when the server starts. Expiration prevents reuse; physical cleanup may occur later. Usage counts and request identifiers remain for quota and retry checks. We do not maintain a permanent analytics report archive.

Service providers

Render hosts the application and database. Google provides authentication and analytics APIs. When you connect ChatGPT, OpenAI processes the results sent to that connection under its own policies. If you use PayPal billing when available, PayPal processes the payment; we store subscription references and verification records, not your payment card details.

Your choices

You can disconnect Google and revoke ChatGPT access from your account. You can also revoke Google access in your Google account. Contact us for account deletion or data access requests; these requests are handled manually. Some payment and operational records may need to be retained to resolve transactions or meet applicable obligations.

Security and cookies

We use HTTPS on the hosted service, encrypted provider credentials, and company-scoped authorization. Session cookies support sign-in and request security. No system can guarantee absolute security. Do not send passwords or API secrets to our support address.