PRIVACY Version 26 October 2026

How Forge uses and protects your data

This notice covers the Forge website, public directory, Provider and Seeker accounts, private workspaces, subscriptions, the Forge Coordinator, connected AI applications and the Niflheim Forge App for iOS and Android. The separate profile policy explains how public provider listings are researched.

Forge cookies and optional video players

The public directory does not place advertising or analytics identifiers on your device. Signed-in areas use only the cookies required to authenticate and protect the Forge account. Provider profile-view totals are recorded as aggregate counts without a visitor identifier. Separately, Vercel Web Analytics measures public Website traffic without analytics cookies; details are below. Optional YouTube/Vimeo players remain blocked until you consent; their own processing is described below.

1. Controller and contact

Luis Godoy Alvarez, trading as Niflheim Records and operating Niflheim Forge, Stabiusstr. 11, 90489 Nürnberg, Germany. Email: kontakt@niflheimrecords.de. Telephone: +49 151 6112 1871.

2. Accounts and authentication

When you create or use a Forge account, we process the verified email address, account name and type, membership and role, language, time zone, working currency, authentication and MFA state, security events and account preferences. A Provider account and a Seeker account remain separate; authentication identifies the person acting for that account.

Every Seeker account can keep a private profile with a display name and optional description, city or region, website, contact email, phone and image or logo. Authorised members of that account can read it; other accounts cannot. Contact email is entered separately from the sign-in address. Choosing profile fields for a business-card draft does not send them, change an existing card or update an exchanged copy. The image stays private to the account. Forge removes embedded metadata from the saved image. Replaced or removed images become inaccessible through the profile immediately and their files are queued for cleanup; unfinished uploads become eligible for cleanup after 24 hours. Profile fields and the saved image reference are included in the account export. Account closure deletes the profile and queues its image files for removal.

If you choose Google authentication, Google supplies the verified email address, a stable account identifier and basic identity fields used to operate the sign-in. Forge does not request access to Google Drive, contacts, calendars or offline Google access, and does not use a Google profile image as provider media.

This processing is necessary to create and perform the Forge contract, respond before a contract is formed, protect accounts and prevent misuse, and comply with legal duties. The applicable bases are Article 6(1)(b), (c) and (f) GDPR.

2a. Sign-in and storage in the Niflheim Forge App

The App uses the same Forge account as the website. Its sign-in session is stored securely on your phone using the iOS Keychain or Android Keystore. The chosen language and your choices about the Android code reader and error reports also stay on the phone. Private profile pictures are held in memory for the signed-in account, not saved as a picture cache on disk. The diagnostic files created after consent are described in section 8b.

Before sign-in, registration or a password reset, the App loads Cloudflare Turnstile in an embedded web view to prevent automated abuse. Cloudflare receives device and connection signals, including IP address, user agent and TLS connection information, together with the site key and domain. Forge receives the challenge result. This security check supports our legitimate interest in protecting accounts under Article 6(1)(f) GDPR; necessary device access relies on section 25(2) TDDDG.

Where offered, Google or Apple sign-in is optional. The chosen provider authenticates you and supplies an identity token and the email information needed for your Forge sign-in. Forge does not request access to your contacts, calendar or cloud files. The provider also processes data under its own terms; Google’s sign-in library declares identity, device and usage information, including processing for its own analytics. These options remain unavailable in the App until configured.

Forge does not use the App to track you across other companies’ apps or websites, create advertising profiles or run behavioural analytics. Optional vendor services still process the data described here. Aggregate provider-interest counts and consent-based error reports are separate from behavioural tracking.

Cloudflare privacy informationGoogle privacy informationApple privacy information

Optional YouTube and Vimeo videos

Providers can add up to three video links and titles, confirming that they have the rights needed to show them. Forge records that confirmation and keeps the links as part of the provider’s private working copy and last published profile. No video files or platform thumbnails are copied to Forge.

The player is blocked until you choose Allow and load for that video. Before this choice, Forge makes no request to the video platform. Once loaded, YouTube or Vimeo receives your IP address, browser information and the referring site and may use cookies or similar technologies, associate activity with an account or process data outside the EEA. Platform privacy links are provided beside the consent control. This optional loading relies on your consent under Article 6(1)(a) GDPR and, where applicable, section 25(1) TDDDG.

