Privacy Policy

Operator and contact

Legal operator

Shay Pinhassi

Privacy, terms and support

[email protected]

For privacy, access, correction, deletion or support requests. Do not send passwords, API keys or authentication codes.

Who is responsible

Growth Studio AI is operated by the individual named in the operator and contact section on this page. Use that contact for privacy, data-access, correction or deletion requests. Do not send passwords, API keys or authentication codes.

Account and workspace information

Account information includes your email, authentication identifier and profile information supplied when you register or sign in. Workspace information includes the business details, preferences, sources, drafts, feedback and membership information you choose to provide. Authentication and security records support sign-in, access control and troubleshooting.

Google sign-in

When you choose Google sign-in, Google and Supabase authenticate you. The sign-in flow can receive your Google account identifier, email, name and profile image. These identify your account and support your profile and session; Growth Studio does not receive your Google password. Sign-in alone does not request Gmail, Drive, YouTube or Analytics access.

Optional connected accounts

Connecting a marketing account is separate from signing in. Its authorization screen must explain the requested access. Native social and Google Analytics connections are not active in the current testing release. The following sections describe the planned read-only pilot, not a currently enabled service. Retention, deletion handling, provider configuration and legal review must be resolved before activation.

Planned Google Analytics read-only data

The planned pilot reads the names and identifiers of Analytics accounts and properties you can access so you can choose a property. For that selected property and reporting range, it reads daily sessions, engaged sessions and page or screen views, together with the property's reporting timezone and data-quality information. Saved reports include those numbers, the property identifier, dates, observation time and quality warnings. The pilot's report query does not request individual visitor identifiers, email addresses or browsing histories. It does not change your Analytics settings.

Planned Facebook and Instagram read-only data

The planned pilot reads the names and identifiers of Pages you can manage and identifiers of linked professional Instagram accounts so you can choose an account. Facebook reports contain Page content views, post engagements and unique content viewers, preserving the provider's daily period boundaries. Instagram reports contain views, total interactions and reach for the requested range. Saved reports include the selected Page and account identifiers, reporting range, observation time and coverage or missing-data information. These metrics may include paid activity; they are not an organic-only or advertising-management report. The pilot does not read private messages or publish, edit, delete or moderate social content.

Why the pilot keeps reports and connection records

The planned connection uses authorization credentials to request your selected read-only data. Credentials are held separately from saved reports in encrypted server-side storage, with connection, permission, expiry and security records needed to manage access. Reports support the workspace's analytics view and later reopening of the same saved observation. Authorized workspace members can see reports according to their role; the public website does not expose them. Supabase provides authentication and database storage, Railway hosts the application, and Google or Meta processes the authorized API requests. This pilot does not send connected-account reports to an AI provider or use them for advertising, sale or generalized model training.

Disconnecting and revoking access

The planned disconnect action removes the active connection in Growth Studio. It does not automatically revoke the permission at Google or Meta, delete your Growth Studio account, erase saved reports or prove that all retained credentials and backups have been removed. Provider permission can be withdrawn separately through the provider's connected-app controls. Deletion requests must be handled separately, including any retained records and backup obligations. Do not treat a disconnected label as a deletion receipt.

Access requests and saved-report downloads

For the planned pilot, saved analytics reports are retained until the workspace owner requests deletion; there is no automatic report-expiry interval. This report policy does not set retention periods for credentials, logs, request receipts or backups. A deletion request is not confirmation that deletion is complete. You can use the contact on this page to request access, correction or deletion; do not include credentials in the message. Request handling needs identity and workspace-authority verification before protected data is released or removed. Saved-report download and removal controls have only been verified locally with generated test data and are not active in the hosted release. When made available, a saved-report file covers only the reports named in the request, not all workspace or account data. A browser download is not confirmed delivery, and removing reports is not completion of every privacy obligation. Credential, log and request-receipt retention, credential cleanup, backup expiry and the complete request-handling process remain under review.

Hosting logs and deletion limits

Railway, our application host, states that application, build, deployment and HTTP logs are stored in US West for 90 days. Shorter plan viewing windows do not shorten storage. Individual entries cannot be deleted or redacted early, and HTTP logging cannot be disabled per service or route. Request metadata can include IP address, user agent, path, status and timing. Railway states that its HTTP logs and internal edge telemetry exclude query strings, Cookie and Authorization headers, request and response bodies, and redirect Location headers. Application output is captured separately, so those exclusions are not a guarantee about everything an app might log. Deleting saved reports does not delete hosting logs. Cloudflare capture and retention, other provider terms and final runtime controls remain under review.

Service providers and workspace access

The current testing infrastructure uses Supabase for authentication and database services, Railway for application hosting, Resend for authentication email delivery, and Cloudflare for domain and configured web protection services. These providers process information needed for their services, such as account, email, network or request data. Members can access workspace information according to their permissions. Operational access must be limited to service and security needs; this draft does not claim a finalized international-transfer or subprocessor agreement.

AI and Google data

Live Hermes execution is not active in this testing release. Before enabling an AI provider, the app must explain what content it receives and the applicable provider settings and terms. Google sign-in is not consent to train AI models or to share your connected-account data with an AI provider. No advertising, data sale or generalized model-training use is authorized by sign-in.

Cookies and browser storage

Authentication cookies maintain your session. Interface preferences and onboarding progress can use browser storage; saving the optional setup draft stores it in the current browser tab for up to one hour after the last save. Signing out and removing site data are different actions. This notice does not ask you to consent to advertising or optional tracking.

Security, retention and deletion

The app uses access controls, workspace separation and additional authentication checks for protected actions. No system can guarantee absolute security. The planned saved-report retention policy is described above. Retention periods for other records, backup expiry and identity-verified deletion handling are awaiting review. Revoking Google access stops that authorization but does not by itself delete your Growth Studio account or existing workspace records. Use the contact on this page to request access, correction or deletion; the final handling process must be confirmed before public launch.

Policy updates

This draft reflects the current testing scope. Material changes to data handling, connected services or AI processing require updated disclosures before the new use begins. The final policy must include the rights and legal disclosures applicable to the people and regions served.