Privacy Policy
Last updated: October 1, 2026
This Privacy Policy explains how Joryio ("we", "us", or "our") collects, uses, discloses and protects personal data when you visit our marketing website at joryio.com, contact us, or use the Joryio customer engagement platform (the "Service"). You can contact us about privacy at [email protected].
1. Our role and the scope of this policy
Website visitors and business contacts. We act as a controller, meaning we decide why and how to use personal data, when we operate our marketing website, respond to inquiries, manage customer and partner relationships, administer accounts, and meet our own legal obligations. Information about people who use or administer business accounts is called "Account Data" in this policy.
Our customers' end users. When a customer submits personal data to the Service about its own users, subscribers or customers ("Customer Data"), we act as a processor: we handle that data on the customer's behalf, under its documented instructions and our Data Processing Agreement. If the customer acts for another organization, we may act as a subprocessor. Customer Data can include profiles, contact details, behavioral events, message content, delivery and engagement records, and consent preferences. We do not use Customer Data to advertise Joryio or its services.
The relevant customer's privacy notice explains why it uses your data and its legal basis for doing so. If your request concerns a message sent by one of our customers or data it holds about you, contact that customer. We assist customers with their obligations and direct requests we receive to the relevant customer where appropriate.
Marketing website and SaaS app. The marketing-site analytics and advertising tools described in section 4 are separate from the SaaS app. Google Analytics, Google Ads, Meta Pixel and LinkedIn Insight Tag are not installed on our SaaS app. The app still processes data needed for authentication, security, account administration and service operation. Analytics and messaging that customers configure for their own websites or apps are governed by their instructions and notices.
This policy does not govern independently operated websites or services linked from our website, or providers you connect under your own agreements.
2. Personal data we collect and its sources
We collect data you provide directly, data generated when you interact with our website or Service, and data provided by your organization or providers involved in delivering the services you use.
| Category | Examples and sources |
|---|---|
| Contact and business information | Your name, work email, company, current platform, reason for contacting us, and the message you submit through a demo, partnership or contact request. We also receive information you send by email or provide in business correspondence. |
| Partner referral information | With your advertising and partner-referral consent, the partner link you used, the first and latest referral times and an opaque browser reference. During same-site navigation, we carry the referral code in internal URLs. If you submit an enquiry during that visit, we may record the link with the enquiry you asked us to handle, without setting a referral cookie or retaining a browser reference. We keep the original eligible referral with that contact and track its follow-up status, including whether it becomes a customer. |
| Account and authentication information | Name, email, workspace membership, role, permissions and authentication records. Depending on the sign-in method, this can include password hashes, passkey public keys, MFA enrollment or information supplied by your identity provider or account administrator. |
| Billing and transaction information | Company and billing details, subscription plan, invoices, transaction references and payment status. Payment card details are handled by our payment provider; we do not store full payment card numbers. |
| Technical and usage information | IP address, browser and device information, request timestamps, pages viewed, referring pages, interactions, sign-in events, diagnostic information and security logs. Sources include your browser or device, our services, and the hosting, analytics or security providers involved. |
| Preferences and communication records | Cookie and marketing choices, consent records, support requests, correspondence and our responses. |
Providing information through our marketing forms is voluntary. Name and email are required to submit a request; the contact form also requires a reason and message. Without the information needed to respond, we may be unable to handle your request. Account, authentication and billing information may be necessary to provide the Service or meet legal requirements. Optional fields are not required to use the marketing website.
Please do not include passwords, full payment card details, health information or other sensitive personal information in marketing forms or ordinary support messages.
3. Why we use personal data
Where the GDPR or UK GDPR applies to our processing as a controller, we need a legal basis to use personal data. Depending on the purpose, this may be your consent, a contract, a legal obligation, or a legitimate business interest considered alongside your rights. The following table explains which bases apply:
| Purpose | Data used | Legal basis |
|---|---|---|
| Respond to inquiries, arrange demos and discuss partnerships | Contact, business and communication information | Our legitimate interest in responding to requests and developing business relationships; steps requested before entering a contract where you would be a party to it. |
| Provide the Service and administer accounts, billing and support | Account, authentication, billing and communication information | Performance of a contract with you, or our legitimate interest in providing the Service to the organization you represent; legal obligations for required financial records. |
| Secure services, investigate abuse and resolve technical problems | Account, technical, usage and diagnostic information | Our legitimate interest in protecting people, accounts and services; legal obligations where applicable. |
| Understand and improve website or service performance | Usage, technical and feedback information | Consent for non-essential tracking where required; otherwise our legitimate interest in maintaining and improving our services, subject to your rights. |
| Measure marketing and send permitted business communications | Contact information, marketing-site activity, referral information and preferences | Consent where required; otherwise our legitimate interest in communicating relevant business information and understanding our marketing, subject to applicable law and your choices. |
| Meet legal obligations, maintain records and establish or defend claims | Information relevant to the obligation, record or claim | Compliance with law and our legitimate interest in protecting legal rights. |
Where we rely on legitimate interests, we consider the effect on your rights and freedoms. A legitimate-interest basis does not replace consent where consent is required for cookies, tracking or marketing.
4. Marketing-site cookies, analytics and communications
On joryio.com, we use necessary storage to remember privacy choices and support website operation. Where enabled, marketing-site tools may also include first-party Joryio analytics and Google Analytics, Google Ads, Meta Pixel and LinkedIn Insight Tag. Google Tag Manager manages the Google, Meta and LinkedIn tags. These tools can process online identifiers, device and browser information, page visits, referral information and events such as a submitted demo request to help us understand website use and measure marketing.
These marketing tags do not run on the SaaS app. Customer-configured integrations in the Service are separate from our own marketing-site tools.
Our cookie controls provide separate choices for analytics and advertising. Where consent is required, you can accept or reject optional categories and change your choices through Cookie settings in the website footer. Necessary technical requests, such as delivering a page or recording a security event, may still occur when optional categories are rejected. See our Cookie Policy for further information about cookies and similar technologies.
You can object to direct marketing at any time by using the unsubscribe option in a marketing message or contacting [email protected]. We may keep a limited record of your opt-out so that we do not contact you again for that marketing. Essential account, security and transactional messages may still be necessary to provide the Service.
5. Who receives personal data
We disclose personal data for the purposes described in this policy to the following categories of recipients:
- Website and business operations providers: hosting, storage, content delivery, security, customer-relationship management, support, email delivery and internal notification providers. Our marketing-site hosting provider operates in the United States and uses a global content delivery network. Our CRM and its hosting and database providers process contact and demo submissions in the United States. Our US-based email delivery provider sends the submitted details to our team. These providers receive the information needed for their functions.
- Partner attribution: our separate partner system stores enquiry and referral records in the United States. Joryio administrators can review contact details and manage follow-up. Partners can see aggregate counts of their referrals and customer outcomes; the portal does not give them enquirers' names, email addresses, messages or internal notes.
- Payment and professional services providers: payment processors, accountants, auditors, insurers and legal advisers, where needed for billing, compliance or professional advice.
- Marketing-site analytics and advertising providers: providers described in section 4 may receive marketing-site identifiers and activity information, subject to applicable law and privacy choices. This does not give them access to Customer Data stored in the SaaS app.
- Your organization and its authorized users: account administrators may access business-account information and activity according to their permissions. Contact your organization about its account-management policies.
- Service subprocessors and customer-directed recipients: Customer Data is processed under the DPA and relevant customer instructions. Our Subprocessor list describes providers used for the Service. Systems you connect, such as your online store, data warehouse or webhook endpoint, receive or supply data according to your instructions. Independently engaged providers operate under your arrangements to the extent they are not processing on Joryio's behalf.
- App operations providers: providers deliver system emails, process payments, protect sign-in and deliver fonts. For example, the web app, admin console and documentation request fonts from Google, which receives the visitor's IP address and request information. These operational requests are separate from marketing analytics and advertising tags.
- Authorities and parties to legal proceedings: where disclosure is required by law or necessary and lawful to investigate abuse, protect safety, or establish, exercise or defend legal claims.
- Parties to a business transaction: a potential or actual purchaser, successor or adviser in a merger, acquisition, financing or sale of assets, subject to appropriate confidentiality and data-protection safeguards.
Providers acting on our behalf are subject to contractual restrictions appropriate to their role. Some recipients, such as payment providers, professional advisers or advertising platforms, may also have independent obligations or act as controllers for specified activities under their own notices.
We do not sell personal data for money. Some privacy laws also treat disclosure to advertising providers as a "sale" or "sharing", even without payment. This can include using information to target ads based on activity across different businesses' websites or apps. Whether a disclosure falls within those definitions depends on how the data is used and the relevant agreements. Your applicable opt-out rights are described in section 8.
6. International processing and transfers
The production Service's primary hosting and core databases are currently in Frankfurt, Germany. Cloudflare's R2 object storage uses its Eastern Europe hub, and edge services process traffic globally. AI providers, system email and some delivery or control-plane activities involve the United States or other countries, as described in our Subprocessor list. Primary EU hosting does not mean every processing activity takes place in the EU.
Marketing-site hosting, CRM storage and enquiry-notification delivery involve providers in the United States. Our first-party Joryio website analytics uses the Frankfurt-hosted Service. Third-party analytics and advertising can involve global processing, subject to applicable law and your privacy choices.
Where applicable law requires safeguards for transfers, we use an applicable adequacy decision or appropriate contractual safeguards, including the European Commission's Standard Contractual Clauses and the relevant UK transfer instrument where required. Reliance on the EU-U.S. Data Privacy Framework, or its applicable UK extension, is limited to eligible recipients and processing covered by a valid certification; this is not a claim that Joryio itself is certified.
You can request information about relevant recipients, transfer safeguards, or a copy of applicable safeguards by contacting [email protected]. Information may be redacted where necessary to protect confidential information or others' rights. Customer Data transfers are also governed by the DPA and applicable customer agreement.
7. Retention and deletion
We retain personal data only for as long as reasonably necessary for the purposes described in this policy. Retention varies by record type and purpose, taking into account our relationship with you, the nature and sensitivity of the data, security needs, applicable limitation periods and legal recordkeeping requirements. We use the following criteria:
- Contact and demo requests: for as long as reasonably necessary to respond to inquiries and manage ongoing business relationships or active sales discussions. We consider the nature of the inquiry, our last meaningful interaction, whether discussions remain active, and applicable legal requirements. We periodically review inactive records and delete or anonymize information that is no longer needed.
- Account Data: while needed to operate and support the account. After closure, we retain relevant records only for as long as needed to resolve outstanding billing or support matters, meet tax and accounting requirements, investigate security incidents, or establish, exercise or defend legal claims within applicable limitation periods. Different account records may have different retention periods.
- Audit and security logs: according to the type of event, the period needed to detect and investigate incidents or misuse, and applicable service settings and contractual requirements. Logs relevant to an ongoing investigation or legal preservation requirement may be retained for the duration needed for that purpose.
- Customer Data: according to the customer's configuration and the return and deletion provisions of the DPA and applicable agreement. In the Service's analytics store, API request logs are currently retained for 90 days by default. For organizations where rendered message copies are stored, their default retention is also 90 days. Analytics events are retained for 730 days by default. These settings are configurable per organization. They do not extend retention beyond applicable deletion instructions, legal requirements or the DPA's post-termination deletion schedule.
- Website analytics and advertising data: according to the purpose, relevant tool settings and identifier lifetimes described in the Cookie Policy. Identifier expiry and deletion of records already held by a provider are separate matters.
- Consent, suppression and rights-request records: for as long as reasonably necessary to respect your choices, demonstrate how a request was handled, and meet applicable legal obligations.
We periodically review retention needs. When retention is no longer necessary, we delete or anonymize the data. Backup copies may remain until their scheduled expiry; they are protected and used for recovery, security or legal purposes rather than ordinary business use. Legal preservation requirements may delay deletion of specifically relevant records. These criteria do not override applicable privacy rights, legal deadlines, or retention and deletion commitments in the DPA or your agreement with us.
8. Your privacy rights and choices
Depending on your location, the applicable law and our role, you may have rights to access your personal data, receive a copy, correct inaccuracies, request deletion, restrict processing, obtain portable data, or object to processing based on legitimate interests. These rights are subject to the conditions and exceptions in applicable law.
You can object to direct marketing at any time. Where we rely on consent, you can withdraw it at any time; withdrawal does not affect the lawfulness of earlier processing.
To make a request about marketing-site data or Account Data, email [email protected]. You may also contact us through our contact page. We may ask for information reasonably needed to verify your identity or an authorized agent's authority, without collecting more information than necessary. We will explain any lawful refusal or limitation. Where an appeal right applies, you can request a review through the same contact channels. We do not discriminate against you for exercising applicable privacy rights.
EEA and UK. We respond without undue delay and generally within one month, subject to the timing rules and permitted extensions in applicable law. Where an extension is permitted because of complexity or the number of requests, we explain it within the required period. You may complain to your local data-protection authority; UK residents can contact the Information Commissioner's Office. You do not need to contact us first to exercise that right.
California and other U.S. states. Where the relevant law applies, rights may include knowing the categories and specific pieces of personal information collected, their sources, purposes and recipient categories; access, correction and deletion; opting out of sale, sharing or targeted advertising; and limiting certain uses of sensitive personal information. Authentication credentials may constitute sensitive personal information; we use them for account access and security. Sections 2, 3 and 5 describe our data categories, purposes, sources and recipients. Marketing-site advertising disclosures are addressed separately from SaaS Customer Data.
You can reject the advertising category through Cookie settings and contact us to exercise applicable sale, sharing or targeted-advertising opt-out rights. Cookie choices apply to the browser or device on which you make them. California access, correction and deletion requests generally receive a response within 45 days, with a further 45 days where permitted and with notice; other requests follow their applicable deadlines.
For Customer Data controlled by one of our customers, direct your request to that customer as explained in section 1.
9. Customer-directed AI and personalization
The Service can process Customer Data to create segments, calculate engagement or predictive scores, personalize messages, and determine delivery timing or channels according to customer instructions. Where a customer enables AI features, inputs can include workspace vocabulary, campaign content, aggregated statistics and profile attributes used for personalization. Joryio-managed AI uses Anthropic, OpenAI or Google Gemini and can process inputs outside the EU. Supported customer-connected AI accounts use the customer's provider arrangements; see the Subprocessor list for providers, processing locations and retention considerations. Customer Personal Data remains subject to the DPA throughout Joryio's processing.
Assistant chat transcripts are stored in Joryio's database in Frankfurt. We include relevant earlier chat turns in individual requests to the selected AI provider, rather than using provider-hosted conversation or file-storage features. Anthropic may briefly cache assistant instructions and workspace configuration. Providers may also retain request data under their applicable abuse-monitoring, safety and legal rules, as explained in the Subprocessor list; sending an individual request does not mean that no provider retention occurs.
We do not use Customer Data to train generalized machine-learning models across customers. Our customer-specific prediction models, brand voice and personalization stay within the relevant organization or workspace. Customers are responsible for explaining their own profiling and automated decisions to their end users and establishing any required legal basis. We assist them as provided in the DPA.
10. Security
We apply technical and organizational measures appropriate to the risks, including encryption, access controls, separation of customer data and logging. Available account-security features include multi-factor authentication, passkeys and IP restrictions; their application depends on the relevant service and configuration. See our security overview.
No system or method of transmission is completely secure. If you believe personal data or an account has been compromised, contact us promptly. We provide incident notifications where required by applicable law and our contractual obligations.
11. Children
Our marketing website and business accounts are not directed to children under 16. We do not knowingly collect personal data directly from children under 16 for those purposes. If you believe a child has provided such information, contact us so we can investigate and take appropriate action. Customers are responsible for lawful collection and use of their own end-user data, including any applicable age restrictions and parental-consent requirements.
12. Updates and contact
We will post changes to this policy here and update the date above. For material changes, we provide additional notice where appropriate to the nature and impact of the change or required by applicable law, for example through email or an in-product notice. We obtain consent where required and provide information about a new processing purpose before using personal data for that purpose. This policy does not limit rights provided by applicable law.
Joryio - Privacy inquiries
Email: [email protected]
Alternative contact: [email protected] or our contact page.