Consent applies only to that player while the page remains open. Unload video and withdraw consent stops the player and further requests from it; it cannot undo data already sent or clear cookies set by the platform. Reloading the page blocks players again. Watching directly on a platform opens its own website, under its privacy terms.

Favourites and exchanged business cards

Favourites are private to your account and separate from project shortlists. Providers see only how many active accounts currently save their profile, never who saved it. Business-card exchange requires a request and acceptance. Before acceptance, the other account sees your name and account type; afterwards, both accounts receive a saved copy of the selected card details. Later edits do not update those copies. A card code has no public card page, and camera scanning processes images on your device without uploading them.

You can remove a favourite or an exchanged contact. Removing a contact removes both saved cards from that connection, but cannot erase copies kept outside Forge. Pending requests expire after 14 days and are deleted by the daily cleanup. Declining, withdrawing or removing an exchange immediately clears its contact details; limited status metadata is deleted by the daily cleanup after 90 days. Abuse-prevention counters become eligible for daily cleanup after two hours. Cards, favourites and exchanges are included in account exports and removed when the owning account closes. Existing contacts remain readable after a paid plan ends.

Product feedback and AI help

When you choose to send feedback, Forge stores your account identifier, feedback category, message, language, generic page area and review status. Only you and authorised support staff can read it. We do not automatically collect screenshots, form contents or private page URLs. Feedback is included in your account export and deleted with your login or by the daily cleanup after 180 days.

When you ask the AI help assistant a question, Forge sends that question, up to six recent help exchanges and a generic page area to OpenAI, together with reviewed product guidance. The assistant does not read your projects, profile drafts, support tickets or payment records, and cannot make changes or send messages. Do not include passwords or sensitive details. Forge stores help messages for 30 days, includes them in your account export and lets you clear them earlier. Login deletion removes them too. Separate usage metadata is retained for 32 days to enforce limits; clearing chat does not reset those limits. We set store to false for these API calls. This does not mean zero retention by OpenAI: its default abuse-monitoring logs may retain API content for up to 30 days, subject to its applicable terms and legal exceptions.

Contacting Forge support

If you contact support while signed in, Forge stores your account identifier, verified email, topic, subject, messages, language and handling status. You and authorised support staff can read and reply to your tickets in the support area on Forge. Your account data export includes the conversation. Internal handling notes are accessible only to authorised staff. A reply reopens a resolved ticket. Tickets, replies and handling notes are deleted when your login is deleted or during the daily cleanup after 180 days have passed since resolution.

Organising incoming requests

Forge uses a private Trello board, provided by Atlassian, to organise incoming claims, profile applications, support requests, feedback, content reports, privacy requests and contract declarations. The cards contain only a generic category, request reference, status, receipt date and a link to the protected Forge Admin record. We do not copy your name, email address, message text, attachments or private handling notes to these cards. The reference can still be linked to your request within Forge.

For each new Trello card, Forge also sends a notification to a private Slack channel. Slack receives the generic category, Trello card number and card link, with link previews disabled. It does not receive your name, email, message text, attachments or private notes. These card references are pseudonymous, not anonymous: authorised staff can follow them back to the request.

This limited tracking supports our legitimate interest in reliably organising and responding to requests under Article 6(1)(f) GDPR. Trello does not decide the outcome of a request, and customer conversations remain in Forge. We schedule deletion of completed cards after 30 days and earlier when the underlying Forge request is deleted. Technical deletion failures are retried and flagged for attention. Slack notifications follow the workspace retention settings; deleting a Trello card does not automatically delete its Slack message. We remove related Slack notifications manually where required by a deletion request. The original Forge records follow their own retention periods described in this notice.

Atlassian data processing termsSlack privacy information

3. Private projects and Provider workspaces

A Seeker workspace can contain project goals, dates, places, budgets, milestones, service needs, briefs, saved providers, comparison evidence, private notes, introductions, exports and Coordinator proposals. A Provider workspace can contain claim evidence, provider-authored profile information, authorised media and rights metadata, service working processes, rates, presentation drafts, introduction settings and provider responses.

