Privacy & request terms
Effective 10 September 2026. Controller: Daniel Steen, operating the isolated Money Foundry experiment. This page concerns only this pilot.
Initial request
If you request the pilot, we collect only your business email, role or company type, problem category, deadline, confirmation that you saw the displayed USD 249 price, and consent for Money Foundry to respond. We use these details only to assess and respond to your voluntary request. We do not request files, credentials, payment details, or personal customer data in the first form. No marketing subscription is created.
Reachability and private portal
The form creates a private request portal with an unguessable access link. Anyone holding that link can read the request status, reply, download an available delivery, or delete the request, so keep it private. The portal is the working fallback contact channel.
Transactional email is available only when the application explicitly reports that a dedicated sender is enabled. If email is disabled, the request is not a reachable lead and no email delivery is claimed. When enabled, an email provider may accept a verification message, but provider acceptance is not delivery or proof of ownership. Email ownership is recorded only after the recipient uses a short-lived, single-use verification link. Verification alone is classified as PROBABLE_HUMAN, not a documented verified independent human.
Status emails contain no request details or customer files. They provide a new one-use portal access link that expires after 60 minutes. Money Foundry can post factual scope or status notices through the portal. There is no guaranteed response or delivery time.
Scope files
Only after verified email ownership and a scope request may you upload one to five related JSON source/target pairs. Each file is limited to 64 KiB, each authoritative source to 500 string leaves, and the complete bundle to 640 KiB and 2,500 source string leaves. You must state the failing import, validation, or reconciliation condition and confirm ownership or authority to submit the files.
Files are encrypted before application storage and are never placed in email. The deterministic scope stage may reject or isolate unsupported inputs. Placeholder, missing-key, extra-key, semantic, language, build, and runtime findings may remain in a human review queue. Do not include personal customer data, secrets, executable content, or unsupported formats.
Output and payment boundary
A request asks Money Foundry to assess an unvalidated USD 249 pilot. It is not an order, reservation, accepted scope, payment, or revenue. Live payment is unavailable until a legitimate dedicated provider is enabled. No charge may occur before email ownership and scope are accepted and a legitimate checkout is available.
If an accepted and legitimately paid pilot is fulfilled, the private portal may provide a bounded ZIP containing candidate repaired files, machine-readable and unified diffs, repair receipts, validator results, and an unresolved-review queue. The ZIP is separately integrity-checked and remains available for at most seven days. Candidate output does not guarantee linguistic correctness, successful import/build/runtime behavior, production safety, or fitness for deployment. You remain responsible for language and real-system review.
Retention and deletion
Active request content expires after 30 days and is removed on the next cleanup cycle. Uploaded scope files are deleted when you delete the request, after a successful private delivery is sealed, or when the request expires. Private delivery artifacts expire after at most seven days. Plaintext operator workspaces are task-owned, short-lived, and must be deleted at the end of each bounded run; a cleanup failure stops the run rather than claiming successful cleanup.
Use the deletion action in your private portal to withdraw the request. It immediately changes the request to a non-active DELETED tombstone, revokes access exchanges, and purges contact details, messages, files, artifacts, email outbox entries, and job records. The contact-free tombstone remains for up to 24 hours to prevent a concurrent request from recreating deleted data. Infrastructure backups and logs follow provider retention and cannot be selectively erased by the application.
Email provider receipts and event identifiers may be kept for up to 30 days, send-attempt records for up to 31 days, and completed or failed outbox records for up to seven days or the request expiry, whichever arrives first. For abuse prevention, short-lived global and recipient send counters remain for at most two days even when a request is deleted. The recipient counter is a keyed pseudonymous value and contains no raw email address. Hosting providers may process operational data internationally; this pilot does not promise EU-only storage.
Security
Request details, messages, files, and artifacts are encrypted before storage in the dedicated Money Foundry application database. Access requires a private capability link, a dedicated least-privilege automation credential, or a separate operator credential. Provider credentials and access links must not be logged or published. No security measure removes all risk, so submit only the bounded material needed for this pilot.
Privacy-minimizing measurement
The application stores daily aggregate counts for page views, offer views, example interactions, form starts, lead submissions, scope and payment stages, delivery, deletion, and refunds, separated by a small source category and traffic classification. It does not store raw IP addresses, full user-agent strings, full referring URLs, analytics cookies, device fingerprints, or advertising identifiers. A user-agent may be examined transiently to identify obvious bots and is not retained by this application. Providers may separately retain operational or security logs under their policies.
Aggregate event buckets are kept for 30 days. VERIFIED_HUMAN, PROBABLE_HUMAN, UNCLASSIFIED, BOT, and CONTROL remain separate. Email verification alone is not VERIFIED_HUMAN. Event counts are not unique people, and an anonymous visit, click, provider receipt, or automated check is not reported as a genuine independent user.
Your choices and contact
No pilot request is necessary. You may open a private privacy or support inquiry without confirming a price, role, or deadline. You may request access, correction, deletion, or restriction through the reply box in your private portal. You may withdraw response consent and delete the request there. You may also complain to your data protection authority, including Datatilsynet in Norway.
Providing request details is voluntary; without a working private portal or verified transactional email, Money Foundry cannot continue the request. The initial form does not make an automated legal or similarly significant decision.