Effective Date: October 24, 2026
Last Updated: October 24, 2026
Privacy at a Glance
This summary is provided for convenience. The complete Privacy Policy below provides additional detail and controls if there is any inconsistency.
- You retain your rights in the content you submit to IdeaFoundry.
- IdeaFoundry supports Public Content, Shared Content, and Private Content.
- Shared and Private Content are not made public merely because you use IdeaFoundry.
- IdeaFoundry does not use Shared or Private Content to train or improve foundation models or general-purpose AI models unless you separately and affirmatively direct or consent to that use.
- IdeaFoundry records certain workflow, authorization, security, and provenance information to operate and protect the coordination network.
- Provenance does not give IdeaFoundry ownership of your underlying work, contributions, or User Content.
- When you choose to use IdeaFoundry through a third-party AI assistant or other Third-Party Host, that provider has its own privacy practices.
- IdeaFoundry does not sell personal information or share personal information for cross-context behavioral advertising.
- IdeaFoundry does not use User Content to infer sensitive characteristics for advertising, unrelated profiling, or eligibility decisions.
- Payment functionality may involve independent Payment Providers such as Stripe.
- You may have rights to access, correct, delete, obtain, or restrict certain personal information, subject to applicable law.
- Where applicable law requires separate notice or consent for a particular use of information, this Privacy Policy does not substitute for that notice or consent.
1. About This Privacy Policy
This Privacy Policy explains how IdeaFoundry LLC ("IdeaFoundry," "we," "us," or "our") collects, uses, discloses, stores, retains, and otherwise processes personal information when you access or use IdeaFoundry websites, applications, profiles, discovery features, messaging, workflows, coordination features, provenance and historical records, APIs, Model Context Protocol interfaces, AI and agent integrations, payment or settlement features, and related services (collectively, the "Service").
This Privacy Policy also describes choices and privacy rights that may be available to you.
This Privacy Policy is a notice describing IdeaFoundry's privacy practices. It does not by itself constitute consent where applicable law requires separate, specific, affirmative, or opt-in consent.
Your use of the Service is also governed by the IdeaFoundry Terms of Service:
https://ideafoundry.network/terms
Where applicable law requires another privacy notice, consent, authorization, or disclosure for a particular processing activity, IdeaFoundry will provide that separately.
This policy covers the live native iPhone and Mac applications, Sign in with Apple, Siri and App Intents, compatible Shortcuts, native conversations and reviewed handoffs, as well as the website and connected-host coordination service. Sections 35 through 39 explain the additional native-app data flows and controls.
2. What IdeaFoundry Is
IdeaFoundry is a host-agnostic coordination service that enables people, organizations, and authorized AI systems to coordinate activity across people, organizations, software, and AI environments.
Depending on available functionality, the Service may allow users to:
- create profiles;
- discover people, organizations, projects, capabilities, or work;
- communicate;
- create and participate in workflows;
- invite participants;
- establish roles and permissions;
- coordinate across applications and AI systems;
- use authorized AI agents and automated systems;
- request, perform, review, or approve actions;
- maintain workflow state and history;
- record contributions and provenance;
- generate histories, records, or exports;
- record or facilitate settlement; and
- use other coordination functionality.
Some IdeaFoundry information is designed to be public.
Other information is available only to specified users, workflow participants, organizations, or other authorized parties.
3. Key Definitions
For this Privacy Policy:
"Authorized Agent" means an AI assistant, AI agent, automated system, application, script, workflow, integration, or other software system that interacts with IdeaFoundry through authority, credentials, permissions, or access provided by a user or organization.
"Personal Information" means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked to an identified or identifiable person, to the extent defined as personal information, personal data, or a similar term under applicable law.
"Private Content" means User Content that the Service does not intentionally make available to other users except as authorized through the Service or as otherwise described in this Privacy Policy or the Terms of Service.
"Provenance Record" means a record generated or maintained by IdeaFoundry concerning activity, state, initiation, authorization, approval, participation, timing, source, history, contribution, or other context associated with use of the Service.
"Public Content" means User Content that a user intentionally publishes or designates as publicly accessible.
"Sensitive Information" means personal information subject to heightened protection under applicable law, which may include certain health information, racial or ethnic background, religious beliefs, sexual orientation, citizenship or immigration status, precise geolocation, biometric or genetic information, account credentials, financial-account information, or other legally protected categories.
"Service Data" means technical, operational, security, analytics, configuration, system, event, usage, and similar information generated through operation of the Service, excluding substantive User Content.
"Shared Content" means User Content made available to specified users, workflow participants, teams, organizations, conversations, or other limited contexts.
"Third-Party Host" means a third-party AI assistant, enterprise application, development environment, MCP client, agent runtime, software platform, or other third-party interface through which IdeaFoundry may be accessed.
"User Content" means text, data, files, messages, profile information, documents, images, links, prompts, outputs, contributions, workflow content, and other substantive material submitted, transmitted, published, or provided through the Service.
4. Data Minimization and Purpose Limitation
IdeaFoundry seeks to collect, use, disclose, and retain personal information only as reasonably necessary and proportionate to:
- provide functionality you request;
- operate the Service;
- maintain security and integrity;
- prevent fraud and abuse;
- maintain appropriate workflow and provenance records;
- comply with law;
- protect legal rights; and
- pursue other purposes described in this Privacy Policy or reasonably compatible with them.
IdeaFoundry does not intentionally collect personal information merely because it might become useful later.
Where applicable law requires separate consent before personal information may be used for a materially different purpose, IdeaFoundry will request the required consent before beginning that processing.
5. Information We Collect
The information IdeaFoundry processes depends on how you use the Service.
5.1 Account and Identity Information
When you create, authenticate, access, or use an IdeaFoundry account or authenticated Service functionality, we may process information such as:
- account or profile identifiers;
- profile handles;
- display names;
- email addresses;
- organization identifiers;
- account status;
- authentication-provider identifiers;
- OAuth authorization information;
- session identifiers;
- authorization state;
- token identifiers or token metadata;
- login events;
- logout events;
- revocation information;
- account creation information;
- Terms acceptance records;
- privacy-notice presentation or acknowledgment records;
- specific consent records where applicable;
- timestamps; and
- account-security information.
Authentication providers may process credentials directly.
IdeaFoundry does not need to receive a provider password merely because that provider authenticates you.
5.2 Profile and Discovery Information
If you create or maintain a profile, we may process:
- display name;
- public handle;
- biography;
- tagline;
- skills;
- interests;
- capabilities;
- projects;
- work descriptions;
- organization affiliations;
- public links;
- social links;
- profile sections;
- published updates;
- profile versions;
- public metadata; and
- other information you choose to include.
Information designated as public may be displayed through public profiles, discovery, search, or other public network functionality.
5.3 Workflow and Coordination Information
When you create, join, or participate in a workflow or similar coordination context, we may process:
- workflow identifiers;
- titles;
- summaries;
- descriptions;
- workflow state;
- participant identifiers;
- roles;
- invitations;
- invitation status;
- acceptance, decline, cancellation, removal, or departure events;
- role changes;
- permissions;
- field values;
- updates;
- requests;
- actions;
- next actions;
- contributions;
- approvals;
- transitions;
- timestamps;
- workflow history;
- linked records; and
- other coordination information.
This information may be Public, Shared, or Private depending on the applicable functionality, permissions, and context.
5.4 Messages and Communications
When you communicate through IdeaFoundry, we may process:
- message content;
- replies;
- sender and recipient identifiers;
- conversation or thread identifiers;
- workflow context;
- requests;
- message status;
- timestamps;
- notification information; and
- related provenance.
We may also process communications sent directly to IdeaFoundry, including:
- support requests;
- privacy requests;
- security reports;
- legal notices;
- copyright communications;
- dispute notices;
- feedback; and
- other correspondence.
5.5 Human Authorization and Approval Information
Where IdeaFoundry provides human confirmation, review, approval, authorization, or similar functionality, we may process:
- the initiating user or system;
- the approving or authorizing user;
- the action requested;
- the action approved;
- the authorization scope;
- relevant workflow or organizational context;
- timestamps;
- applicable state information;
- session context;
- Third-Party Host or integration context; and
- related Provenance Records.
These records help IdeaFoundry maintain an accurate history of what the Service recorded as requested or authorized.
5.6 Provenance and Historical Information
IdeaFoundry may create Provenance Records concerning:
- profile creation or publication;
- workflow creation;
- invitations;
- participation;
- roles;
- role changes;
- field changes;
- workflow transitions;
- requests;
- messages;
- replies;
- human authorization;
- AI or automated activity;
- contributions;
- settlement events;
- originating users;
- originating systems;
- Third-Party Host context;
- timestamps;
- historical versions;
- authentication events;
- revocation events;
- security events; and
- other material Service events.
Provenance Records describe what the Service recorded.
They do not necessarily establish that the underlying information was true, independently verified, legally authorized, or legally binding.
5.7 AI Agents, MCP, APIs, and Integrations
If you access IdeaFoundry through an Authorized Agent, API, MCP client, Third-Party Host, enterprise application, development environment, automation, or other integration, we may process:
- tool requests;
- API requests;
- request payloads;
- responses;
- principal or user identifiers;
- integration identifiers;
- host or client identifiers;
- requested scopes;
- granted scopes;
- authorization status;
- token metadata;
- tool invocation information;
- workflow context;
- requested actions;
- completed actions;
- errors;
- rate-limit information;
- authentication events;
- revocation events;
- timestamps; and
- operational or security logs.
Substantive content transmitted through an integration may also be processed where necessary to perform the action requested.
5.8 Third-Party Host Information
When you use IdeaFoundry through a Third-Party Host, we may receive information that the host transmits to perform your request.
This may include:
- your IdeaFoundry identity;
- host or client information;
- instructions;
- messages;
- workflow information;
- content you ask the host to transmit;
- authorization information;
- tool requests;
- requested actions; and
- technical metadata.
Third-Party Hosts may independently process information before or after it is transmitted to IdeaFoundry.
Their independent processing is governed by their own terms and privacy practices.
5.9 Payment and Settlement Information
If payment or settlement functionality is available and you use it, IdeaFoundry and applicable Payment Providers may process:
- Connected Account identifiers;
- Payment Provider identifiers;
- onboarding status;
- verification status;
- transaction identifiers;
- settlement identifiers;
- amounts;
- currencies;
- payment status;
- payout status;
- refund status;
- reversal or chargeback status;
- applicable fees;
- timestamps;
- tax-related status or information where required;
- limited banking or payment information made available by the Payment Provider; and
- information needed to prevent fraud or comply with law.
Payment Providers such as Stripe may collect financial-account, payment-card, identity, tax, or banking information directly.
IdeaFoundry may not receive complete payment-card or bank-account credentials where those details are collected directly by the Payment Provider.
5.10 Technical, Device, Usage, and Security Information
When you interact with the Service, we or our service providers may automatically process:
- IP address;
- browser type;
- device type;
- operating system;
- user-agent information;
- referring pages;
- requested pages or endpoints;
- request timestamps;
- session information;
- approximate location derived from IP address;
- API or MCP request metadata;
- error logs;
- diagnostic information;
- performance information;
- security logs;
- rate-limit information;
- authentication events;
- cookies;
- local-storage identifiers; and
- similar technical information.
We use this information to operate, secure, debug, measure, maintain, and improve the Service.
IdeaFoundry does not ordinarily require precise device geolocation to provide the Service.
5.11 Information From Other Users and Organizations
IdeaFoundry may receive information about you from another user or organization where that person or organization:
- invites you to a workflow;
- adds you to an organization or project;
- sends you a message;
- references you in User Content;
- records a contribution involving you;
- creates a request involving you;
- shares information with you;
- connects an integration; or
- otherwise uses the Service in a way involving you.
If IdeaFoundry contacts you because another user invited you to participate, the invitation should identify why you are receiving it and provide access to this Privacy Policy.
5.12 Information From Service Providers and Other Third Parties
We may receive information from providers that help operate or secure IdeaFoundry, including:
- authentication providers;
- cloud and infrastructure providers;
- security providers;
- monitoring providers;
- communication providers;
- Payment Providers;
- analytics providers;
- Third-Party Hosts;
- enterprise software; and
- integrations you choose to use.
The information received depends on the provider and the Service functionality involved.
Native conversation information, device storage, Apple sign-in information, selected imports, optional model processing, public-source requests and handoffs are described more specifically in Sections 35 through 39. Local processing is distinguished there from information transmitted to IdeaFoundry or an independent provider.
6. Sensitive Information
Users may voluntarily include Sensitive Information in User Content.
IdeaFoundry does not intentionally use User Content to infer a person's sensitive characteristics for:
- advertising;
- cross-context behavioral advertising;
- unrelated profiling;
- eligibility decisions;
- employment decisions;
- credit decisions;
- housing decisions;
- insurance decisions; or
- other independent purposes unrelated to providing the Service requested.
In particular, IdeaFoundry does not intentionally infer from User Content a person's:
- race or ethnicity;
- religion;
- health status or diagnosis;
- sexual orientation;
- gender identity;
- citizenship or immigration status;
- biometric identity;
- genetic characteristics;
- political beliefs; or
- other legally protected sensitive characteristic
for advertising, unrelated profiling, or eligibility decisions.
Where applicable law requires separate affirmative consent before IdeaFoundry may process Sensitive Information for a particular purpose, IdeaFoundry will request that consent separately.
Acceptance of the Terms of Service or acknowledgment of this Privacy Policy is not intended to substitute for specific consent required by law.
If IdeaFoundry introduces functionality specifically designed to collect, infer, or use Sensitive Information for a new purpose, IdeaFoundry will provide any additional notice, consent, or controls required by applicable law before that processing begins.
Consumer health information is addressed further in Section 25 and in the separate IdeaFoundry Consumer Health Data Privacy Policy.
7. Sources of Personal Information
Depending on how you use IdeaFoundry, personal information may come from:
- you directly;
- your account activity;
- Authorized Agents acting through authority you provide;
- Third-Party Hosts you choose;
- organizations with which you participate;
- other IdeaFoundry users;
- workflows and coordination activity;
- authentication providers;
- Payment Providers;
- service providers;
- integrations;
- public sources; and
- information generated through operation of IdeaFoundry.
8. How We Use Information
We may use information for the purposes below.
Providing the Service
This includes:
- maintaining accounts;
- authenticating users;
- managing authorization;
- maintaining sessions;
- providing OAuth functionality;
- processing API and MCP requests;
- providing profiles;
- providing discovery;
- providing workflows;
- delivering messages;
- providing integrations;
- providing contribution records;
- providing settlement functionality;
- generating authorized histories or exports;
- transmitting information to intended recipients; and
- performing actions users request.
Maintaining Coordination and Provenance
This may include:
- recording material Service events;
- maintaining workflow history;
- recording participant state;
- recording invitations and acceptance;
- recording human authorization;
- preserving relevant historical context;
- maintaining contribution information;
- maintaining settlement records; and
- providing authorized users with provenance or historical information.
Security and Integrity
This may include:
- authentication;
- access control;
- fraud prevention;
- abuse detection;
- rate limiting;
- revocation;
- security monitoring;
- incident investigation;
- maintaining security logs;
- protecting users;
- protecting infrastructure; and
- protecting network integrity.
Operating and Improving the Service
This may include:
- diagnosing errors;
- improving reliability;
- testing functionality;
- measuring Service usage;
- improving performance;
- developing functionality;
- capacity planning;
- maintaining compatibility;
- internal analytics; and
- internal research concerning Service operation.
Our use of information to improve the Service does not override the AI-model-training restrictions described in Section 12.
Communications
This may include:
- transactional communications;
- security alerts;
- account notices;
- workflow notifications;
- responding to support;
- responding to privacy requests;
- responding to legal communications; and
- providing material policy or Service notices.
Payments and Compliance
Where applicable, this may include:
- enabling Payment Provider functionality;
- transmitting authorized payment instructions;
- calculating or collecting IdeaFoundry fees;
- processing payment-status information;
- handling refunds or chargebacks;
- detecting fraud;
- satisfying tax or reporting obligations;
- sanctions compliance; and
- other legal obligations.
Protecting Legal Rights
We may process information where reasonably necessary to:
- enforce our Terms;
- investigate suspected violations;
- comply with legal process;
- maintain legally required records;
- establish, exercise, or defend legal claims; and
- protect IdeaFoundry, users, or third parties.
9. Public, Shared, and Private Information
Public Information
Public Content may be accessible to anyone.
Public information may be:
- displayed;
- indexed by search engines;
- linked;
- copied;
- archived;
- screenshot;
- quoted;
- analyzed;
- summarized;
- redistributed; or
- independently used by third parties.
Information intentionally made public may remain available elsewhere after it is changed or removed from IdeaFoundry.
IdeaFoundry cannot control independent copies or uses of information a user intentionally makes public.
Shared Information
Shared Content is made available according to the permissions and context of a workflow, conversation, organization, team, project, or other limited coordination context.
Authorized recipients may view, receive, retain, or export information available to them.
Changing IdeaFoundry permissions does not necessarily remove copies already received by another person.
Private Information
Private Content is not intentionally made public.
IdeaFoundry may process Private Content where reasonably necessary to:
- provide requested functionality;
- maintain authorized access;
- transmit content to intended recipients;
- secure the Service;
- prevent fraud or abuse;
- maintain appropriate provenance;
- comply with law; and
- perform other processing described in this Privacy Policy.
"Private" describes an IdeaFoundry access-control state.
It does not by itself create attorney-client privilege, a nondisclosure agreement, or another legal privilege.
10. User Content, Service Data, and Provenance Rights
IdeaFoundry does not claim ownership of your User Content merely because you use the Service.
Your rights in User Content are addressed in the Terms of Service.
IdeaFoundry separately generates technical Service Data through operation of the Service, including:
- operational telemetry;
- security logs;
- system events;
- rate-limit information;
- technical metadata;
- infrastructure records;
- internal analytics;
- platform schemas; and
- system-generated event information.
A Provenance Record may combine Service Data with information concerning user activity.
The existence of Service Data or a Provenance Record does not transfer to IdeaFoundry ownership of your underlying:
- content;
- contribution;
- intellectual property;
- work product; or
- substantive information.
11. Provenance, Deletion, and Minimization
Provenance is an important part of IdeaFoundry's coordination architecture.
A Provenance Record may contain personal information because it can identify:
- who initiated an action;
- who approved an action;
- who participated;
- who sent or received a message;
- which account or system performed an action;
- which role someone held;
- when an event occurred; or
- which Third-Party Host or integration was involved.
IdeaFoundry may use Provenance Records to:
- maintain workflow state and history;
- provide authorized historical context;
- maintain security;
- investigate misuse;
- resolve inconsistencies;
- prevent fraud;
- establish recorded authorization;
- support dispute handling; and
- maintain network integrity.
IdeaFoundry does not treat a desire to preserve provenance as an unlimited exception to applicable privacy rights.
Personal information contained in Provenance Records may be retained only to the extent permitted by applicable law and reasonably necessary for purposes such as:
- security;
- fraud prevention;
- legal compliance;
- enforcing or defending legal claims;
- transaction integrity;
- protecting the rights of other users;
- maintaining records required by law; or
- other lawful purposes.
Where an underlying provenance event can reasonably be preserved without continuing to identify an individual, IdeaFoundry may:
- de-identify;
- pseudonymize;
- redact;
- separate;
- minimize; or
- otherwise reduce
identifying information rather than retaining it unnecessarily.
Where applicable law requires deletion notwithstanding a provenance interest, IdeaFoundry will comply with the applicable legal requirement.
12. AI Model Training and AI Inference
IdeaFoundry does not use Shared Content or Private Content to train or improve foundation models or general-purpose AI models unless you separately and affirmatively direct or consent to that use.
IdeaFoundry does not intentionally authorize service providers acting solely on IdeaFoundry's behalf to use Shared Content or Private Content to train or improve models for those providers' own purposes.
This restriction does not prevent IdeaFoundry from transmitting content to an AI service selected, connected, or otherwise authorized for the purpose of producing an output or performing an action you request, subject to the applicable provider configuration and terms.
For example, using an authorized model to analyze or summarize content at your request is different from using that content to train a general-purpose model.
We may use:
- Service Data;
- technical information;
- security information;
- aggregate information;
- de-identified information;
- diagnostic information;
- feedback; and
- usage information
to operate, secure, evaluate, maintain, and improve the Service, subject to applicable law.
Independent Third-Party Hosts and AI providers you choose may have different data practices. Their independent processing is governed by their own terms and privacy policies.
Public Content is publicly accessible. Third parties outside IdeaFoundry may independently use Public Content for AI training or other purposes, and IdeaFoundry cannot control those uses.
For native features, distinguish on-device processing, direct Apple cloud processing where available and selected, a separately configured Shortcut, and a handoff into another AI host. The relevant data and choices are described in Sections 35 through 38. A general acceptance or sign-in does not replace any separate permission required for third-party AI sharing.
13. Automated Processing and Significant Decisions
IdeaFoundry uses software and automated systems to operate the Service.
Automated processing may support:
- authentication;
- authorization;
- request routing;
- search;
- discovery;
- rate limiting;
- fraud prevention;
- abuse prevention;
- security monitoring;
- workflow state;
- permission enforcement;
- provenance creation; and
- AI- or agent-assisted functionality requested by users.
IdeaFoundry does not currently use its own automated systems to make final decisions determining an individual's eligibility for employment, credit, housing, insurance, education, health care, or other similarly significant opportunities.
Search, discovery, matching, ranking, or recommendation functionality does not itself make a final eligibility determination unless IdeaFoundry expressly states otherwise.
Users and organizations may use their own Authorized Agents, Third-Party Hosts, or external systems in connection with IdeaFoundry. Those parties are responsible for determining whether their own uses constitute regulated automated decisionmaking.
If IdeaFoundry introduces automated processing subject to a pre-use notice, access right, opt-out right, appeal right, impact assessment, or similar legal requirement, IdeaFoundry will provide the applicable notice and controls before beginning that processing where required.
14. How We Disclose Information
IdeaFoundry may disclose information in the circumstances below.
14.1 People You Direct Us to Share With
When you:
- publish information;
- join a workflow;
- invite a participant;
- send a message;
- share content;
- create a request;
- participate in an organization;
- approve an action; or
- otherwise direct IdeaFoundry to make information available,
we disclose relevant information according to the applicable functionality and permissions.
14.2 Public Disclosure
Public Content and public metadata may be made available through:
- public webpages;
- profiles;
- discovery;
- search;
- public APIs;
- previews;
- links; and
- other public network surfaces.
14.3 Third-Party Hosts and Integrations You Choose
When you direct IdeaFoundry to interact with a Third-Party Host, AI provider, application, integration, development environment, or other external system, information may be transmitted to or received from that system as necessary to perform your request.
The third party's independent processing is governed by its own privacy terms.
14.4 Service Providers and Processors
We may disclose information to providers that process information on our behalf or help operate the Service.
Categories may include providers of:
- cloud infrastructure;
- hosting;
- databases;
- storage;
- authentication;
- security;
- monitoring;
- logging;
- communications;
- analytics;
- development infrastructure;
- payment processing;
- customer support; and
- professional services.
Where required, IdeaFoundry uses contractual or other measures intended to restrict processing to appropriate purposes.
14.5 Payment Providers
Information may be disclosed to Payment Providers for:
- onboarding;
- identity verification;
- payments;
- payouts;
- settlement;
- fraud prevention;
- sanctions screening;
- transaction monitoring;
- tax compliance; and
- related payment functions.
Payment Providers may independently control some information under their own legal obligations and privacy policies.
14.6 Organizations and Administrators
If you use IdeaFoundry through or for an organization, information associated with that organizational environment may be available to authorized administrators and other organizational users according to applicable permissions, settings, agreements, and law.
14.7 Legal, Safety, and Security
We may disclose information where reasonably necessary to:
- comply with law;
- comply with valid legal process;
- respond to lawful government requests;
- enforce the Terms;
- detect or investigate fraud;
- address abuse;
- investigate unauthorized access;
- protect security;
- protect users or third parties;
- protect IdeaFoundry's rights;
- address intellectual-property claims;
- establish, exercise, or defend legal claims; or
- respond to a credible emergency involving safety.
Where legally permitted and appropriate, IdeaFoundry may seek to narrow or challenge requests believed to be invalid or overbroad.
14.8 Business Transfers
If IdeaFoundry is involved in a merger, acquisition, financing, restructuring, asset sale, bankruptcy, change of control, or similar transaction, information may be reviewed, disclosed, or transferred as part of that transaction.
Any successor remains subject to applicable privacy law.
Questions about material service providers and the processing relevant to your use may be directed to support@ideafoundry.network. A provider independently chosen by a user is not necessarily a processor acting solely on IdeaFoundry's behalf.
15. No Sale or Cross-Context Behavioral Advertising
IdeaFoundry does not sell personal information.
IdeaFoundry does not share personal information for cross-context behavioral advertising.
IdeaFoundry does not operate a third-party behavioral advertising business using personal information obtained through the Service.
Disclosures made:
- at your direction;
- to provide functionality you request;
- to processors or contractors;
- to Payment Providers;
- for security;
- for legal compliance; or
- in other circumstances permitted by applicable law
are not intended to constitute sale or cross-context behavioral advertising.
If these practices materially change, IdeaFoundry will provide any notices, consent mechanisms, opt-outs, or other controls required by applicable law before applying the new practice where required.
16. Cookies, Local Storage, and Similar Technologies
IdeaFoundry and its service providers may use:
- cookies;
- local storage;
- session storage;
- server logs; and
- similar technologies
to:
- authenticate users;
- maintain sessions;
- remember settings;
- operate Service functionality;
- protect security;
- prevent abuse;
- understand Service usage;
- diagnose errors; and
- improve performance.
IdeaFoundry does not use tracking technologies for cross-context behavioral advertising.
Browser or device settings may allow you to control certain technologies.
Disabling technologies required for authentication or core Service operation may prevent functionality from working correctly.
17. Global Privacy Control and Preference Signals
Some browsers or extensions transmit privacy preference signals such as Global Privacy Control ("GPC").
Because IdeaFoundry does not currently sell personal information or share it for cross-context behavioral advertising, there may be no such processing to opt out of.
Where applicable law requires IdeaFoundry to recognize a valid opt-out preference signal, IdeaFoundry will process the signal as required.
Generic "Do Not Track" signals are technically and legally distinct from recognized opt-out preference signals.
18. Retention
IdeaFoundry retains different categories of information for different periods based on why the information is needed.
Relevant factors may include:
- how long information is needed to provide the Service;
- account or workflow status;
- user and organizational expectations;
- security needs;
- fraud prevention;
- contractual requirements;
- legal requirements;
- dispute resolution;
- applicable limitation periods;
- transaction or payment obligations; and
- whether information can reasonably be deleted, de-identified, or minimized.
Account Information
Account information may be retained while an account remains active and afterward for a reasonable period where necessary for:
- security;
- fraud prevention;
- legal compliance;
- disputes;
- account restoration; or
- protection of legal rights.
User Content
Public, Shared, and Private Content may be retained while reasonably necessary to provide applicable Service functionality and according to applicable permissions, deletion requests, organizational settings, contractual requirements, and law.
Provenance
Provenance Records may be retained only as permitted by law and subject to the principles in Section 11.
Security and Technical Data
Security, access, authentication, diagnostic, and technical logs may be retained for periods reasonably necessary to:
- detect threats;
- investigate incidents;
- prevent abuse;
- maintain system integrity;
- debug problems; and
- protect legal rights.
Payment Information
Payment and settlement records may be retained as required by:
- Payment Providers;
- tax requirements;
- accounting obligations;
- fraud prevention;
- financial regulation;
- chargeback processes; and
- other legal obligations.
Legal and Consent Records
Records concerning:
- Terms acceptance;
- privacy-notice presentation;
- specific consents;
- consent withdrawal;
- arbitration opt-outs;
- legal notices;
- privacy requests;
- disputes; and
- similar legally significant events
may be retained for as long as reasonably necessary to establish, exercise, or defend legal rights and satisfy applicable law.
Backups
Deleted information may remain in secure backups for a limited period consistent with applicable backup rotation and legal requirements.
Backup information is generally not returned to ordinary active use except when required for disaster recovery, security, or other legitimate operational purposes.
IdeaFoundry maintains or intends to maintain internal retention rules appropriate to major categories of information.
The device-only native conversation vault and its deletion/export controls are described in Sections 35 and 39. It is excluded from the app cloud-backup path; the general backup description above does not promise cloud backup of that vault. Publisher caches, selected preferences, external providers and server records have separate retention paths.
19. Security
IdeaFoundry uses technical, administrative, and organizational measures designed to protect information from:
- unauthorized access;
- unauthorized disclosure;
- loss;
- misuse;
- alteration; and
- destruction.
Measures may include, where appropriate:
- authentication;
- authorization;
- scoped permissions;
- access controls;
- session management;
- revocation;
- logging;
- monitoring;
- encryption in transit;
- infrastructure security;
- rate limiting;
- security testing; and
- incident-response measures.
No internet or software service is completely secure.
IdeaFoundry cannot guarantee that:
- unauthorized access will never occur;
- vulnerabilities will never exist;
- credentials cannot be compromised;
- third parties will always remain secure; or
- information can never be lost.
Users are responsible for protecting credentials, devices, connected systems, and Third-Party Hosts under their control.
20. Your Privacy Choices
Depending on how you use the Service, you may be able to:
- edit profile information;
- control whether particular information is published;
- modify workflow information where authorized;
- revoke certain authorizations;
- disconnect integrations;
- log out;
- stop using a Third-Party Host;
- request account closure;
- request access;
- request correction;
- request deletion;
- request a portable copy of certain information; or
- exercise additional rights provided by law.
Revocation generally operates prospectively.
Revocation does not necessarily:
- recall messages;
- reverse completed actions;
- erase copies already received by another participant;
- erase information independently held by a Third-Party Host;
- reverse completed transactions; or
- delete information IdeaFoundry or another independent entity is permitted or required to retain.
Native users can initiate account deletion through Account and manage local conversations through Conversations. Those controls, optional AI routes and Siri while locked are explained in Sections 35 through 39.
21. Privacy Rights Requests
Depending on applicable law, you may have rights to:
- confirm whether IdeaFoundry processes your personal information;
- access personal information;
- obtain a copy of personal information;
- correct inaccurate information;
- request deletion;
- obtain information about sources;
- obtain information about purposes;
- obtain information about categories of recipients;
- obtain information about specific third parties where applicable law provides that right;
- receive portable information where applicable;
- object to or restrict processing;
- withdraw consent where processing relies on consent;
- opt out of certain processing;
- limit certain uses of Sensitive Information;
- appeal certain decisions concerning privacy requests; and
- receive equal service without unlawful discrimination for exercising privacy rights.
Requests may be submitted to:
Please identify the right you wish to exercise and provide enough information for IdeaFoundry to understand the request.
IdeaFoundry may verify your identity or authority before fulfilling a request.
Verification may depend on:
- the sensitivity of the information;
- the nature of the request;
- whether an authenticated account exists;
- the risk of unauthorized disclosure; and
- legal requirements.
Information provided for verification will be used only as reasonably necessary to:
- verify the request;
- process the request;
- prevent fraud;
- maintain required records; and
- comply with law.
Where applicable law gives you a right to appeal a privacy decision, you may submit an appeal by replying to the decision or emailing:
with the subject line:
Privacy Appeal
22. Authorized Agents for Privacy Requests
Where applicable law permits an authorized agent to submit a privacy request for you, IdeaFoundry may require:
- proof of authorization;
- verification of your identity;
- direct confirmation from you; or
- other information permitted by law.
An AI system's technical access to IdeaFoundry does not by itself establish authority to exercise statutory privacy rights on your behalf.
23. Organizations: Controller and Processor Roles
IdeaFoundry's privacy role depends on the particular processing activity.
For information where IdeaFoundry independently determines why and how processing occurs, IdeaFoundry generally acts as the entity responsible for that processing.
Examples may include:
- IdeaFoundry account administration;
- authentication;
- Service security;
- fraud and abuse prevention;
- platform-level provenance;
- billing;
- payment administration;
- legal compliance;
- Terms acceptance records; and
- operation of IdeaFoundry's own network functionality.
In other situations, an organization may determine the purposes for which certain personal information is processed and direct IdeaFoundry to process that information on its behalf.
Where IdeaFoundry processes personal information solely on an organization's documented instructions under an applicable agreement, IdeaFoundry may act as that organization's:
- processor;
- service provider;
- contractor; or
- equivalent role
under applicable law.
IdeaFoundry may nevertheless act independently for separate processing activities such as security, fraud prevention, legal compliance, or maintenance of IdeaFoundry's own legal records.
If an organization controls information relating to your use of IdeaFoundry, privacy requests concerning organization-controlled information may need to be directed to that organization.
IdeaFoundry remains responsible for privacy requests concerning processing it controls independently.
Organizational customers may enter into additional data-processing terms with IdeaFoundry where appropriate.
24. Payment Providers and Privacy Rights
Payment Providers may independently control certain personal information because of their own:
- financial-regulatory obligations;
- identity-verification requirements;
- fraud-prevention obligations;
- tax requirements;
- transaction records; or
- other legal responsibilities.
A privacy request submitted to IdeaFoundry does not necessarily exercise privacy rights against an independent Payment Provider.
You may need to contact the Payment Provider directly concerning information it independently controls.
IdeaFoundry will address information it controls as required by applicable law.
25. Consumer Health Data
IdeaFoundry is not designed as a health service and does not provide functionality whose primary purpose is medical diagnosis or treatment.
Users may nevertheless voluntarily include information relating to health in messages, workflows, files, or other User Content.
Where Washington's My Health My Data Act or another consumer-health-data law applies, IdeaFoundry will process applicable consumer health data according to the requirements of that law.
IdeaFoundry maintains a separate Consumer Health Data Privacy Policy at:
https://ideafoundry.network/consumer-health-data-privacy
That policy describes applicable:
- categories of consumer health data;
- purposes;
- sources;
- sharing;
- recipients;
- rights;
- consent requirements; and
- deletion processes.
IdeaFoundry does not sell consumer health data.
This Privacy Policy is not intended to replace a separate consumer-health-data privacy policy, notice, consent, or authorization where one is required by law.
26. Children
Authenticated IdeaFoundry services are intended only for users who are at least 18 years old.
The Service is not directed to children under 13.
IdeaFoundry does not knowingly collect personal information from children under 13 in circumstances requiring parental consent.
If IdeaFoundry learns that a person using authenticated IdeaFoundry is under 13, IdeaFoundry will take the actions required by applicable law, which may include:
- restricting access;
- terminating the account;
- deleting personal information; or
- obtaining legally required parental consent where appropriate.
If you believe a child under 13 has provided personal information to IdeaFoundry, contact:
27. California Privacy Notice
This section supplements the rest of this Privacy Policy where the California Consumer Privacy Act, as amended ("CCPA"), applies to IdeaFoundry.
Nothing in this section is intended to state that IdeaFoundry is subject to the CCPA where its statutory applicability requirements are not met.
Where applicable, IdeaFoundry will maintain disclosures concerning the categories of personal information actually collected during the preceding 12 months.
Categories potentially relevant to IdeaFoundry include:
| Category | Examples |
|---|---|
| Identifiers | Name, handle, email address, IP address, account identifiers, authentication identifiers |
| Account and customer information | Contact, account, organization, and Service relationship information |
| Commercial information | Subscription, transaction, settlement, fee, or payment-status information where applicable |
| Internet or network activity | Logs, Service interactions, pages/endpoints, API/MCP activity, device and browser information |
| Approximate geolocation | Approximate location derived from IP address |
| Professional information | Skills, work descriptions, projects, affiliations, organizational roles |
| User Content and communications | Profiles, messages, workflow information, files, prompts, outputs, requests |
| Inferences or derived information | Workflow state, provenance, fraud or security indicators, contribution context |
| Sensitive personal information | Account credentials, certain private communications, financial information, or sensitive information voluntarily submitted |
The specific categories actually collected depend on the functionality you use.
IdeaFoundry uses California personal information for purposes described in this Privacy Policy, including:
- providing the Service;
- authentication;
- authorization;
- workflows;
- messaging;
- profiles;
- discovery;
- provenance;
- payment functionality;
- security;
- fraud prevention;
- debugging;
- maintenance;
- analytics;
- Service improvement;
- support;
- legal compliance; and
- protection of legal rights.
Personal information may be disclosed for business purposes to categories described in Section 14.
IdeaFoundry does not sell personal information as "sale" is defined by the CCPA.
IdeaFoundry does not share personal information for cross-context behavioral advertising as "sharing" is defined by the CCPA.
IdeaFoundry does not have actual knowledge that it sells or shares the personal information of consumers under 16.
IdeaFoundry does not use or disclose Sensitive Personal Information for the purpose of inferring characteristics about individuals for advertising or unrelated profiling.
Where the CCPA applies, California consumers may have rights to:
- know;
- access;
- obtain specific pieces of personal information;
- correct;
- delete;
- opt out of sale or sharing;
- limit certain uses of Sensitive Personal Information; and
- receive equal treatment for exercising rights.
Requests may be sent to:
Where applicable law requires a Notice at Collection, IdeaFoundry will provide that notice at or before the applicable point of collection.
Where California law requires a separate pre-use notice or controls concerning automated decisionmaking technology, IdeaFoundry will provide them before the applicable processing begins.
28. Other U.S. State Privacy Rights
Residents of certain U.S. states may have privacy rights under laws applicable in their jurisdiction.
Depending on the law, these may include rights to:
- access;
- correct;
- delete;
- obtain portable personal information;
- obtain information about categories of processing;
- obtain information about categories of recipients;
- obtain a list of specific third parties where required;
- opt out of targeted advertising;
- opt out of sale;
- opt out of specified profiling;
- withdraw consent;
- appeal a privacy decision; or
- exercise other rights provided by law.
IdeaFoundry does not currently sell personal information or use personal information for cross-context behavioral advertising.
To exercise an applicable state-law right, contact:
29. International Users
IdeaFoundry is based in the United States.
If you access IdeaFoundry from another country, information may be processed in:
- the United States; and
- countries where relevant service providers or Third-Party Hosts operate.
Privacy requirements vary among jurisdictions.
If European, United Kingdom, or another international data-protection law applies to a particular IdeaFoundry processing activity, IdeaFoundry will provide the disclosures, legal bases, rights, transfer protections, contractual terms, or other safeguards required for that activity.
Organizational customers may receive additional data-processing terms where appropriate.
IdeaFoundry does not rely on this general Privacy Policy alone as a substitute for any:
- data-processing agreement;
- international-transfer mechanism;
- legally required representative;
- specific consent;
- special-category-data requirement; or
- other safeguard required for a particular international deployment.
30. De-Identified and Aggregate Information
Where permitted by law, IdeaFoundry may create or use information that has been:
- aggregated;
- de-identified; or
- otherwise processed so that it is not reasonably linked to an identifiable individual.
Such information may be used for:
- analytics;
- research;
- security;
- capacity planning;
- Service evaluation;
- performance measurement;
- product development; and
- understanding network activity.
Where applicable law imposes requirements concerning de-identified information, IdeaFoundry will maintain and use the information in de-identified form and will not attempt to re-identify it except as permitted by law.
31. Notice at Collection and Contextual Notices
This Privacy Policy provides general information about IdeaFoundry's privacy practices.
IdeaFoundry may also provide shorter contextual notices at points where personal information is collected or a new processing activity begins.
A contextual notice may explain:
- categories of information collected;
- purposes;
- retention criteria;
- whether information is sold or shared;
- recipients;
- automated processing;
- Sensitive Information;
- applicable choices; or
- specific consent requirements.
A contextual notice supplements this Privacy Policy.
Where applicable law requires the contextual notice before information is collected or used, IdeaFoundry will provide it at the required time.
32. Consent Records
Where IdeaFoundry relies on legally required consent, it may maintain records concerning:
- the person or principal providing consent;
- consent type;
- purpose;
- scope;
- applicable policy or notice version;
- date and time;
- surface or method through which consent was obtained;
- withdrawal; and
- date and time of withdrawal.
A record that you acknowledged this Privacy Policy is not necessarily evidence that you consented to a separate processing activity for which specific consent is legally required.
33. Changes to This Privacy Policy
IdeaFoundry may update this Privacy Policy as the Service or applicable law changes.
When we update it, we will revise the "Last Updated" date.
Where a change materially affects how personal information is processed, IdeaFoundry may provide additional notice through:
- the Service;
- your account;
- email;
- an authorization flow;
- the website; or
- another reasonable method.
Where a proposed change requires consent under applicable law, IdeaFoundry will obtain the required consent before applying that new processing to information subject to the consent requirement.
Merely publishing an updated Privacy Policy is not intended to substitute for legally required consent.
34. Contact and Privacy Requests
Questions about this Privacy Policy or privacy requests may be directed to:
IdeaFoundry LLC
1309 Coffeen Avenue STE 1200
Sheridan, Wyoming 82801
United States
Privacy:
support@ideafoundry.network
Legal:
support@ideafoundry.network
Website:
https://ideafoundry.network
Privacy Policy:
https://ideafoundry.network/privacy
Terms of Service:
https://ideafoundry.network/terms
Consumer Health Data Privacy:
https://ideafoundry.network/consumer-health-data-privacy
Do not send:
- passwords;
- private cryptographic keys;
- authentication tokens;
- full payment-card numbers;
- government identification documents; or
- other unnecessary Sensitive Information
through an ordinary privacy-request email unless IdeaFoundry specifically requests information through an appropriate verification method.
IdeaFoundry may need to verify your identity or authority before processing a privacy request.
35. Native Conversations, Device Storage and Exports
Information in Native Conversations
The iPhone and Mac apps support ideation and planning conversations. Depending on your use, a conversation may contain your goals, prompts, replies, constraints, drafts, summaries, selected source excerpts, imported context, model-route information, handoff edits and account context you viewed or selected. Some of this information may be personal or sensitive.
The app's native conversation history is stored in an encrypted vault on the device, separated by authenticated account. The app marks that vault as excluded from cloud backup and stores its keys using device-only Keychain settings. App preferences, model choices and route-test state are stored separately from conversation text. Authentication credentials are stored in the device Keychain rather than the conversation preference store.
The native conversation-history feature does not itself upload your conversation vault to IdeaFoundry for server-side history storage or synchronize it across devices. This does not mean that all use of IdeaFoundry stays on-device: authentication, account reads, authorized account operations, public-source requests, external AI processing and handoffs have the separate data flows described below. Shared profiles, messages, Workflows and Settlement Records continue to be processed by the IdeaFoundry service.
History, Export and Loss
You can view and delete individual native conversations, delete all local conversations for the current account, or export readable text or JSON through Conversations. Exports can include dialogue, sources and other saved conversation information. Once exported, the copy is outside the encrypted vault and may be stored, backed up or shared under the destination's settings. An exported file is not protected by the vault's encryption merely because it originated there.
Local history remains until you delete it or it is otherwise removed by account cleanup, device management or operating-system behavior. Signing out does not by itself erase saved history. Because local history is device-bound and excluded from the app's cloud-backup path, device loss, unavailable encryption keys or deletion may make it unrecoverable. These measures do not guarantee protection against a compromised or accessible device.
36. Sign in with Apple and Authentication
Sign in with Apple is available as an authentication option. Depending on your choices and the authentication flow, Apple supplies an app- or developer-associated identifier, authentication assertions and, where you authorize it, your name and email address. Your email may be a private relay address rather than your ordinary address. The information supplied can differ between your first authorization and later sign-ins.
Apple and our authentication provider process the sign-in transaction. IdeaFoundry uses the resulting identity and authorization information to create or identify your account, establish sessions, protect access, communicate with you and handle account recovery or deletion as appropriate. Sign in with Apple does not disclose your Apple password to IdeaFoundry or give IdeaFoundry general access to your Apple Account, iCloud files, Photos library or Apple payment information.
A relay email and an ordinary email can differ even when used by the same person. We do not treat possession of a copied handle, a public profile or an email resemblance as proof of account ownership. Authentication and any account-linking process must establish the relevant authority.
You can manage Apple authorization and relay-email choices through your Apple Account settings. Disabling email forwarding can affect delivery of account communications. Revoking Apple sign-in authorization, signing out of IdeaFoundry and deleting an IdeaFoundry account are separate operations. Where applicable, account deletion includes revocation of associated Sign in with Apple tokens. Deleting IdeaFoundry does not delete your Apple Account.
Apple's independent processing is described in Apple's Sign in with Apple privacy notice: https://www.apple.com/legal/privacy/data/en/sign-in-with-apple/ . Completing Apple sign-in is not itself permission for optional external AI sharing or acceptance of every separate processing activity.
37. AI Processing, Public Research and Host Handoffs
On-Device and Apple Cloud Processing
On-device reply generation processes selected conversation context using an Apple model on your device. Choosing an external or cloud route can instead transmit the relevant input to the selected service. Where supported and selected, direct Apple cloud processing is distinct from processing through a user-installed Shortcut. Availability depends on Apple's platform, account, region, operating-system and capability requirements.
Optional Model Routes Through Shortcuts
The app supports optional Apple Cloud, Apple Cloud Pro and ChatGPT routes through compatible Shortcuts. Before conversational context is shared through such a route, the app presents a provider-sharing choice. The authorized route can receive your request, goal, relevant dialogue, selected inspiration or research excerpts, and attachments you add to that chat. The input may therefore include personal information you put in those fields. Returned answers, route labels and related request information may be saved with local conversation history.
Enabling or selecting a route applies to the scope described by that control and may apply to subsequent messages until you change it. A separate research action can transmit only a public question you review, rather than the broader conversation. The app does not treat acceptance of the Terms or acknowledgment of this Privacy Policy as a substitute for explicit permission where required before personal information is shared with a third-party AI service.
Shortcuts are separately installed and can be configured or modified by you or another provider. The configured Shortcut controls its actual model and processing destinations. A route's requested label or successful callback does not independently verify the Shortcut's internal configuration. Review the Shortcut and selected provider before enabling it. Apple and any AI provider process inputs under their own applicable terms, settings and privacy practices. This policy does not promise that independent providers never retain data or use it for training.
Change the model selection or disable the route in app settings to stop future use of that route. Doing so does not delete information already received by Apple, an AI provider or another recipient. Direct any provider-specific deletion request to that provider as appropriate. IdeaFoundry's own restrictions on generalized-model training in Section 12 continue to apply.
Public Research and Inspiration
When you request background research, the reviewed question or derived search terms can be sent to the selected public-source service, such as Wikipedia or Crossref. A browser search sends the search text to the chosen browser/search service. Optional legacy search configurations, where available and enabled, may use a user-supplied provider key stored in the device Keychain. The public-research request does not automatically include an account bearer token or the full conversation.
Inspiration cards retrieve public publisher feeds and, where available, publisher-declared images. Providers and image hosts receive the request and ordinary network information, such as IP address, request headers and timing. These requests may occur when a feed or image loads, without a separate query. Publisher content and image caches are separate from the encrypted conversation vault. A local-topic preference, such as choosing Seattle content, is a preference, not a request for precise GPS location.
Handoffs to Other Hosts
Preparing a handoff assembles selected context, which may include your goal, summary, dialogue excerpts, sources, imported material and the intended IdeaFoundry profile hint. Review the content before copying, exporting, sharing or opening the destination. Copying writes the reviewed text to the system clipboard; the host receives it when it is passed or pasted there. Depending on the selected flow, an opening or sharing action may also transmit information shown by that flow.
The receiving host processes the material under its own terms and settings. A copied profile hint is not an authentication credential. The receiving host must establish its own authenticated access before reading private IdeaFoundry account state or taking authorized actions. Imported content, a handoff or a summary does not by itself grant unrestricted authority.
38. Siri, Imported Context and Support
Siri and Optional Locked-Device Access
Siri and App Intents can pass your request and explicitly supplied context to IdeaFoundry and return a spoken or displayed response. Apple handles speech and Siri processing under its own settings and privacy terms. IdeaFoundry does not save raw speech audio in native conversation history; transcribed requests and generated text may be saved there. This statement does not describe Apple's independent audio retention.
If you enable Allow Siri while locked, the app creates a separate device-only authorization that can make the authorized IdeaFoundry context and local conversation history available to Siri while the device is locked, after the applicable device authentication state permits it. This changes the access conditions for that information. You can turn the option off; signing out or changing accounts revokes the app's Siri authorization. Apple and device controls may add restrictions. Other people able to invoke Siri on your device may hear information the feature makes available.
Selected Text, Images and Files
You can explicitly paste text, supply a link, select a screenshot or image, import a supported file, or pass context through an App Intent or sharing flow. The app reads the selected material to prepare context for your review. Screenshot text recognition takes place on-device. Recognized text can contain errors. Accepted excerpts and source information may be saved in local conversation history and included in later processing or a handoff according to your selections.
Selecting one item does not authorize background access to the whole Photos library, clipboard, other apps or earlier Siri history. Opening IdeaFoundry alone does not transfer another app's content. A source link may be recorded without retrieving the page. After you attach context to a chat, its text may be included in the next message to your selected external model; review the model and sharing choices before sending sensitive material.
Support and Diagnostics
Contact support opens a mail draft addressed to support@ideafoundry.network with a fixed subject. That action does not automatically attach your transcript, account details, credentials or diagnostics, and does not automatically send the email. We receive information you choose to send. Your email provider independently processes the communication.
App diagnostics or reply traces, where available, can contain prompts, replies, source material and technical context. A local diagnostic view is not itself an automatic upload. If you choose to export or send diagnostics, inspect and minimize the material first. Server-side authentication, security and operational logs remain subject to Sections 5, 8, 18 and 19. A privacy manifest declaring a required-reason API is not a statement that the app or connected services collect no personal information.
39. Native Account Deletion and Privacy Controls
You can initiate deletion of your IdeaFoundry account from Account in the native app. The process may require fresh authentication, verification that the intended account is selected and an explicit final confirmation. If you cannot access the control, contact support@ideafoundry.network for help or to exercise applicable privacy rights. A verification step alone does not complete deletion.
Account deletion removes the account and associated personal information as required by law, revokes IdeaFoundry access and addresses linked authentication records, including applicable Sign in with Apple token revocation. Native local-history and credential cleanup is performed on the requesting device as part of the app's deletion flow. It is not a remote wipe of exported files, other devices, other participants' copies or independent providers' records.
We do not retain identifiable personal information solely because it appeared in a provenance record where law requires deletion. Where a shared record must remain for a lawful purpose, we delete, redact, de-identify or otherwise minimize identifying information as appropriate. Limited information may be retained for legal obligations, fraud prevention, security or legal claims only where and for as long as legally permitted. Shared-record integrity does not override applicable deletion rights.
Deleting local conversations affects the selected account's history on that device and does not delete server-side messages or shared work. Logout and revocation stop future authorized access within their scope without necessarily deleting records. Uninstalling the app does not itself request server-account deletion. Disabling Apple sign-in or a model route does not by itself delete the IdeaFoundry account. Requests concerning data independently controlled by Apple, another AI host or another recipient must be addressed to that controller where appropriate.
You can request access, correction, deletion, portability or another applicable privacy right through support@ideafoundry.network. Specify the request type in the subject or message, for example Privacy Request, Privacy Appeal or Consumer Health Data Request. This does not limit the other request methods, rights or appeal procedures stated in this policy or required by law.
Copyright © 2026 IdeaFoundry LLC. All rights reserved.
Back to top ↑