Private workspace data is available only to the owning typed account and authorised same-side members, subject to product access and database permissions. A customer controls when an introduction shares selected project information with an opted-in provider. Negotiation, contracting, delivery and provider payment remain outside Forge.

A direct enquiry from a Provider profile shares the Seeker account display name, subject and message only when an authorised member sends it. It does not automatically share the sender’s login email, phone, private profile or projects. The participating Provider chooses whether to accept and share its contact method. Forge keeps the request and response for the two accounts. Message text is removed 30 days after withdrawal or 90 days after acceptance, decline or expiry. Remaining request history, including the shared contact route, is deleted after 730 days under the request-retention rules.

4. Billing and consumer contracts

For a paid subscription we process the selected product and interval, billing and contract country, terms version and acceptance, Stripe customer, checkout, subscription and invoice references, payment state, cancellation, withdrawal, refund and dispute state. Stripe processes payment methods and full card or bank details; Forge does not store them.

Billing and contract data is processed to form and perform the subscription, provide statutory contract controls, defend or resolve claims and meet accounting and tax obligations under Article 6(1)(b), (c) and (f) GDPR.

Plans bought in the Forge app for iPhone and iPad are sold and billed by Apple, which processes the payment as an independent controller under Apple's privacy policy; Forge receives no payment details, name or email address from Apple. Forge receives Apple's signed record of the purchase and of later renewals, plan changes, refunds and cancellations: Apple's transaction identifiers, the product, the purchase, expiry and refund dates, whether the subscription renews, whether it is a test purchase, and the Forge account identifier the app attached to the purchase. Forge uses this to give that account its plan, to prevent a second subscription and to answer questions about the plan, under Article 6(1)(b) GDPR. It is kept while the account exists and deleted when the account is closed or deleted; the record of each notification Apple sends is deleted after 90 days.

5. OpenAI models: Coordinator, working processes and directory translation

When an authorised account member requests Coordinator assistance or help with a provider’s working process, Forge sends the necessary project, provider-draft or catalogue context to the OpenAI API. Forge requests non-persistent API processing and stores only the bounded result needed for the private review workflow, usage accounting and safe application of an explicitly accepted proposal.

Forge also uses the same API without any member request. The description text that Forge publishes on a public directory profile is sent to OpenAI in batches so the German version of that description can be produced, and this applies to researched profiles of organisations and of named individuals alike. Such a request carries the published description text, which can name the provider, together with an internal record identifier; it carries no account, contact or private workspace data. Non-persistent processing is requested here as well, and every imported translation keeps the model, prompt version and source-text fingerprint that produced it.

Whether a profile is published is decided by Forge's own controls and never by a model, and a model cannot write project or provider data directly, contact providers or approve a decision. Deterministic Forge code and an explicit customer action control every saved proposal.

6. Connected AI applications and OAuth

If you connect ChatGPT, Claude or another accepted client, Forge records the client, the authorising account, granted scope, connection state and security timestamps. The connected application receives only the Forge access that you approve and that the account's current product permits. You can revoke the connection from Forge and from the client.

Forge does not receive the external application's password and does not retain MCP prompts, tool arguments or tool results. The connected application processes information under its own account terms and privacy notice after you authorise it.

7. Email and notifications

Forge uses the verified account email for authentication, security, privacy, contract and account-administration messages. Contract confirmations and receipts for cancellation or withdrawal are required service messages and do not depend on optional notification preferences. Other workflow messages are sent only for registered-account events and only when that channel is active. Optional marketing is off by default and requires a separate, recorded consent that can be withdrawn at any time.

Email delivery providers receive the destination address and the minimum message data only when Forge sends the relevant email. Forge does not send permission requests or marketing to providers found through public research.

If you report allegedly illegal public content, Forge processes the profile location, category, explanation, good-faith declaration, contact details where supplied, review state, decision and delivery record in order to meet legal notice-and-action duties, protect affected people and document moderation. The reporter and affected Provider receive the required service messages independently of optional account-notification settings.

