Privacy Policy
Effective Date: 2026-10-05 · Last Updated: 2026-10-05 · Version: 2026-10-05
Introduction
This Privacy Policy explains how GenieForge Technologies Inc. ("GenieForge," "we," "us," or "our") collects, uses, stores, and shares personal information in connection with the GenieForge platform, websites, and related services (the "Platform"). It also explains your rights with respect to your personal information and how to exercise them.
GenieForge operates a two-tier platform: Builders are businesses and individuals who create accounts and build AI-powered applications on the Platform; End-Users are the people who use those applications. This Policy covers Builder personal information and platform-level data practices. It does not cover the full scope of data that Builders collect from their own End-Users through applications built on the Platform. That collection is governed by each Builder's own privacy notices and by our End-User Privacy Policy.
This Policy applies to Builders and visitors to genieforge.ai. If you are an End-User of an application built on GenieForge, your primary privacy notice is the privacy policy provided by the Builder of that application. The GenieForge End-User Privacy Policy explains how GenieForge itself processes personal information in connection with End-User-facing App features.
Information We Collect
Information You Provide
- Account information: Name, email address, phone number (if provided), company name (if provided), and authentication credentials. Builder passwords are handled by our self-hosted identity service on our infrastructure and stored in irreversible hashed form.
- Billing information: Payment details processed by our payment provider (Stripe). We do not store full card numbers. We retain billing identifiers, emails, and subscription records as needed to bill you.
- End-User billing details (when enabled): If you use the Platform's Stripe Connect feature to collect payments from your End-Users, we collect information about your connected Stripe account, transaction metadata, and related records necessary to facilitate payments and calculate GenieForge's transaction fee. We do not store your End-Users' full card numbers.
- App content: System prompts, tool configurations, page designs, schemas, environment-variable metadata, and other content you create while building applications
- Conversations and AI activity: Messages exchanged with AI assistants, tool call inputs and results, uploaded attachments, and optional per-user memories when enabled
- Support, feedback, and usage signals: Bug reports, feature requests, product-assistant feedback, and usage signals captured from Apps (title and description text) so we can help you improve those Apps and improve the Platform. That text is stored in Platform tables, clustered with embeddings, and reviewed by authorized GenieForge staff. Enhancement proposals created from those signals are reviewed the same way.
- Communications: Emails and messages you send to support or legal contacts
Information Collected Automatically
- Usage data: First-party product events. Signed-in Builder page views, and account-linked product events (including events generated on our servers, such as signing up, creating or publishing an App, starting checkout, subscription and billing changes, invitations, connecting or disconnecting MCP clients, chats, and scheduled job runs), are off until you turn them on in Cookie Preferences (in the footer of genieforge.ai) or in the Privacy section of your Profile page. That choice is saved to your account. We do not record those events unless you have turned them on, and we do not use region detection to make that choice. When recorded, an event contains the event type, internal identifiers, counts, and fixed categories (such as plan, role, source, and status). A page view also records the page path with identifiers removed, and the device and browser categories described below. It does not contain App, project, job, or tool names, or other free text. Invitation events record the role offered, not the invitee's contact details. Names already stored in these events are being removed. Separately, usage signals from your App (title and description text you or your App submit) are stored so the Platform can provide dashboards, AI-powered usage queries, and enhancement proposals. Those signals are described under Information You Provide and are not the product-analytics events in this bullet.
- Device and browser information: Browser family and major version, operating system family, device class (desktop, mobile, or tablet), a screen size range (five widths, not exact pixels), and the primary language of your browser (for example "fr", not "fr-CA"), derived from your browser and stored as categories. We do not store the raw user-agent string, exact screen size, or language region for analytics. The user-agent is also processed transiently to hash guest page views
- IP address: For security, rate limiting, and abuse prevention. For page views (guest page views, and signed-in page views when you have turned product analytics on) we derive a country code from the IP address and do not store the IP address itself; guest analytics hashes the IP for the day and does not store it. We do not use IP address, country, or browser timezone to decide whether a signed-in Builder has turned product analytics on
- Referral and campaign information: The domain of the site that referred you (not the full address) and campaign tags (UTM parameters) on marketing pages
- Cookies and similar technologies: Session cookies (required for authentication) and preference cookies, including the localStorage analytics consent preference described in the Cookies section
Information Related to End-User Activity
When your App processes data from your End-Users (including through tenant/project environments), we act as your data processor for that End-User data. The personal information processed on your behalf as part of your App's operation, including End-User account information, session activity, AI agent interactions, and content submitted through your App, is described in the End-User Privacy Policy and is processed under your instructions and the terms of any applicable BAA or data processing agreement. We do not use End-User personal data for our own marketing or analytics purposes.
Information We Do Not Collect (by default)
- We do not use third-party advertising trackers or sell personal information to data brokers
- We do not collect biometric identifiers for Platform authentication
- We do not collect precise GPS geolocation
Apps you build may collect additional categories of data from End-Users under your control. That collection is described in your notices and our End-User Privacy Policy.
How We Use Your Information
| Purpose | Basis (where applicable) |
|---|---|
| Provide, maintain, and secure the Platform, including account administration, authentication, and other records needed to deliver the service | Necessary for service delivery / contract. Not controlled by the analytics choice |
| Process payments and manage your subscription, including billing, payment, and subscription records | Contractual obligation. Not controlled by the analytics choice |
| Send account-related communications (password resets, billing alerts, security notices) | Necessary for service delivery / legitimate interest |
| Security and audit logs, and detecting or preventing fraud, abuse, or security incidents | Legitimate interest / legal obligation. Not controlled by the analytics choice |
| Optional first-party product analytics: signed-in page views and account-linked events, including events generated on our servers | Consent where required. Recorded only after you turn them on. Generating an event on our servers does not, by itself, place it outside this choice or outside a consent requirement. Legitimate interest may support proportionate analytics under GDPR after the appropriate assessment, and does not replace consent where Canadian law or another law requires consent |
| Improve the Platform using aggregate or de-identified usage patterns and Feedback | Legitimate interest |
| Platform improvement review of App blueprints and Builder conversations (see below) | Legitimate interest / contract |
| Describe, in general terms, the kinds of Apps built on GenieForge in our website, marketing, and sales materials, without naming you, your organization, your App, or your End-Users (see Terms Section 5) | Legitimate interest. You can opt out by emailing legal@genieforge.ai |
| Respond to support and privacy requests | Contractual obligation / legal obligation |
| Comply with law and enforce our Terms | Legal obligation / legitimate interest |
Necessary records (account administration, authentication, billing and payment records, subscription records, security and audit logs, and records needed to deliver the service) are kept whether or not you turn product analytics on. Using an operational event for optional product analytics is a separate purpose. Optional tracking follows your analytics choice regardless of where the event is generated. We obtain consent for that optional tracking where the law requires it.
Platform improvement review
Authorized GenieForge personnel may occasionally review App blueprints and Builder build activity to identify gaps in the Platform and improve its capabilities. Reviews typically focus on App blueprints (tools, pages, schemas, prompts, configurations) and, when needed for context, Builder conversations and related build activity. They also include usage signals and enhancement proposals: builder-submitted free text copied into Platform staff-review tables, plus embeddings used to cluster similar items. The purpose of these reviews is to make the Platform more robust, close capability gaps, and learn from general Builder behavior. Insights inform our product roadmap in aggregated or de-identified form where practical.
Limits on these reviews:
- (a) Reviews are performed by authorized GenieForge personnel under access controls and are not disclosed publicly or to other customers.
- (b) We do not use App content, build conversations, or End-User data reviewed in this process to train or fine-tune AI models.
- (c) We do not use these reviews to share your confidential App materials with other customers.
- (d) HIPAA Apps under a BAA are excluded from product-improvement review of App content and End-User data, except as expressly permitted by the BAA (which covers Platform services, security, support, and automated processing of usage signals and enhancement proposals).
- (e) Support access to a Builder's account or App requires multi-factor authentication, is limited to a 30-minute session, expires automatically, and is logged so the affected Builder can see that access occurred. Builders can additionally require their own approval before any GenieForge staff access (App Settings, Privacy, "Platform support access").
End-User business data and End-User chat are not the focus of this review.
We do NOT:
- Sell your personal information
- Share your data with advertisers or data brokers for their independent marketing
- Use your app content or build conversations to train or fine-tune AI models (Platform policy)
Aggregated and De-Identified Data
GenieForge does not sell, license, or otherwise disclose to third parties the underlying data of Builders or End-Users, including in anonymized or pseudonymized form, other than to service providers acting on our behalf under contractual restrictions, and disclosures you direct. GenieForge reserves the right to generate and use aggregated, de-identified usage analytics that cannot reasonably be attributed to any individual, organization, or specific application (for example, usage frequency distributions, feature adoption rates, and general performance trends across the Platform). Such analytics do not include any customer-specific content, application data, or personally identifiable information. If GenieForge ever changes its practices in a way that would involve monetizing, licensing, or disclosing data in a materially different manner, we will provide advance notice and, where required by applicable law, obtain any consents necessary before doing so.
AI Processing
When you use AI features, your prompts, relevant App context, conversation history, and necessary attachments are processed by AI model providers to generate responses in real time. Categories of providers are listed on our Subprocessors page. For HIPAA-enabled Apps, AI processing is restricted to providers permitted under our Business Associate arrangements (currently AWS Bedrock within the HIPAA boundary).
Your conversations are not used by GenieForge to train or fine-tune AI models. Processing occurs under our agreements with providers. Model providers may process data in the regions where their services operate, as described on the Subprocessors page.
AI outputs can be wrong. Do not rely on them as sole professional advice.
Data Sharing
We share your information with service providers that help us operate the Platform, under contracts that restrict use of the data to providing services to us. Categories include:
| Category | Purpose | Examples |
|---|---|---|
| Cloud infrastructure | Hosting, compute, storage, databases, email delivery, and our self-hosted identity service | Amazon Web Services (United States) |
| CDN / edge / custom domains | CDN, DDoS protection, TLS termination, and vanity / custom hostname routing | Cloudflare |
| Payment processing | Subscription billing, invoicing, and End-User payment processing via Stripe Connect (when enabled) | Stripe |
| AI inference | Generate assistant and agent responses | AWS Bedrock; and for non-HIPAA Apps, providers such as Anthropic, OpenAI, and xAI |
| Product analytics | Optional account-linked product events, recorded only if you turn them on, and guest marketing-site page views described in Cookies (consent where required; HIPAA limits described below) | First-party (stored in our AWS database) |
| Optional Platform tools | Features you or your App enable (web search, transcription, scraping, image generation, push delivery, form captcha, currency conversion) | Tavily, Soniox, Apify, OpenAI images, FCM / web push, hCaptcha, Frankfurter, jsDelivr, as configured |
| Customer-directed integrations | Services you connect (OAuth, webhooks, outbound HTTP) | Destinations you authorize (Google, Slack, Notion, Stripe Connect, and others) |
A living list of subprocessors is published at /subprocessors. We may update that page as providers change. For material changes affecting how personal information is processed, we will provide notice consistent with this Policy and applicable law.
We may also disclose information when required by law (for example, a valid court order or subpoena), to protect rights and safety, or in connection with a merger, acquisition, or asset sale (with appropriate safeguards).
Personnel in Canada may access systems and data as reasonably necessary to operate, support, and secure the Platform, and to perform Platform improvement review as described above.
Data Retention
| Data Type | Retention Period |
|---|---|
| Account and profile | Until you delete your account or we close it |
| App content and configurations | Until you delete the app or your account |
| Build conversations and attachments | Until you delete the conversation or your account |
| Usage signals and product feedback | Until resolved/deleted in-product or account deletion, subject to de-identified improvement use |
| Product analytics events | Individual events up to 90 days. Daily aggregate counts, which do not identify individual Builders, up to 12 months. Events tied to your account are deleted when your account is deleted. Product events tied to a HIPAA App are not recorded. If events were recorded for an App before it became a HIPAA App, those earlier events are deleted once they are older than 30 days. |
| Billing records | As required by tax/financial law (typically up to 7 years) |
| Audit records | Where HIPAA documentation retention applies, a minimum of six (6) years from creation or last effective date. Otherwise, as required by applicable law and our security program. Audit log tables are append-only; deletion requires a specially controlled role. |
| Security and operational logs | Ordinary security and operational logs, other than the audit records above, are kept for no more than 2,192 days. That is the longest period configured for those logs. Some of them are kept for a shorter period. HIPAA's six-year documentation rule does not require every operational log to be kept for six years. Where applicable law requires a longer period, that longer period applies. |
| Encrypted backups | Rolling operational window of about 35 days, plus monthly long-term recovery snapshots retained up to 12 months for recovery from corruption or deletion discovered late, and for legal hold. Backups are encrypted and are not used to restore individual records after a deletion request except where required by law |
Upon account deletion, personal data is removed from active systems within a commercially reasonable period, subject to legal retention and backup windows described above. To request deletion, email privacy@genieforge.ai.
Your Rights
Depending on your jurisdiction, you may have the right to:
- Access a copy of the personal data we hold about you
- Correction of inaccurate data
- Deletion of your account and personal data (subject to legal retention)
- Data portability of data you provided, in a structured, commonly used format where technically feasible (App blueprint export is available in-product; full account portability packages are handled via privacy requests)
- Object to certain processing activities
- Withdraw consent where processing is based on consent
To exercise any right, email privacy@genieforge.ai. We aim to respond within 30 days, or within the period required by applicable law if shorter or longer.
Canadian privacy (PIPEDA and applicable provincial laws)
If you are in Canada, your rights are governed by the Personal Information Protection and Electronic Documents Act (PIPEDA) and, where applicable, substantially similar provincial privacy legislation (including the Act respecting the protection of personal information in the private sector in Quebec, which imposes additional obligations including data localization considerations). You may request access to and correction of personal information we hold about you by contacting privacy@genieforge.ai. We will respond within 30 days unless an extension is permitted by applicable law. If you believe we have handled your personal information inappropriately and we have not resolved your concern, you may contact the Office of the Privacy Commissioner of Canada or the applicable provincial privacy regulator.
California (CCPA / CPRA)
If you are a California resident, you may have rights to know, delete, and correct personal information, to opt out of "sale" or "sharing" for cross-context behavioral advertising, and to limit our use of sensitive personal information. GenieForge does not sell or share personal information as those terms are defined under the CCPA/CPRA. We do not use sensitive personal information to infer characteristics about you beyond what is necessary to provide the Platform. To exercise rights, email privacy@genieforge.ai. We will not discriminate against you for exercising privacy rights.
European Economic Area / UK
If GDPR or UK GDPR applies, our legal bases are described in the table above. For transfers outside the EEA/UK, we may rely on legally recognized transfer mechanisms and safeguards permitted by applicable law. Contact privacy@genieforge.ai for questions. You may have the right to lodge a complaint with a supervisory authority.
Cookies
We use the following categories of cookies and similar technologies:
| Category | Purpose | Duration | Required? |
|---|---|---|---|
| Session / authentication | Keeps you logged in and secures the session | Browser session or as set by our identity service | Yes |
| Preferences | Remembers UI settings (for example, theme) | Up to 1 year | No (functional) |
| Analytics preferences | Records whether optional product analytics are on or off | Saved to the Builder account for signed-in events. For guests, stored in this browser (localStorage) until you change it | No. Signed-in account-linked analytics, including server-side events, stay off until you turn them on. Consent where required |
We do not use third-party advertising cookies.
We do not set an analytics cookie. Optional product analytics follow the choice above whether the event is generated in the browser or on our servers. Signed-in Builder page views and account-linked events stay off until you turn them on in Cookie Preferences (in the footer of genieforge.ai) or in the Privacy section of your Profile page. That choice is saved to your account, and our servers do not record those events without it. We do not use region detection for that choice. Necessary records described in How We Use Your Information are kept either way.
Guest page views on the marketing site (when you are not signed in) use a daily hash of IP address and user agent, together with the device, country, referral, and campaign categories described under Information Collected Automatically. The raw IP address and user-agent are processed transiently and are not stored. Those guest rows are not linked to an account. Hashed guest rows cannot reasonably be linked to a person, so access or erasure requests cannot match them. Guest page views are recorded by default. Where the browser's timezone suggests Europe, they are recorded only after the guest accepts. Guests can decline them in Cookie Preferences. A browser timezone is not a reliable way to identify where a person is, including Quebec or a country in Europe.
Product events tied to a HIPAA App are not recorded. Analytics are also disabled on certain End-User surfaces (for example, intake and portal) as implemented in the product. See also /subprocessors.
Security
We implement technical and organizational measures we consider appropriate for a platform of this type. Current measures include: encryption of data at rest, and encryption of data in transit using TLS 1.2 or higher over public networks and on our connections to databases, caches, and managed cloud services. Traffic inside our private cloud network, between a Platform load balancer and the application workloads behind it, is protected by network segmentation and access restrictions and may not be separately encrypted. We also use multi-factor authentication requirements for administrative and support access; access controls and role-based permissions limiting data access to authorized personnel; audit logging of security-sensitive actions in append-only tables; and periodic security reviews. For HIPAA Apps, additional safeguards apply as described in the HIPAA-Eligible Accounts section below. Details for enterprise diligence may be available on request under a confidentiality agreement. No method of transmission or storage is completely secure, and we do not guarantee that unauthorized access will never occur. We will notify affected parties of a data breach to the extent required by applicable law.
HIPAA-Eligible Accounts
If you enable HIPAA mode for an App and execute a Business Associate Agreement (BAA) with GenieForge, the following additional safeguards apply to End-User data processed within that App:
- (a) AI model routing: All AI inference is routed exclusively through AWS Bedrock. Non-AWS AI providers are blocked, keeping PHI within the AWS Business Associate boundary.
- (b) Analytics: Product events tied to a HIPAA App are not recorded, and no analytics data from HIPAA App usage is sent to any third-party analytics service. If events were recorded for an App before it became a HIPAA App, those earlier events are deleted once they are older than 30 days. Account-level events that are not tied to an App (for example signing up, or subscription and billing changes) may still be recorded for a Builder who also has a HIPAA App, only if that Builder has turned product analytics on. Those events contain no free text and no PHI. The absence of an App identifier is not the only control: the events are limited to the event type, internal identifiers, counts, and fixed categories.
- (c) Image generation: OpenAI image generation is blocked for HIPAA Apps because OpenAI has not executed a BAA with GenieForge.
- (d) Support access: Administrative support impersonation requires multi-factor authentication, is limited to 30 minutes per session, expires automatically, and is logged so the affected Builder can see that access occurred.
- (e) Audit logs: Audit records are stored in append-only tables. Deletion requires a specially controlled administrative role. Where HIPAA documentation retention applies, those audit records are retained for a minimum of six (6) years. Ordinary security and operational logs are a separate set and are retained for no more than 2,192 days, unless applicable law requires longer. HIPAA's six-year documentation rule does not require every operational log to be kept for six years.
- (f) Encryption: Data is encrypted at rest. Data in transit is encrypted using TLS 1.2 or higher over public networks and on Platform connections to databases, caches, and managed cloud services. Traffic inside the private cloud network, between a Platform load balancer and the application workloads behind it, is protected by network segmentation and access restrictions and may not be separately encrypted.
- (g) Backups: Backup practices for HIPAA Apps are described in security documentation available on request or under a BAA.
Enabling HIPAA mode does not change how your Builder account data is processed for platform administration. GenieForge does not certify your App as "HIPAA certified"; compliance depends on your configuration and practices as well as ours. Custom domains may route traffic through Cloudflare; for PHI, use GenieForge-provided hostnames unless we have confirmed that the custom-domain path is covered under applicable Business Associate arrangements. See /subprocessors.
International Users
GenieForge Technologies Inc. is incorporated in Canada. Platform infrastructure is hosted in the United States on Amazon Web Services. GenieForge personnel in Canada may access systems and data as reasonably necessary to operate, support, and secure the Platform. If you access the Platform from outside Canada or the United States, your personal information will be transferred to and processed in the United States and Canada. Different countries have different data protection laws. We may rely on legally recognized transfer mechanisms and safeguards permitted by applicable law. Contact privacy@genieforge.ai for information about the safeguards applicable to your data.
Children
GenieForge Builder accounts are for individuals 18 and older. The Platform is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe we have, contact privacy@genieforge.ai and we will take appropriate steps to delete it.
Changes to This Policy
We may update this Policy from time to time. We will post the updated Policy with a new Version and Last Updated date. For material changes, we will provide notice via email and/or in-app notification when practicable. Unless we state a later effective date, changes take effect when posted. We will not backdate this Policy. Continued use after the effective date does not replace any consent the law requires, including consent to optional product analytics.
Contact
For privacy inquiries:
- Email: privacy@genieforge.ai
- Entity: GenieForge Technologies Inc.
- Privacy Officer: Founder, GenieForge Technologies Inc., reachable at privacy@genieforge.ai
- Mailing address: available on request to privacy@genieforge.ai