Privacy policy
How Jynhold processes personal information for Magnetly: what is collected, providers, transfers, retention periods and rights.
1. Status and scope
Version dated 9 November 2026. This text describes the Magnetly v2 processing as the service implements it.
This notice concerns the Magnetly website, business accounts, support and service operation. If you answer a form created by a Magnetly customer, that customer’s privacy notice also explains why it collects your information and how it uses it.
2. Who is responsible for your information?
Magnetly is a product operated by Jynhold, a French simplified joint-stock company (SAS) with share capital of €1,000, registered with the Paris Trade and Companies Register under number 992 428 581, whose registered office is at 50 avenue des Champs-Élysées, 75008 Paris, France.
For business-account administration, its own customer relationships, support, billing records and service security, Jynhold determines the relevant purposes and acts as a data controller. Contact: [email protected]. Jynhold has not appointed a data protection officer (DPO), as it is not required to; privacy requests are handled at this address.
For personal information collected through a customer’s forms, the customer normally acts as controller and Jynhold processes that information on its instructions. If the customer itself acts for another controller, the applicable contractual chain must reflect that role. These activities are covered by the data processing agreement (DPA).
3. Information involved and where it comes from
- Business accounts: email address, name and, with Google sign-in, profile picture; workspaces, members and invitations (invited address; only a hash of the invitation link is kept); AI assistants connected through the MCP server (client name, consent and access tokens); for each sign-in session, IP address and browser (user agent).
- Customer content: conversations with Magnetly’s AI, tools and their versions, uploaded files, product catalogues, brand and website pages imported at the customer’s request.
- Subscriptions and purchases: plan, subscription status and periods, Stripe customer and subscription identifiers, credits granted and used. Payment events received from Stripe are kept without name, email, address or signed link; payment-card data never reaches Magnetly.
- Support and correspondence: contact details, messages and attachments that you choose to send.
- Service operation: a record of AI calls (model, provider, volumes and cost; for a web search, its queries and the addresses read); abuse-limiting counters, some keyed by IP address; error reports without IP address, cookie, header, request body or user identity; the host’s runtime logs.
- Product analytics of the application: events that Magnetly’s server records when a signed-in user acts in the application (signing up and in, creating, saving, previewing, publishing and sharing a tool, imports, cards, paywalls, purchases, settings), each with the user’s internal identifier, the workspace’s public identifier and plan, the kind of action and counts (for instance a message’s length in a range); never the content of prompts, tools, products or files, nor an email address, a name, an IP address or any visitor’s data. The application sets no analytics cookie and loads no analytics script in the browser.
- Customer-form information: depending on the customer’s configuration, visitors’ email, first name, last name, telephone, LinkedIn details, consent and answers; for each session, where it came from: channel, embedding page without query parameters, referring site’s domain,
utm_*parameters and device type, and the journey’s events (display, screens viewed, clicks on the result), which feed the customer’s analytics. No IP address or cookie is tied to a visitor’s session. The customer selects its questions and purposes.
Information is provided directly by users or visitors, by the customer configuring the service, by the chosen sign-in/payment services, or through technical service operation. You should not enter special-category data, criminal-conviction data or unnecessary personal information into prompts or free-text fields. Any permitted special use requires a separate assessment and written agreement.
4. Purposes and legal bases
| Purpose | Legal basis for Jynhold’s own processing |
|---|---|
| Open and administer an account, provide the subscribed service and manage a subscription | Performance of the contract when the individual is the customer; otherwise Jynhold’s legitimate interest in administering its relationship with the customer organisation and its authorised users |
| Respond to a request or provide support | Pre-contractual steps or performance of the contract where applicable; otherwise the legitimate interest in responding to business correspondence |
| Keep required accounting and tax records | Compliance with applicable legal obligations |
| Protect accounts, prevent abuse, diagnose errors and maintain the service | Legitimate interests in service security and reliability, subject to necessity, minimisation and users’ rights |
| Measure how the application is used to improve it (product analytics events recorded by Magnetly’s server, without cookie) | Legitimate interest in understanding and improving the service, limited to the user’s internal identifier, workspace, actions and counts, never content; objection at [email protected] |
| Measure the audience of the marketing website (www.magnetly.co) in the browser with PostHog: pages viewed, clicks on calls to action, scroll depth and, if chosen separately, session replay with typed text masked | Consent, given in the website’s cookie banner before anything is loaded or stored, as easy to refuse, withdrawable at any time from “Cookie settings” at the bottom of each page (cookie policy) |
For leads and answers processed on behalf of a customer, that customer determines and discloses the purpose and lawful basis. A customer’s use of Magnetly does not, by itself, establish consent for marketing. Reading this policy, browsing the site or accepting the service terms does not constitute consent to optional tracking or unrelated marketing.
5. AI processing and prompts
Lead contact fields (email, first name, last name, telephone, LinkedIn, consent) are never sent to the AI. Visitors’ free-text answers, customers’ messages and instructions, and imported pages, files and catalogues can however contain personal information, and are sent to the models when the operation requires it. Customers and users must avoid inserting unnecessary personal information into that material and remain responsible for the questions and content they configure.
Every AI request goes through OpenRouter, which routes it only to providers that retain no data (“zero data retention”) and exclude its collection. As of this version: building and editing tools with DeepSeek V4.1 Flash (Together AI and Baseten first); the result shown to a visitor with gpt-oss-120b (Groq and Cerebras first); the agent’s web search with gpt-oss-20b and the Exa search engine; dictation with Whisper Large V3 Turbo (DeepInfra and Groq). Other zero-retention providers may take over when the first ones are unavailable. OpenRouter, these providers and Exa are established in the United States.
Dictation is transcribed without being stored: neither the recording nor its transcript is kept by Magnetly, and the text is saved only if you then send it as a message. ZDR is a provider and routing configuration, not a guarantee that every category of metadata or every legally required record is absent. The model providers and Exa are engaged by OpenRouter, not by Jynhold, and are not certified under the Data Privacy Framework. Requests are routed only to providers that OpenRouter classes as retaining no data, and lead contact fields are never part of them. Jynhold has asked OpenRouter for the contractual chain with these providers (Article 28(4) GDPR) and the basis of their transfers. This notice does not claim a universal guarantee about all third-party models or training practices.
6. Recipients and service providers
Information is accessible to authorised Jynhold personnel only to the extent needed for their duties, to the customer’s authorised workspace users for customer-controlled information, and to the relevant providers used to deliver the service. Authorities or advisers may receive information where lawfully required or necessary for legal claims.
Jynhold’s processors: Railway Corporation (hosting of the application and the marketing website, EU West region, Amsterdam); Databricks, Inc., for Neon, LLC (Postgres database, AWS eu-central-1 region, Frankfurt); Cloudflare, Inc. (DNS, network and protection, file storage on R2 under EU jurisdiction, delivery of the embed script through Pages, customers’ custom domains); Plus Five Five, Inc., doing business as Resend (transactional email, eu-west-1 sending region, without open or click tracking); Modal Labs, Inc. (isolated environment for catalogue imports, EU region); Functional Software, Inc., doing business as Sentry (error reports, EU data region); PostHog, Inc. (product analytics of the application, events sent by Magnetly’s server; and, only with the visitor’s consent, audience measurement and session replay of the marketing website in the browser; EU data region, Frankfurt); OpenRouter, Inc. (routing of AI requests to the providers listed above and Exa); Google Cloud France SARL (Google Workspace: the [email protected] mailbox, including support). All of these companies except Google Cloud France are established in the United States.
Acting for their own purposes, as independent controllers: Stripe, through Stripe Payments Europe, Limited (Ireland), Jynhold’s contracting party under the Stripe agreement, with Stripe, LLC (United States), for payments, fraud, tax and transaction support; as Jynhold understands it, under Stripe Managed Payments, Link (Sold through Link, LLC), merchant of record without being the seller of the service (Jynhold supplies Magnetly), acts as an independent controller of buyers’ payment data; Google for optional sign-in with a Google account, which it controls: this third-party service is not a Jynhold processor. Their own notices apply; Stripe’s privacy policy describes its processing. Magnetly uses no advertising tool. The application loads no measurement script in the browser: its only measurement is the server-side product analytics described above. Only the marketing website measures its audience in the browser, with PostHog, after the visitor accepts it in its cookie banner, as described in the cookie policy.
The DPA repeats this register for customer data, with each provider’s transfer safeguard and a link to the list of its own subprocessors.
7. International transfers
The application’s data is hosted in the European Union: application in Amsterdam, database in Frankfurt, files in R2 buckets under EU jurisdiction, emails sent from the eu-west-1 region, error reports, product analytics and the import environment in EU regions. Several providers are however companies established in the United States, and AI requests (OpenRouter, model providers, Exa) are processed in the United States: transfers outside the European Economic Area therefore take place.
Transfer safeguards for each provider established in the United States: Railway is certified under the Data Privacy Framework (EU–US, with its UK and Swiss extensions), found adequate by the European Commission’s decision of 10 July 2023, with the standard contractual clauses of decision 2021/914 (modules 2 and 3) as a fallback; Databricks and Neon are certified under the Data Privacy Framework, and Neon’s DPA includes the standard contractual clauses (modules 2 and 3); Cloudflare and Sentry are certified under the Data Privacy Framework, with the standard contractual clauses as a fallback; Resend is certified under the Data Privacy Framework (EU and UK), with the standard contractual clauses (modules 2 and 3); PostHog transfers under the standard contractual clauses of its DPA; Modal and OpenRouter, which are not certified, transfer under the standard contractual clauses (module 2); for Google Workspace, Google LLC is certified under the Data Privacy Framework, with the standard contractual clauses of its Cloud Data Processing Addendum. The model providers and Exa, engaged by OpenRouter, are not certified: Jynhold has asked OpenRouter for the basis of their transfers. Stripe, LLC, which receives data from Stripe Payments Europe, is certified under the Data Privacy Framework, with the standard contractual clauses of Stripe’s Data Transfer Addendum.
A controller–processor agreement does not replace these transfer safeguards. A copy of the applicable safeguards can be requested at [email protected].
8. Retention and deletion
Personal information is retained only for the purpose that justifies it, with any legally required archive separated from ordinary use. Periods Jynhold applies:
- Accounts: kept for the duration of the contract. An inactive account, with no sign-in for 3 years, is deleted after an email notice. An account can also be deleted at any time from Account settings; its sessions, sign-in methods, access granted to AI assistants and workspace memberships are then erased at once, together with the workspaces of which it is the only member.
- Email of a deleted account: a keyed hash (HMAC) of the address, never the address in clear, is kept for as long as needed to prevent a new account opened with the same address from receiving a second free trial.
- Connection data: IP address, browser and time of each sign-in, with the account identifiers, kept for 1 year, the period set for data identifying people who create online content (article 6 of the French law on confidence in the digital economy, LCEN, and decree no. 2021-1362).
- Tools: a deleted tool disappears at once and is no longer served; 30 days later, its sessions, responses, leads, events, versions, catalogue, conversation and files are erased for good.
- Workspaces: when its owner deletes a workspace, its members lose access and its invitations are revoked at once; its data is erased under the same 30-day rule.
- Responses and leads (processed on the customer’s behalf): kept as long as the customer keeps the tool; erased within 30 days of the tool’s deletion or of the end of the contract (defined below). They can be exported as CSV. The interface does not delete a single lead: such a request goes to [email protected].
- Accounting records and invoices: 10 years (article L123-22 of the French Commercial Code).
- Support exchanges and evidence of the contract: for the duration of the relationship, then 5 years in intermediate archive, the civil limitation period (article 2224 of the French Civil Code).
- Technical logs (Railway host logs, Sentry error reports): as long as needed for security and debugging, 1 year at most.
- Product analytics (PostHog): events kept for the retention period of PostHog’s plan, at most 1 year; a deleted account’s events are erased at PostHog with it.
- Marketing website audience measurement (PostHog, with consent only): events at most 1 year, session recordings at most 30 days; PostHog’s
ph_*cookie at most 13 months and the cookie choice 6 months on the visitor’s device, both erased as soon as consent is refused or withdrawn. - Technical data: abuse-limiting counters erased after 24 hours; uploaded files attached to no tool or workspace erased after 24 hours; sign-in sessions valid for 7 days; invitation links valid for 7 days.
- AI-call record and payment events: kept, detached from the deleted tool or workspace, for billing and credit accounting.
- Backups: the database can be restored to any point in the last 7 days, a restore tested on 9 November 2026; erased data can therefore remain for up to 7 days in that history, outside ordinary use.
End of the contract: The contract ends when the customer deletes the workspace, or the account that owns it, or when that account is deleted after 3 years without a sign-in; the workspace’s data is then erased within 30 days. A workspace whose subscription or trial has ended stays read-only, with its data kept, until one of those events.
The 12-month validity of purchased credits and the one-month rollover of subscription credits are commercial rules, not personal-data retention periods.
9. Your rights and how to exercise them
Subject to the conditions in the GDPR, you can request access, correction, erasure or restriction, object to processing based on legitimate interests, and request portability for eligible information processed automatically on the basis of consent or contract. Where processing is based on consent, you may withdraw it without affecting earlier lawful processing. You can object to direct marketing at any time where it is carried out.
For Jynhold-controlled information, contact [email protected] with enough information to identify your request. Additional identity information is requested only where reasonably needed. Jynhold responds within 30 days; this period may be extended by two months where the complexity or number of requests justifies it, with notice within the first 30 days.
From the application, you can delete your account (Account settings), a tool or a workspace, and export a tool’s responses and a workspace’s leads as CSV. There is no full account export in the application: request it at [email protected] and it is provided within the same 30 days.
For a form you answered, contact the business identified on that form first: it controls the use of your answers. Jynhold will assist that customer under the DPA and will forward or coordinate a request received directly as appropriate.
You may complain to the French data protection authority, CNIL, or another competent supervisory authority.
10. Required information, automated decisions and security
Information necessary to create an account, authenticate or complete a purchase must be supplied for that requested service to work. Optional information should be identified at collection. Each customer must similarly identify required and optional fields in its own forms and explain any consequences of not providing them.
AI-generated recommendations and classifications should be reviewed in context. This document does not authorise a customer to use Magnetly for a solely automated decision producing legal or similarly significant effects without the required legal assessment, safeguards and information.
Jynhold applies technical and organisational measures appropriate to the risks and limits access to authorised persons. Measures in place, detailed in Schedule 3 of the DPA:
- traffic encrypted with TLS, HSTS in production and security headers on every response of the application; the application reachable only through Cloudflare; the database reachable only over TLS with certificate verification;
- passwordless sign-in, with a one-time code sent by email or with Google, and sessions stored on the server;
- each workspace’s data accessible to its members only, a control covered by integration tests; for support, access by Jynhold administrators through a logged sign-in limited to 24 hours;
- rate limits against abuse; secrets kept in the host’s environment, never in the code;
- encryption at rest provided by the storage providers (Neon for the database, Cloudflare R2 for files); the database can be restored to any point in the last 7 days, a restore tested on 9 November 2026;
- catalogue imports run in an isolated environment, limited in memory and reaching only public internet addresses; pages read by the server limited to public addresses;
- error reports without personal data; AI requests routed only to providers that retain no data;
- an automated test suite (unit, integration and end-to-end) run before each change is merged; daily purge tasks.
Jynhold holds no security certification (ISO 27001, SOC 2 or other). In the event of a personal data breach for which it is the controller, Jynhold notifies the CNIL within 72 hours where the law requires it and informs the people concerned where the risk is high.
11. Cookies, external services and updates
Cookies, browser storage and similar technologies must be described according to their actual use. Technologies strictly necessary to provide a service requested by the visitor may have a different consent regime from optional analytics, advertising or third-party tracking. Where consent is required, optional technologies must remain inactive until a valid choice is made, with an equally easy refusal and a continuing way to withdraw consent.
The marketing website is described in the cookie policy: it keeps the visitor’s choice in magnetly-lp-consent (6 months), and its PostHog cookies and storage (ph_*) for audience measurement and session replay are set only after the visitor accepts them in its cookie banner, can be refused as easily and are erased when consent is withdrawn from “Cookie settings” at the bottom of each page. The Magnetly application and the published tools use only storage needed for the service requested, set by Magnetly itself, with no advertising tracker, no analytics cookie and no audience-measurement script (the product analytics described above is recorded by Magnetly’s server):
| Name | Where | Purpose | Duration |
|---|---|---|---|
better-auth.session_token (prefixed __Secure- over HTTPS) | Application, cookie | Keep the sign-in session | 7 days, renewed with use |
magnetly_terms | Application, cookie | Carry the acceptance of the Terms of Service and the Privacy Policy, ticked on the sign-in form, to the creation of the account | 1 hour |
magnetly_last_workspace | Application, cookie | Reopen the last workspace viewed | 1 year |
sidebar_state | Application, cookie | Remember whether the sidebar is open | 7 days |
theme | Application, local storage | Remember the light or dark theme | Until cleared |
magnetly:dictation-microphone | Application, local storage | Remember the microphone chosen for dictation | Until cleared |
magnetly.preview-as | Application, local storage | Remember the chosen preview format | Until cleared |
magnetly.pending-prompt.*, magnetly.pending-attachments.* | Application, session storage | Hand the request and files typed on the Dashboard to the tool created | Until sent, at most until the tab closes |
mg:walk:* | Published tools, local storage of embed.magnetly.co | Resume an interrupted journey, without the email or other contact details | Until cleared |
magnetly:shown:<embed> | Published tools, local or session storage of the customer’s site | Not reopen on its own a popup already shown to the visitor | Until cleared, or until the tab closes |
magnetly:done:<tool> | Published tools, local storage of the customer’s site | No longer open on its own the popup of a tool already completed | Until cleared |
The fonts, images and files of published tools are served from files.magnetly.co: a visitor’s browser loads no font from Google.
External websites opened through a link have their own notices. The final version of this notice will state its effective date. Material changes will be communicated through an appropriate channel before a new incompatible purpose is introduced, with consent obtained where required.