8. Website delivery, security and aggregate interest

Vercel, Supabase and network providers necessarily process request metadata such as IP address, time, requested address, browser or device information and security signals to deliver and protect the service. Anonymous report intake uses a daily changing keyed hash of the network address to limit repeated submissions. Raw addresses are not stored in this limiter; expired hashes are removed by the daily retention sweep, normally within three days. Forge keeps application security and audit records only where needed to investigate abuse, protect accounts, prove sensitive actions or meet legal duties.

Provider-interest reporting contains daily aggregate profile views, project saves and introduction requests. Public profile views do not use a cookie, device identifier or IP-derived identifier. Country information is retained only as an aggregate dimension and is shown to a provider only above the product's privacy threshold.

8a. Website error diagnosis and performance

Forge uses Sentry, provided by Functional Software, Inc., to detect website errors and investigate slow requests. Reports contain technical error messages, code locations, time, browser or runtime version, the affected page path, release information and sampled request timings. This supports our legitimate interest in operating a reliable and secure service under Article 6(1)(f) GDPR.

Forge disables automatic collection of account identity, cookies, request headers and bodies, query values, database query contents and AI inputs or outputs. Filters remove email addresses and recognised credentials from diagnostic text and replace the event IP address with a non-routable value. Sentry still receives network metadata when a report is transmitted. Do not put sensitive information into error reports. Session replay, screenshots and advertising profiles are not enabled.

Forge sends these diagnostics to Sentry’s EU ingestion service. Support and other processing by the supplier or its subprocessors may also take place outside the EEA under the safeguards described below. Diagnostic retention follows the active Sentry plan and our operational need to investigate failures; it does not extend retention of your Forge account or workspace records.

Sentry privacy informationSentry data processing terms

8b. Error reports from the App

The Forge App asks whether you want to allow optional error reports, with Allow error reports and Not now. The App remains usable if you refuse. Your choice is stored on your phone and can be changed at any time in Settings under Language and preferences. Neither the Dart nor the native part of Sentry’s software starts before you consent. This reporting relies on your consent under section 25(1) TDDDG and Article 6(1)(a) GDPR, separately from the Website configuration described in section 8a.

If you allow reporting, the App sends Sentry, provided by Functional Software, Inc., technical reports about errors and crashes: the error type and message, code locations, time, App version and build, and selected device and system details such as model, operating system, language, screen size and memory size. Reports exclude structured account identity such as account IDs, names and email addresses, Forge request or response payloads, and breadcrumbs recording earlier actions. Filters scrub email addresses, recognised access tokens, URL parameters and local installation paths from diagnostic text. This cannot guarantee anonymity: other personal information may remain in an error message.

After consent, Sentry’s software stores diagnostic files locally on your phone: queued reports, crash data awaiting the next start and state needed for crash detection. It also stores a random installation identifier locally; reports exclude that identifier. If you choose Not now, Sentry does not start, and any Sentry files remaining from earlier consent are deleted.

You can withdraw consent using Stop error reports in Settings. Withdrawal stops new reporting and deletes queued reports and Sentry’s local files, including its installation identifier. A report already in transit may still arrive. Withdrawal does not automatically erase reports already received by Sentry and does not affect the lawfulness of processing before withdrawal; your data rights are described in section 11.

The App replaces the report’s IP address with a non-routable value. Sentry’s server-side data scrubbing and Prevent Storing of IP Addresses setting are enabled. Sentry still receives network metadata when a report is transmitted. Reports go to Sentry’s EU ingestion service. The supplier-processing, international-transfer and diagnostic-retention limits in sections 8a and 9 also apply to these reports; EU ingestion does not mean all processing stays in the EEA.

Session replay, screenshots, performance tracing, profiling, logs and metrics remain disabled in the App.

8c. Videos, QR scanning and Wallet in the App

The App loads a provider’s YouTube or Vimeo player only after you allow that video. It uses YouTube’s privacy-enhanced player or Vimeo with its do-not-track option. The platform receives connection and device data and the playback request; the referring page identifies Forge’s website. Closing the player or withdrawing consent stops further player requests. Before consent, covers come from Forge, not the video platform. The consent basis and limits in the video section above apply to the App too.

