GROWTH ENGINEER · LEGAL
Privacy Policy
Last updated: October 28, 2026
This policy explains how Growth Engineer handles information when you use our website, marketing workspace, and connected-account features.
1. Who operates Growth Engineer
Growth Engineer is operated by Peter Foy. Contact peter@growthengineer.ai about privacy, access, or deletion. For information we collect to operate the service, Peter Foy is the data controller. If an organization uses a workspace to process information about other people, that organization determines its own purposes for that information; contact it about its use of your data.
2. Information we handle
- Workspace information: project descriptions, tasks, skills, routines, notes, links, reviews, metrics, and other content you or your authorized agents submit.
- Account and support information: login credentials or their protected representations, session identifiers, contact details you provide, and correspondence.
- Connected accounts: account identifiers, authorization credentials, permissions, connection status, and the data returned by the enabled integration described below.
- Technical information: request times, IP addresses, browser information, errors, and activity records used to deliver and protect the service. Hosting and integration providers may also keep technical logs.
3. What integrations access
Connecting an account is optional. The current workspace integrations read data; they do not publish posts, send messages, or purchase advertising. A provider’s consent screen may grant broader permissions than the operations currently exposed by Growth Engineer, particularly when using a development test app.
- TikTok: with your authorization, we request your account identifier, display name, username, follower and following counts, total likes, and public video count. We use these to identify the account and display its performance. The current integration does not collect private messages or individual viewer identities.
- YouTube: Growth Engineer uses YouTube API Services to retrieve your channel identifier, channel name, and current subscriber, view, and video counts. See the Google Privacy Policy.
- App Store Connect: when you supply API credentials, the current integration lists apps accessible to those credentials, including app names, identifiers, bundle IDs, SKUs, and primary languages. Download and revenue report collection is not currently enabled.
Current integration reads display results without automatically adding those results to the workspace’s metric history. You or an authorized agent may separately save observations or other records. Integration providers may retain request logs independently of the workspace.
4. How we use information
We use information to provide the workspace, connect accounts you authorize, display reports, execute requests from agents you connect, preserve work history, answer support requests, and prevent misuse. We do not sell personal information or use connected-account data for advertising targeting. We do not use connected-account data to train general-purpose AI models.
Where data-protection law requires a legal basis, we rely on performance of our agreement to deliver requested services, legitimate interests in security and support, consent where required for optional processing, and legal obligations where applicable. You can withdraw consent without affecting earlier lawful processing. Declining account access prevents the related integration from working.
5. Service providers and agents
We use Nango for connected-account authorization, credential storage and refresh, and API requests. We use Cloudflare for the public website and hosted workspace, including storage of workspace records and authentication information. Other infrastructure providers used to host a deployment may process technical information necessary to serve it. Development workspaces and migration backups may remain on the workspace owner’s computer.
Agents and tools that you authorize can access the projects and integration results made available to their access keys. Data returned to an external AI tool is processed by that tool under your arrangement with its provider. Connecting an integration does not, by itself, send all its data to an AI provider. Only give workspace access to tools and people you intend to authorize.
We may disclose information when legally required or reasonably necessary to address fraud, security incidents, or protection of rights. Providers may process information outside your country, including outside the EEA. Where required, transfers must use an applicable adequacy decision or contractual safeguards. Contact us for details about the providers and safeguards applicable to your deployment.
6. Retention, revocation, and deletion
Workspace records are retained while needed to provide your workspace and its history. Archiving a task hides it from the active board; it is not permanent deletion. Credentials remain with the connection provider while the connection is maintained. Support and technical records are retained only as needed for their purpose, legal obligations, or resolving disputes.
To request deletion of a connection, stored integration data, or workspace information under our control, email peter@growthengineer.ai and identify the relevant workspace and account. Do not include passwords or API secrets. We may need to verify your authority before acting. Requests are handled manually; there is no automatic deletion button in the current workspace. We will delete stored YouTube API data covered by a verified user deletion request as soon as possible and within seven calendar days.
You can also revoke Google access through your Google account’s third-party connections, revoke TikTok access in TikTok’s app permissions, or revoke an Apple API key in App Store Connect. Revoking provider access stops future authorized access but does not itself erase records already saved in a workspace or copied to an external agent. Contact us for deletion of copies we control. Locally hosted workspace files and copies held by tools you independently use must also be managed by their respective owners.
7. Cookies, storage, and security
The workspace uses a session cookie for login and browser storage for preferences such as light or dark appearance. These policy pages do not include advertising or analytics scripts. External services have their own cookie practices. We restrict access to credentials and workspace data, but no system can guarantee complete security. Keep access keys private and revoke keys you no longer need.
8. Your rights
Depending on applicable law, you may request access, correction, deletion, restriction, portability, or object to processing of your personal information. You may withdraw consent and complain to your local data-protection authority. Contact us at the address above to exercise your rights. Growth Engineer is intended for adults and is not directed to children. We do not use connected-account statistics to make decisions with legal or similarly significant effects on individuals.
9. Changes
We will update this page when our practices change and change the date above. Material changes to connected-data use will be explained before that new use begins, with additional consent where required.