Your data, explained.

Who provides the service

Apex Foundry and SeerFlow are products of Tetheric Systems Private Limited. Apex Foundry is a marketing workspace, with SeerFlow as its current pilot brand. This notice describes Apex Foundry’s handling of information when you research a brand, create marketing materials or connect an account.

For privacy questions, access or correction requests, or deletion requests, contact hitarthdesai01@gmail.com. This notice covers Foundry. Connected platforms and AI services also have their own data practices.

Information used in the workspace

Work you provide

Prompts, brand briefs, approved facts, reference materials, draft copy, review decisions and feedback. These support the work you request and its revision history.

Public research

Website addresses, page text, source links, quotations, public social links, brand colours, logos and reference images. Public sources may include names or other information about people.

Creative outputs

Research notes, ideas, plans, copy, images, scripts, generated audio, rendered video, quality checks and approval history.

Connected accounts

Provider identity and email where returned, account or channel names and identifiers, granted permissions, roles, destination selections, token expiry and connection status. Ad-account reads may include currency, time zone and status.

Requested social reads

Instagram post identifiers, captions, permalinks, dates and available like/comment counts; LinkedIn member-level impressions, reach, reactions, reshares or comments, when the relevant account and permission are available.

Access credentials

Provider access and refresh tokens. Custom email connections can store an app password and server settings. Provider sign-in is handled by the provider; do not send us your ordinary account password.

Operational records

Actions, timestamps, status and error summaries, usage and cost estimates, campaign proposals and any configured delivery results. Saved performance observations and approved feedback can inform later ideas for the same brand.

AI processing and other services

OpenAI processes the prompts and relevant workspace context needed to generate or review text, images and narration. This can include recent conversation history, brand facts, source excerpts, feedback, reference images and the script to be spoken. Generated media is saved in the workspace.

The text-generation integration requests that responses are not stored as retrievable response history by OpenAI. This is not a promise of zero provider retention. OpenAI’s endpoint-specific retention and safety practices still apply; see OpenAI’s API data controls.

Local pilot sign-in relay: when enabled for LinkedIn, Meta Business or Instagram, this site receives the authorization code or cancellation response, together with the request state, and redirects the same browser to Foundry on the same Mac. The local app validates the connection request and exchanges the code. The relay does not receive the app secret or resulting account access tokens, and its application code does not store the response or log its query. Vercel, which hosts this relay, still processes the request under its infrastructure and logging practices. This relay is for the local pilot; it does not give remote users access to the local workspace.

Firecrawl receives search terms and public URLs for requested research and brand discovery. Those sites may receive the resulting page requests. Do not place private credentials in a research URL or prompt.

HeyGen receives a generated fictional-presenter image and generated narration only when a talking-avatar service is separately configured and requested. That optional service is distinct from Foundry’s locally rendered narrated reels.

An optional delivery service, configured by the workspace operator, can receive approved content, its selected account, channel and schedule for publishing. Connecting a platform does not configure or authorize this delivery service.

Connected providers receive the sign-in and account-read requests necessary for features you choose. Content sent to an external provider is subject to that provider’s processing and retention practices. Removing a local file does not automatically remove a provider’s copy.

Optional Google connections

Google connections are optional. Sign-in identifies the account and asks for the permissions associated with the selected feature.

• Gmail: an explicitly requested mailbox-header view can read message and thread identifiers, From/To/Subject/Date headers and unread status. It does not download message bodies or attachments. Email preparation creates a local draft; the current tool does not send mail.
• YouTube: Foundry uses YouTube API Services to discover the connected user’s channel and save its name, identifier and selection. Private-upload preparation does not upload a video.
• Google Ads: Foundry reads accessible account identifiers and account metadata so you can select an advertiser and prepare a local campaign proposal. It does not launch the proposed campaign.

Connected Google mailbox, channel and advertising-account reads are not automatically fed into the marketing AI prompts. If you independently paste information into an AI conversation, that submitted text follows the AI-processing flow described above.

The current pilot does not use Google account data to train general AI models, target advertisements or sell data. It uses that data for the connected features you request. See the Google API Services User Data Policy, including its Limited Use requirements, and Google’s Privacy Policy.

When you disconnect a Google account in Foundry, the app removes its locally saved access and identified connection data, then asks Google to revoke the grant when a readable token is available. The result distinguishes confirmed revocation from an unsuccessful or unavailable attempt. If Google does not confirm, remove the grant through your Google Account permissions.

Google revocation can affect more than one service. It removes the permissions granted to the same Google app project for that account, so Gmail, YouTube, Google Ads or another connection using that project may need to be connected again. Foundry also disconnects connections it can identify as sharing that account and sign-in setup within the workspace, including other brands. It cannot identify every connection that Google may affect.

Storage, access and retention

The current pilot stores workspace records and generated files in its local application storage. Connection secrets are encrypted. This does not mean every prompt, research record or creative file is encrypted. The workspace operator can access saved workspace content and operational records to run and support the pilot.

Saved work remains until removed by the workspace operator. The pilot currently has no general automatic deletion schedule. Disconnecting clears locally stored connection credentials and permissions and cancels pending deliveries that explicitly refer to that connection.

For Google connections, Foundry also removes the saved account identity, cached channel or ad-account details and selections, and the provider details in recognized connection-related activity records. It does this for the connections it can identify as sharing the grant. A record that a disconnect occurred remains. Earlier briefs, creative files and unrelated activity are preserved; removing those requires a separate request. Other providers currently use local credential removal without this Google-specific data-removal and revocation flow.

There is no published fixed retention period for every category in this pilot. To request removal of remaining records, use the data deletion instructions. Data already delivered to a platform or external service may require a separate request to that service.

External services may process data in locations outside your country. The pilot does not offer a guaranteed processing region or certified security standard.

Your choices

You can choose which account to connect, review the provider’s permissions, select a destination and disconnect it in Foundry. Google disconnect also attempts provider revocation; other providers require grant removal in their own settings. You can use provider settings yourself whenever you want to confirm that access has been removed. You can request access to, correction of, or deletion of workspace information at hitarthdesai01@gmail.com. Include the relevant brand or workspace and the account email or public channel identifier so the request can be located. Do not include passwords, access tokens or private customer lists.

Deletion requests are handled manually in the current pilot. Verification of your authority over the workspace may be needed before data is released or removed. See what disconnecting and deletion each cover.

Cookies and this information site

These information pages contain no advertising trackers, analytics scripts, embedded media or third-party fonts, and set no cookies. The application uses a short-lived browser cookie during account connection to tie the sign-in response to the browser that began it. Its purpose is connection security.

The service hosting this information site may process ordinary request and security information, such as network addresses and browser details, to deliver and protect the pages. Contact the team for information about hosting and support records.

Updates and contact

This notice describes the current pilot. The revision date appears above. Contact the team with questions about this notice or the handling of your information.