The camera opens only when you choose to scan a business-card code and allow camera access. On iPhone, Apple’s AVFoundation reads it on the device. On Android, Google’s ML Kit code reader through Play services also reads it on the device, but sends diagnostic and usage data with device and app identifiers to Google. Neither scanner uploads pictures or the code it reads to Google or Apple. The App uses the recognised Forge code to look up the card with Forge.

Android asks for your consent before using Google’s code reader. You can withdraw it in Settings and enter the card code manually instead. Optional reader processing relies on Article 6(1)(a) GDPR and, where applicable, section 25(1) TDDDG. Camera permission and consent to Google’s reader are separate choices.

Adding a card to Apple Wallet or Google Wallet is optional and follows section 9a. The App sends its access token only to Forge’s pass endpoint, never to the Wallet provider. On Android, Google Play services checks whether Wallet supports passes and opens Google’s save sheet when you choose it. Google’s Pay library processes account and device identifiers, interactions in that sheet and crash information under Google’s terms. Forge does not log or retain the pass or save token on the phone.

Google ML Kit data disclosureGoogle Pay library data disclosure

8d. Public Website traffic statistics

We use Vercel Web Analytics to understand which public pages people visit and improve the Website. Reports include the page address, referring website, visit time, approximate location and browser, device and operating-system information. We remove URL query parameters and fragments before sending page views. Sign-in, account, project, Provider Studio, private preview and invitation journeys are excluded. We do not send custom events, form contents or account identities.

Vercel uses a hash derived from request information to distinguish visits within a day; that visitor session is discarded after 24 hours. Analytics does not place cookies or persistent visitor identifiers on your device and does not track you across websites. Vercel still receives network metadata when your browser sends the request. Aggregate reports remain available according to the active Vercel plan.

This processing supports our legitimate interest in understanding and improving the public Website under Article 6(1)(f) GDPR. It is separate from the aggregate Provider statistics described above and does not apply to the native App. You may object to this processing using the contact details in this notice.

Vercel Web Analytics privacy information

9. Processors and transfers

For disaster recovery, Forge stores encrypted copies of uploaded profile pictures, banners, portfolio images, thumbnails and their rights and description information with Backblaze B2 in the selected EU storage region. Files are encrypted before upload. GitHub Actions is configured to run this backup process and temporarily processes readable source files and restored copies for verification; these temporary files are removed after the job. The EU storage location does not mean all processing by these providers is confined to the EEA.

Forge uses Supabase for the EU-hosted operational database and authentication, Cloudflare for Turnstile security checks, Google for chosen Google authentication, Android code-reader or Google Wallet use, Apple for chosen Apple authentication or Apple Wallet use, Vercel for hosting, content delivery and the public Website traffic statistics described above, Stripe for payments and invoices, OpenAI for requested product help, Coordinator assistance and reviews of provider working processes and for the German translation of published directory profile text, Mailjet for Forge email when that delivery channel is active, Atlassian Trello for the limited request-tracking metadata described above, Slack for the associated new-work notifications, and Sentry for the limited Website error and performance diagnostics and optional App error reports described above. These providers receive only the data required for their function and act under their applicable data-processing terms.

Where a provider processes data outside the EEA, Forge relies on an applicable adequacy decision or contractual safeguards. Public provider facts are, by their nature, available wherever the public directory can be opened; private account and workspace data is not made public.

9a. Optional cards in Wallet

Provider Links cards, Provider Business cards and Seeker Business cards can be added to Apple Wallet or Google Wallet when available for the account. A Links card contains published Provider identity, picture and the public Links Page address; its QR opens that page without a Forge account. A Provider Business card contains its identity, chosen public contact lines, profile address, picture and exchange code. A Seeker Business card uses the saved private Seeker profile, picture and contact details with an exchange code; adding it to Wallet does not create a public Seeker profile.

When you request a Google Wallet pass, Forge sends Google the applicable card details while preparing it, even if you cancel the add screen. Google keeps the pass if you add it. Apple Wallet stores the signed pass, including its embedded picture where present, and processes it under Apple’s Wallet terms. These optional services have their own privacy notices and may process data outside the EEA.

