Privacy & Data Handling Notice
This Notice explains how Jamey processes personal data in connection with Jamey.lu and its related business services. The English version is the authoritative one; French and German pages summarise the contact details and point here.
Effective 19 August 2026 · Last updated 19 August 2026
1. Purpose and contact details
This Privacy & Data Handling Notice explains how Jamey S.à r.l.s, 177, Rue de Luxembourg, L-8077 Bertrange, Luxembourg, Luxembourg Trade and Companies Register no. B288826 (Jamey, we, us or our), processes personal data in connection with Jamey.lu and its related business services.
For privacy questions or to exercise your rights regarding data for which Jamey is controller, contact privacy@jamey.lu. Before publication, Jamey will ensure that this mailbox is active and monitored.
This Notice does not replace the privacy notice of a business that uses Jamey as its CRM platform. Where Jamey processes personal data entered by a business customer into that customer's CRM or workspace, that business is normally responsible for explaining the processing to the people concerned.
2. The two data-protection roles
Jamey has different roles depending on the data and purpose:
| Situation | Who decides why the data are used? | Jamey's role |
|---|---|---|
| Your Jamey Account, authentication, billing, account administration, support request, security log, and Jamey's own B2B relationship with you | Jamey | Controller |
| Your employer's or another business's CRM records, contacts, client links, campaign audiences, website-form data or other data placed in the Services for that business's own purposes | The business customer | Processor/service provider, acting on that business's instructions |
One reusable Jamey Account across businesses
A Jamey Account is a central account that can be created through a participating Jamey business page and used to sign in to another participating Jamey business. Jamey is the controller of the central account identity, credentials, authentication, account-security information and central account-management preferences.
When you deliberately choose to join, sign in to or use another Jamey business, we may share only the minimum information needed to set up that new relationship: normally your Jamey Account identifier, verified sign-in status, name and email address. That new business is responsible for its own service relationship with you and must show its own relevant terms and privacy notice.
We do not automatically share your prior orders, delivery addresses, booking history, payment data, CRM records, campaign preferences or activity from one business with another simply because you use the same Jamey Account. If a feature allows you to share saved details with a new business, it must clearly show the recipient and the fields before you confirm the transfer.
Account reuse is a login convenience; it is not the GDPR right to data portability and does not authorise a broad transfer of information between independent businesses. The statutory right to data portability remains available where applicable under section 14.
If you are a contact, client, prospect or employee appearing in a business customer's Jamey CRM, please contact that business first to exercise your privacy rights. We will assist the business as required by applicable law and our contract.
3. Personal data we process as controller
Depending on your interaction with Jamey, we may process the following categories:
| Category | Examples |
|---|---|
| Identity and account data | Name, work email address, telephone number, account ID, business/organisation, role, login and authentication details. |
| Subscription, payment and connected-account data | Plan, orders, invoices, payment status, VAT/business information, payment-provider reference data, and—where Stripe Connect is used—business, representative, beneficial-owner, verification, payout and transaction information required for onboarding and payment operations. We do not intentionally store full payment-card details when Stripe handles them. |
| Support and communications data | Messages, feedback, call/meeting notes, support tickets, account requests and WhatsApp B2B communications with you. |
| Technical and security data | IP address, device/browser information, timestamp, authentication events, audit/activity logs, cookie identifiers where applicable, error and security information. |
| Business relationship data | The business you represent, your role, contract and onboarding status, preferences and communications relating to Jamey's own B2B relationship with that business. |
Please do not send special-category data, passwords, payment-card details or other sensitive information in routine support messages unless we specifically ask for it through a secure channel.
4. Why we process controller data and our legal bases
We process controller data for the purposes below, each with its typical legal basis.
| Purpose | Typical legal basis |
|---|---|
| Create and administer accounts; provide the Services; authenticate users; manage subscriptions and respond to service requests | Performance of a contract or steps taken at your request before entering a contract (Article 6(1)(b) GDPR) |
| Issue invoices, keep financial records and meet legal/regulatory obligations | Compliance with a legal obligation (Article 6(1)(c) GDPR) |
| Protect accounts and Services; prevent fraud, abuse and unauthorised access; maintain logs; improve reliability; handle business administration and legal claims | Legitimate interests (Article 6(1)(f) GDPR), balanced against your rights and freedoms |
| Send product news or direct marketing about Jamey's own B2B services | Consent where required, or legitimate interests where legally permitted; you may object at any time |
| Use optional cookies or similar technologies | Your consent where required by applicable law |
When we rely on legitimate interests, those interests include operating a secure and sustainable B2B service, communicating with current or prospective business customers, improving the Services, and defending legal claims. You may object to processing based on legitimate interests as described in section 14.
5. WhatsApp: B2B communications only
Jamey uses WhatsApp only to communicate with a Customer's representatives and Authorised Users in a B2B context. We may use it for onboarding, support, service-operation information, meeting coordination and matters concerning the contractual relationship.
We do not use WhatsApp to contact a Customer's own CRM contacts, clients or prospects for Jamey's benefit. We do not use Customer CRM Data to create Jamey marketing audiences.
You can ask us at any time to stop non-essential WhatsApp communications by replying in the conversation or emailing privacy@jamey.lu. We may use email or in-product messages instead for essential service, security, billing or legal notices. WhatsApp/Meta independently processes information under its own terms and privacy policy when you use that channel.
6. CRM data, client relationships and marketing campaigns for a business customer
A Jamey business customer may use the Services as its CRM platform to manage its relationship with its own clients, prospects, suppliers or team members. At that customer's instruction, the platform can link a contact to a business, project, transaction, communication or campaign, and can build recipient segments and exclusions for the customer's campaigns.
For this processing:
the business customer decides the purposes and means of processing and is the controller;
Jamey processes the data only to provide the platform and according to the customer's documented instructions, subject to law and the applicable data-processing agreement;
the business customer must ensure it has an appropriate lawful basis, provides any required privacy information, and honours objections, unsubscribe requests, consent withdrawals and suppression lists; and
Jamey does not sell Customer CRM Data or use it for its own direct marketing.
If you receive a campaign from a Jamey business customer, use the unsubscribe or objection method supplied by that business or contact the business directly. We will forward a verified request to the relevant customer where necessary and appropriate.
Order, booking and delivery forms
When a Jamey business customer uses the Services for an order, booking or delivery form, the customer collecting the order is normally the controller of the end customer's information. The form should identify that business and show a link to that business's privacy notice and terms of service before the end customer submits the form.
The business must not silently turn a guest order, delivery or booking into a reusable Jamey Account. If account registration is offered, it must be a distinct, clearly labelled step that explains that the account can be reused across participating Jamey businesses and links to Jamey's central-account Terms and this Notice.
The required manual checkbox is for acceptance of the business's terms where needed to place the order. It may also state that the end customer has read or acknowledged the privacy notice, but it is not Jamey's or the business's consent basis for processing the information needed to receive, prepare, deliver, pay for or support the order. That processing is normally necessary to take steps at the customer's request and perform the order contract.
Any marketing consent must be separately optional, unchecked by default and specific to the relevant marketing channel or purpose. An end customer should be able to submit an order without agreeing to promotional emails, SMS or WhatsApp messages. The business customer must maintain the resulting preference and suppression information and honour withdrawals and objections.
7. Core technology, AI and payment providers
We use the following core providers to operate the Services. The current, complete list—including legal entities, functions, locations and transfer safeguards—is published at https://jamey.lu/legal/sub-processors [publish before launch].
| Provider | Service purpose | Data-location / transfer note |
|---|---|---|
| Vercel | Domain management, web hosting, content delivery and related application infrastructure | Relevant production workloads are configured in European regions. Global delivery, support, telemetry, security and approved sub-processors can still involve international processing. |
| Supabase | Main relational PostgreSQL database and supporting database infrastructure | The primary database is configured in a European region. Region choice controls primary data location but does not alone determine every backup, log, support or external-transfer location. |
| OpenRouter, Inc. and selected AI model providers | Optional AI routing and inference for AI features that you deliberately invoke | OpenRouter is a United States provider. Requests may be routed to different model providers, which can have different locations, retention and training policies. See section 8 for the safeguards and limits. |
| Stripe / Stripe Connect | Jamey subscription payment processing; processing, payouts, fraud prevention and business verification for a Customer's payment flow | Stripe processes data under its own terms and privacy documentation and may act as controller and/or processor depending on the context. International processing can occur as set out in Stripe's documentation and agreements. |
8. AI processing through OpenRouter
AI features are optional. When you deliberately use an AI feature, we send the input necessary to perform the request to OpenRouter and the selected downstream AI model provider. The output is returned to the Services for display or the requested workflow.
OpenRouter and individual model providers may process requests outside the EEA and their policies differ by provider and endpoint. A provider may have its own prompt logging, retention or training policy. We maintain a routing policy and, where the selected product configuration supports it, apply available restrictions relating to data retention and model training. We do not promise that every AI request is zero-retention, EEA-only or excluded from model training unless we have specifically confirmed the relevant model/endpoint configuration in writing.
Do not submit sensitive personal data, credentials, payment-card data, special-category personal data, confidential third-party information or data subject to strict residency requirements through AI features unless Jamey has confirmed that the chosen configuration is suitable. For Customer CRM Data, the Customer remains responsible for the lawful basis, notices and instructions for any AI input.
AI results can be inaccurate or unsuitable. Human review remains necessary before output is relied on, communicated externally or used to make a decision with a material effect on an individual.
9. Payments through Stripe and Stripe Connect
Jamey subscriptions
We use Stripe to process payments for Jamey's B2B subscriptions. Stripe collects payment-method details and processes the payment; we retain the invoicing, payment-status and transaction-reference information necessary to administer the contract, provide support and meet accounting obligations.
Customer B2B2C transactions
A Jamey business customer may use Stripe Connect to accept payment from its own clients and receive payouts. The relevant business must complete the KYB, identity, bank-account, tax and other verification required by Stripe and is responsible for keeping its business and representative information accurate and up to date.
Unless Jamey is expressly identified in writing as merchant of record for a particular payment flow, the relevant business customer is responsible for its transaction with its client, including its product/service, pricing, taxes, legal disclosures, refunds, disputes and chargebacks. Jamey is not a bank, payment institution, e-money institution, custodian or seller in that transaction solely because it provides the platform.
Stripe may process, verify and retain business, representative, beneficial-owner, customer, transaction and payout information for fraud prevention, payment processing, KYB/KYC, anti-money-laundering and other legally required purposes under its own documentation. For Stripe privacy requests about its independent processing, use Stripe's own contact methods; for a business's client data, contact the relevant business customer first.
10. Recipients, service providers and international transfers
We share personal data only where necessary for the purposes described above, including with:
Jamey personnel and authorised contractors who need access to perform their work and are subject to confidentiality obligations;
infrastructure, cloud hosting, database, storage, identity/authentication, security, payment, email, support and messaging providers that process data for us under contract;
professional advisers, insurers, auditors and competent public authorities where required or permitted by law; and
a successor business where Jamey is involved in a merger, financing, acquisition or sale of assets, subject to appropriate safeguards.
Our current list of sub-processors and service providers is available at https://jamey.lu/legal/sub-processors [publish before launch].
We configure the principal hosting and database workloads described in section 7 in European regions. If data are transferred outside the EEA, the United Kingdom or a country recognised as adequate by the European Commission—including due to OpenRouter/selected AI model providers, global infrastructure, support or payment processing—we will use an appropriate safeguard, such as the European Commission's Standard Contractual Clauses, and apply supplementary measures where required.
11. Retention
We keep controller data only for as long as necessary for the purposes in this Notice, including to meet legal, accounting, tax, security and dispute-resolution requirements. The exact periods must reflect the actual system configuration:
| Data | Retention approach |
|---|---|
| Active account data | For the lifetime of the account, then deletion process as in section 13. |
| Billing, subscription and payment records | Kept for the period required by Luxembourg tax and accounting law. [Confirm exact period with counsel/accountant.] Stripe may independently retain payment/verification data as required under its documentation and applicable financial-crime/payment laws. |
| Support communications and routine account logs | [Confirm configured period.] Retained only as long as needed for support, security and dispute handling. |
| Security logs and incident records | [Confirm configured period.] Retained proportionately for security, investigation and compliance. |
| Customer CRM Data | Processed for the relevant business customer for the subscription period and then returned/deleted under the data-processing agreement, subject to legal retention and backup cycles. AI inputs submitted by a Customer are subject additionally to the routing and provider policies described in section 8. |
| Backups | Isolated and overwritten according to the configured backup cycle of [confirm period]; not reused for routine processing after deletion. |
12. Security
We use technical and organisational safeguards appropriate to the risk, including access controls, authentication measures, least-privilege access, encryption where appropriate, logging, backup and recovery processes, confidentiality obligations and security monitoring. No online service is completely secure; you should protect your credentials and notify us promptly if you suspect unauthorised access.
13. Managing or deleting your account
Every Jamey business-service login page provides a Manage your account link. The account-management screen must clearly separate the following actions:
A · Remove me from this business
This action removes your membership and access to the particular business workspace only. It does not delete your Jamey Account, your access to other Jamey services or businesses, or the business's own CRM, audit and compliance records. Where you are the sole administrator, the business may need to appoint a replacement administrator first.
B · Delete my Jamey Account
This action is available from the central Jamey account-management page. After we verify your identity, we immediately deactivate your Jamey Account and sign you out. We permanently delete the account across Jamey services after a 30-day recovery period [confirm], unless a longer retention period is necessary to comply with law, resolve a security/fraud matter, establish/exercise/defend legal claims, or preserve records that a business customer is entitled or required to retain.
Deleting a Jamey Account does not automatically delete an organisation or the Customer CRM Data belonging to a business customer. The business controls its own data retention. A former user's identity may be removed or pseudonymised while necessary business records remain.
C · Delete an organisation
Deleting an organisation is a separate action available only to a verified organisation administrator. It includes a data-export opportunity and an explicit confirmation. It is not triggered merely because an individual deletes their Jamey Account.
You may also contact privacy@jamey.lu to request deletion or exercise other rights. We may ask for information to verify your identity and authority.
14. Your rights
Subject to the conditions and limits in applicable law, you may have the right to request access to your personal data; correction of inaccurate data; deletion; restriction of processing; portability; and objection to processing based on legitimate interests.
You have the right to object at any time to the use of your personal data for direct marketing, including profiling related to that direct marketing. Once you object, we will no longer use your data for that purpose.
Where we rely on consent, you may withdraw it at any time without affecting the lawfulness of processing before withdrawal. To exercise your rights regarding data for which Jamey is controller, contact privacy@jamey.lu. You also have the right to lodge a complaint with the Luxembourg National Commission for Data Protection (CNPD) or another competent supervisory authority.
Where the conditions for the GDPR right to data portability are met, you may request the personal data you provided to Jamey as controller in a structured, commonly used and machine-readable format. For records held by a separate Jamey business—such as that business's orders, delivery data or CRM history—contact that business directly.
For CRM data controlled by a Jamey business customer, contact that business directly. We will assist it where we are required to do so.
15. Children
The Services are intended for professional and business users, not for children. We do not knowingly collect personal data from children through the Services. If you believe a child has provided personal data to us, contact privacy@jamey.lu.
16. Cookies and similar technologies
We use strictly necessary technologies required for authentication, security and basic Service operation. Non-essential analytics, preference or marketing technologies are not enabled without consent. Details are in our separate Cookie Notice at https://jamey.lu/cookies.
The providers that process personal data on our behalf are listed, with their roles, locations and transfer safeguards, at https://jamey.lu/legal/sub-processors.
17. Changes to this Notice
We may update this Notice when our processing, Services or legal requirements change. For material changes, we will give appropriate advance notice through the Services, by email or another durable method. The latest version will be published at Jamey.lu with its effective date.