For Apple updates, Forge stores a device library identifier and push token for each registered pass, plus a hash of the pass’s authentication token. The account export includes Wallet metadata and registrations, but no signing credentials or authentication-token hashes. Card changes queue an update; delivery depends on Apple, Google and the device being reachable. Paused or replaced exchange codes stop working in Forge immediately, even if a device still shows an older card.

Closing the account or removing an owner/manager removes its device registrations and queues voided Apple passes and expired Google passes with the card details removed. Forge keeps final push destinations for at most 24 hours and a minimal revocation record (pass identifier, token hash and one-way device digests, without account or profile links) for 30 days so installed passes can retrieve the final update. Cleanup retries if interrupted. Wallet providers or offline devices may retain previously received copies; you can remove the card in Wallet.

Apple, Apple Wallet and iPhone are trademarks of Apple Inc., registered in the U.S. and other countries. Google Wallet is a trademark of Google LLC.

10. Retention

Account and workspace data is kept while the account is active and then deleted, anonymised or restricted after a valid deletion request, except where continued retention is required for contracts, accounting, security, disputes or another legal obligation. Billing records are retained for the applicable statutory period. Closed claim, privacy-request and content-moderation records are normally retained for up to three years; minimal suppression or publication-restriction identifiers may remain while Forge operates so a removed or restricted item is not silently recreated.

Aggregate provider-interest rows are retained for 90 UTC calendar days (today and the preceding 89 days), with older rows removed by the daily cleanup. Short-lived delivery and security records are retained only for the period necessary for their purpose. Provider-authored public content remains until it is changed, unpublished or removed through the applicable account or rights process.

Encrypted picture-backup snapshots are retained for 30 days. Expired copies are removed by the backup cleanup process; storage-provider deletion can take a further day, and a failed cleanup can delay removal until it is resolved. Backup copies are restricted to recovery. Before recovered content returns to service, Forge reapplies later deletions, rights withdrawals and publication restrictions. These backups support service continuity and data protection under Article 6(1)(f) GDPR; they do not give Forge permission to republish withdrawn content.

11. Your choices and rights

Forge answers a deletion request within one month.

Subject to the legal conditions, you can request access, correction, deletion, restriction, portability or object to processing based on legitimate interests. You can withdraw optional consent at any time without affecting earlier lawful processing. Forge does not make a solely automated decision that has legal or similarly significant effects on you.

You may complain to a data-protection authority. The supervisory authority responsible for Forge is the Bavarian State Office for Data Protection Supervision (BayLDA), Promenade 18, 91522 Ansbach, Germany.

Request deletion of your Niflheim Forge account

12. People in Switzerland

Where the Swiss Federal Act on Data Protection (FADP) applies, Forge also observes its transparency, proportionality, purpose and personality-right requirements. The GDPR Article 6 wording above describes European lawful bases; the FADP does not use the same lawful-basis catalogue.

For researched public provider profiles, Forge uses limited professional facts from provider-controlled sources or an applicable official public register and relies on its overriding private interest in operating a factual directory where the Article 30(3) FADP presumption for data made generally accessible does not apply. Public availability alone is not blanket permission. The separate profile policy explains the assessment under Articles 19, 20, 30 and 31 FADP and the correction, objection, restriction and removal controls.

A person in Switzerland may report a data-protection concern to the Federal Data Protection and Information Commissioner (FDPIC). The FDPIC recommends contacting Forge first and does not decide individual civil disputes.

Report a concern to the FDPIC

13. Required and optional information

An email address, account type and account name are required to create a Forge account. Information marked optional can be left unknown. Without the data needed for a requested product, security check, payment, introduction or rights request, Forge may be unable to complete that specific action but does not convert the account into another type.

Public provider profiles have a separate policy

Read how Forge verifies public professional facts, handles unknown information and supports correction, objection, restriction and removal.

Read the data and profile policy

Ask about your Forge data

Include the account email or public profile address involved and describe the right or correction you want to exercise.

Email the controller