PRIVACY POLICY
プライバシーポリシー
個人情報およびサービスデータの収集、利用、保護、取り扱いについては、INNORIXプライバシーポリシーをご確認ください。
Effective Date: October 21, 2026
INNORIX processes personal information and service data necessary for the use of its website and the INNORIX Platform.
This Privacy Policy explains what information INNORIX processes and how it is used when you use the INNORIX website, Account, Cloud Service, Software, API, and related services.
Where INNORIX processes Personal Data as a Processor on behalf of a Customer, the Data Processing Addendum (DPA) may apply together with this Privacy Policy.
Information We Collect#
The information INNORIX processes depends on how the Services are used.
Website Information#
When you visit the INNORIX website, the following information may be processed.
IP address
Browser and device information
Pages visited
Referrer information
Cookie and preference information
Website interaction information
This information is used for website operation, security, performance analysis, and improving the user experience.
More information about Cookies is available in the Cookie Policy.
Account Information#
When you create an INNORIX Account or join an organization, the following information may be processed.
Name
Business email address
Organization
User identifier
Role and permissions
Account settings
Authentication information
If you sign in through Google or another supported Identity Provider, that Provider may provide INNORIX with information required for authentication.
INNORIX uses this information for Account creation, authentication, permission management, and customer support.
Device & Connection Information#
When a Server, PC, VM, Kubernetes Node, Object Storage, or other Endpoint is connected to INNORIX, Device information required to operate the Service may be processed.
For example:
Device ID
Device name
Operating system
Software version
IP address
Connection status
Device type
Last connection information
Workspace or organization association
This information is used to identify Devices, maintain connection status, execute transfer operations, and monitor operational status.
Transfer & Operational Metadata#
When file transfers and automation are executed, Metadata required for Service operation may be generated.
For example:
Source and destination identifiers
Run ID
Transfer ID
Flow information
Transfer status
Start and completion time
File transfer result
File size
Error and retry information
Audit information
Where required by product functionality, this may include information such as File names or paths.
INNORIX uses this information for transfer execution, Monitoring, Audit, troubleshooting, and Service operation.
Customer Files#
Direct transfer keeps file content on the transfer path#
When using INNORIX's Direct Transfer configuration, files move directly between the connected Source and Destination.
In this architecture, INNORIX Cloud is not used as intermediate storage for file transfers.
Instead, the INNORIX Control Plane manages operational information such as the following.
Connected Devices
Transfer instructions
Policies
Transfer status
Results
Operational metadata
The actual data path may vary depending on the customer's Deployment, Routing, and additional service configuration.
Object Storage Connections#
When Object Storage is connected, INNORIX may process authentication and connection information required to operate that Connection.
INNORIX does not store Raw Credentials in Metering or Billing records.
Credentials or security References required for Service operation may be used, while usage records contain only the necessary identifying information.
The customer's Cloud Account, Storage permissions, and Bucket permissions are managed by the customer and the applicable Cloud or Storage Provider.
API Information#
When the API is used, the following information may be processed.
API credential identifier
Organization and Workspace information
Request information
API operation
Request time
Response status
Security and rate-limit information
API request records may be used for authentication, security, troubleshooting, Usage management, and Audit.
Usage & Metering Information#
INNORIX processes Usage information to operate Subscriptions and measure usage.
For example:
Active Devices
Additional Device usage
Successfully delivered payload volume
API usage
Run and Transfer counts
Log usage
Applicable Plan and entitlement information
The Metering system primarily processes information required for Service operation and usage calculation.
File contents, Passwords, Raw Access Tokens, and Raw Storage Credentials are not stored as usage data.
Billing Information#
When using a paid Subscription, the following Billing information may be processed.
Organization and billing account
Legal or business name
Billing address
Country
Tax information
Subscription
Currency
Invoice information
Purchase Order information
Payment status
Credits and adjustments
When Card Payment is used, Payment Card processing may be handled through an external Payment Provider.
INNORIX may process Payment Provider References and Transaction information required for Service operation.
Support Information#
When a customer contacts INNORIX or requests technical support, the following information may be processed.
Contact information
Support request
Communications
Relevant Device or Transfer identifiers
Error information
Logs provided by the customer
Other diagnostic information provided for troubleshooting
Customers should avoid including personal or confidential information in Support materials when it is not necessary for troubleshooting.
How We Use Information#
INNORIX uses collected information for the following purposes.
Provide the Service#
Create and operate Accounts
Connect Devices
Execute file transfers
Run automation
Provide API access
Display operational status
Maintain transfer history
Secure the Service#
Authenticate users and systems
Protect Accounts and Devices
Detect unauthorized access
Apply security controls
Investigate suspicious activity
Maintain audit records
Operate and Improve the Service#
Monitor performance
Diagnose errors
Maintain reliability
Analyze service usage
Improve product operation
Manage Subscriptions and Billing#
Measure usage
Apply Plan entitlements
Generate invoices
Process payments
Manage credits and adjustments
Prevent billing errors and abuse
Provide Support#
Respond to inquiries
Investigate technical problems
Restore service operation
Communicate with administrators
Meet Legal Obligations#
INNORIX may process or retain information where necessary to comply with applicable:
laws
tax requirements
accounting requirements
regulatory obligations
valid legal requests
Legal Basis for Processing#
Where applicable law requires a legal basis for processing Personal Data, INNORIX may rely on one or more of the following:
performance of a contract
steps requested before entering into a contract
legitimate interests in operating and securing the Services
compliance with legal obligations
consent where required
Where INNORIX processes Customer Personal Data solely on behalf of a Customer, the Customer determines the legal basis for that processing and INNORIX acts according to the applicable DPA.
Customer and INNORIX Roles#
INNORIX may process Personal Data in different roles depending on the context.
INNORIX as Controller#
INNORIX generally determines the purposes of processing for information such as:
INNORIX Account administration
Website operations
Billing administration
Security of INNORIX services
Communications with INNORIX customers
INNORIX as Processor#
Where Customer Personal Data is processed through the Services according to a Customer's instructions, INNORIX may act as a Processor on behalf of that Customer.
The applicable Processing terms are described in the DPA.
How We Share Information#
INNORIX does not disclose Personal Data except as necessary for legitimate business and service purposes, including the circumstances described below.
Service Providers#
INNORIX may use external providers to support functions such as:
Cloud infrastructure
Service operations
Authentication
Communications
Payment processing
Customer support
Monitoring
Providers that process Customer Personal Data on behalf of INNORIX are managed according to applicable contractual and data protection requirements.
The relevant providers can be found in the Subprocessor List.
AI Assistant providers (such as Anthropic and OpenAI) that receive tool results when you use an AI Assistant connector are not INNORIX service providers; they process the information under their own terms, as described in AI Assistant Connectors.
Business Transactions#
Information may be transferred as part of:
merger
acquisition
corporate restructuring
financing
sale of business assets
where permitted by applicable law and subject to appropriate confidentiality and data protection requirements.
Legal Requirements#
INNORIX may disclose information when reasonably necessary to:
comply with applicable law
respond to valid legal process
protect INNORIX, customers or others
investigate fraud or security incidents
enforce applicable agreements
Where legally permitted, INNORIX may notify the affected customer of a government request involving Customer Personal Data.
International Data Processing#
INNORIX operates across multiple regions and may use service providers located in different countries.
Personal Data may therefore be processed outside the country in which it was originally collected.
Where applicable law requires safeguards for international data transfers, INNORIX uses legally recognized transfer mechanisms as applicable to the relevant processing.
Additional terms governing Customer Personal Data are described in the DPA.
When you use an AI Assistant connector, tool results are transferred to the provider of the AI Assistant you connect (Anthropic or OpenAI, United States), as described in AI Assistant Connectors.
The MCP server that provides the connector (mcp.innorix.com) is hosted by OVHcloud in Canada. The information the MCP server keeps, described in AI Assistant Connectors, is stored and processed there:
| Recipient | OVH Hosting Inc. (Hébergement OVH Inc., OVHcloud), 800-1801 McGill College Avenue, Montréal, Quebec H3A 2N4, Canada. Privacy contact: Privacy Officer, rprp@ovh.ca |
| Country | Canada |
| Information | MCP server service usage logs, web server logs and error logs, workspace selections, sign-out records and demo data |
| When and how | Each time your AI Assistant calls the connector, sent to the hosting servers over an encrypted connection (HTTPS) |
| Purpose | Hosting and operating the MCP server |
| Retention | As in "Retention by INNORIX" in "AI Assistant Connectors" (logs up to 30 days, workspace selection 90 days after last use, demo data 7 days after last use) |
| How to refuse | Do not connect an AI Assistant. You can still use INNORIX Platform from the web console. |
Data Location#
The location in which information is processed may depend on:
Service
Deployment
Cloud region
Customer configuration
Subprocessor
support requirements
On-Premises, Hybrid, Sovereign Cloud and Air-Gapped deployments may provide different data-processing architectures.
A specific data residency commitment applies only where it is part of the selected Service or applicable customer agreement.
Data Retention#
INNORIX retains information for the period reasonably necessary for the purpose for which it is processed.
Different categories of information have different retention periods.
Account Information#
Account information is retained while necessary to operate the Customer Account and applicable Services.
Operational Logs#
Searchable operational log retention depends on the applicable Plan and configuration.
Billing and Contract Records#
Invoice, payment, tax and contract records may be retained after service termination where necessary for accounting, tax, legal or dispute-resolution purposes.
Support Information#
Support communications and diagnostic information may be retained for support, service improvement, security and audit purposes.
Account Termination & Data Deletion#
When a paid Subscription ends, INNORIX may provide a limited Read-only Grace Period under the applicable Terms.
During this period, available information such as:
Logs
Receipts
Configuration
Operational records
may remain accessible for review or export.
After the applicable Grace Period, INNORIX begins deletion of active service data that is no longer required.
Information that must be retained for legal, tax, accounting, security or dispute purposes may be retained for the applicable period.
Backups#
Information that has been deleted from active systems may remain temporarily in Backup copies until removed through normal Backup Rotation.
Backup data is maintained for recovery and continuity purposes and is protected from ordinary active use.
Security#
INNORIX uses technical and organizational safeguards appropriate to the Services to protect information against unauthorized access, loss, alteration or disclosure.
Security controls include protections relating to areas such as:
Access control
Authentication
Data transmission
Device security
Audit
Monitoring
Operational security
Backup and recovery
More information is available on the Security page.
Your Choices and Rights#
Depending on applicable law and the context in which INNORIX processes Personal Data, individuals may have rights to:
access Personal Data
correct inaccurate information
request deletion
restrict certain processing
object to certain processing
receive portable data
withdraw consent where processing is based on consent
Some rights may be subject to legal limitations or exceptions.
Customer-Managed Personal Data#
Where Personal Data is processed by INNORIX on behalf of a Customer, individuals should generally direct privacy requests to the organization that controls that data.
INNORIX assists Customers with applicable requests according to the DPA and available Service functionality.
Account Information#
Users can manage certain Account and Organization information directly through available product settings.
Where information cannot be managed through the product, privacy-related requests may be submitted through INNORIX's website contact channels.
INNORIX may need to verify identity or authority before completing a request.
Cookies#
INNORIX uses Cookies and similar technologies where necessary to operate its website and, where applicable, understand website usage or remember preferences.
Users can manage non-essential Cookies through Cookie Preferences.
Marketing Communications#
Where INNORIX sends optional marketing communications, recipients can use the unsubscribe option provided in the communication.
Unsubscribing from marketing does not prevent INNORIX from sending operational or contractual communications necessary for an Account or Service.
Third-Party Services#
Customers may connect INNORIX with third-party services such as:
Cloud providers
Object storage
Identity providers
Monitoring services
SIEM platforms
Collaboration tools
Personal Data processed directly by those providers is also subject to their own privacy policies and contractual terms.
Customers are responsible for selecting and configuring third-party services they connect to INNORIX.
AI Assistant Connectors (INNORIX Platform MCP Server)#
INNORIX provides a Model Context Protocol (MCP) server at https://mcp.innorix.com that lets you use INNORIX Platform from AI assistants such as Claude and ChatGPT ("AI Assistant"). With it, you can ask your AI Assistant to see your devices, browse folders, start or schedule transfers, and check transfer status. This section explains what we process when you use the connector. The rest of this Privacy Policy also applies.
Connecting your account
When you connect an AI Assistant, you sign in to INNORIX on innorix.com, approve the permissions (scopes) the connector may use, and may choose a workspace. We keep a connection record with:
- your user ID, email address and name;
- the name and client ID of the AI Assistant that connected;
- the permissions you approved and the workspace you chose;
- when the connection was created and last used.
To keep you connected, we issue a short-lived access token and a refresh token. We store refresh tokens only in hashed form. The MCP server does not store access tokens; it checks each token and uses it to call the INNORIX Platform API on your behalf.
The sign-in and consent pages on innorix.com are part of our website. The request log they write (IP address, time, requested page, browser information) is kept for 90 days; otherwise the website and account sections of this Privacy Policy apply.
What the connector processes
When your AI Assistant calls a connector tool, it sends the tool name and the values needed for that request, such as a device name, a folder path or a transfer schedule. The MCP server forwards these to the INNORIX Platform API, which performs the action, and returns the result to your AI Assistant. Results can include device names, folder paths, file names and sizes, transfer status and history, workspace information, and activity records that show what happened in the workspace.
- The connector does not look up your chat history, your AI Assistant's memory, or files you upload to your AI Assistant. It processes the information your AI Assistant includes in a tool call to carry out the request. That information can come from your conversation or from files you uploaded to your AI Assistant.
- Other workspace members' names, email addresses and IP addresses are left out of these fields: the user and IP address of activity records, the person in file activity, and the owner of devices and workspaces. In activity records your own actions are labeled as yours and other members appear as "member 1", "member 2" and so on, and email and IP addresses written inside activity details are hidden. A device's IP address is shown only for your own devices, and your own activity records include your IP address.
- File names, folder paths and device names can still contain personal information, including information about people other than you, such as colleagues or customers, and are sent to your AI Assistant as part of the tool results. If you use INNORIX Platform on behalf of an organization, make sure your organization allows this information to be shared with the AI Assistant you use.
- File contents do not pass through the MCP server. Files move between your devices as described in "Customer Files".
- The MCP server does not store the values sent with a request or the results it returns. Actions you take through the connector, such as a transfer you start, are recorded in INNORIX Platform in the same way as actions you take in the web console. They are covered by the sections on transfer and operational metadata and on API information.
Information the MCP server keeps
- Service usage logs: for each request, the time, a pseudonymous caller identifier derived from a one-way hash of your user ID, the authentication type, the operation or tool name, the response status and the response time. The pseudonymous identifier can be linked back to your account by INNORIX, so we protect it as personal information.
- Web server logs: for each request, the IP address it came from, the time, the request line (method and path), the response status and size, the referrer and the user agent (the name and version of the client software). When you use Claude or ChatGPT, requests usually come from your AI Assistant provider's servers, so the IP address is usually theirs rather than yours.
- Error logs: technical details of failed requests, used to troubleshoot problems.
- Service usage logs and web server logs do not record the values sent with a tool call, the results or access tokens. Error logs are configured not to record them.
- Workspace selection: if you switch workspaces from your AI Assistant, the workspace you chose, stored under the pseudonymous identifier.
- Sign-out records: when you sign out through the connector, the identifier of that connection, so its remaining access token is refused.
- Rate-limit counters: short-lived request counts kept only in memory to protect the service.
How we use this information
We use it to authenticate you, to carry out the requests you make through your AI Assistant, to keep your workspace choice, to protect the service against abuse, and to troubleshoot problems. We do not sell this information or use it for advertising. INNORIX does not develop or train AI models, and does not use any information processed through the connector to train AI models.
Your AI Assistant provider
The results of the tools your AI Assistant calls are sent to the AI Assistant you connected, which is operated by its own provider (for example, Anthropic for Claude or OpenAI for ChatGPT). That provider processes them under its own terms and privacy policy. INNORIX has no technical means to change or delete what the provider keeps, but you can still send INNORIX requests and complaints about the transfer (see "Contact"). Whether the provider keeps this information or uses it to improve its models depends on its terms, your plan and your settings. Other sharing follows "How We Share Information", and the service providers we use to host the connector are listed on the Subprocessors page.
Transfers outside your country
AI Assistant providers may process tool results outside your country. Tool results are transferred to the provider of the AI Assistant you connect. You can connect the connector only from the AI Assistants below:
| AI Assistant | Recipient | Country | Privacy contact |
|---|---|---|---|
| Claude, and Claude Code signed in with an Anthropic account | Anthropic PBC, 548 Market St, PMB 90375, San Francisco, CA 94104 | United States | privacy@anthropic.com |
| ChatGPT | OpenAI OpCo, L.L.C., 1455 Third Street, San Francisco, CA | United States | privacy.openai.com, dsar@openai.com |
Claude Code is supported only when it is used with an Anthropic account (Pro, Max, Team, Enterprise or a Console API key); Claude Code used through Amazon Bedrock, Google Cloud or Microsoft Foundry is not supported. For users in the EEA, the UK and Switzerland, these providers name a different entity in their privacy policies (for example, Anthropic Ireland, Limited for Claude).
| Information | The tool results described above (device names, folder paths, file names and sizes, transfer status and history, workspace information, activity records, and IP addresses of your own devices and your own activity). File names, folder paths and device names may contain personal information. |
| When and how | Each time your AI Assistant calls a tool, sent over an encrypted connection (HTTPS) |
| Purpose | To let your AI Assistant answer your request. The recipient may also use the information for the other purposes in its privacy policy, such as security, preventing abuse, meeting legal obligations and, depending on your settings and plan, improving its services and models. |
| Retention by the recipient | See "Retention by AI Assistant providers" below. |
| Legal basis | Your consent, which you give on the consent screen when you connect the connector, separately from the permissions. For users in the Republic of Korea, these are two consents with their own checkboxes: consent to provision to a third party (Article 17(1)(1) of the Personal Information Protection Act) and a separate consent to transfer outside Korea (Article 28-8(1)(1)). |
| Safeguards | Sent only over an encrypted connection (HTTPS) and only within the permissions you grant; other workspace members' names, email addresses and IP addresses are left out of the user and owner fields described above. Complaints can go to INNORIX (see "Contact") or to the recipient's privacy contact listed above. Ending the connection stops the transfer at any time. |
| How to refuse | Leave the consent boxes unchecked and press Deny on the consent screen, or end the connection later (see "Your choices"). You can then use INNORIX Platform from the web console, but not from your AI Assistant. |
Retention by AI Assistant providers
Tool results are kept with the conversation or coding session in the AI Assistant you use, as its provider describes (as of October 20, 2026):
| Provider and plan | Retention |
|---|---|
| Anthropic: Claude (app) Free, Pro and Max | Kept in your chat history until you delete the conversation, then deleted from back-end systems within 30 days. If you allow your chats to be used to improve Claude, de-identified data may be kept for up to 5 years. Conversations flagged for violating the usage policy: inputs and outputs up to 2 years, safety classification scores up to 7 years. Longer where required by law. (source) |
| Anthropic: Claude Team and Enterprise | Kept in the product until you delete the chat; deleted chats are removed from back-end systems within 30 days. On Enterprise, your administrator can set a different retention period. (source) |
| Anthropic: Claude Code with a personal account (Free, Pro, Max) | 30 days, or 5 years if you allow your data to be used for model improvement. (source) |
| Anthropic: Claude Code with Team, Enterprise or a Console API key | 30 days by default. Exceptions: features with longer retention you control, separate agreements with Anthropic (such as zero data retention), usage policy enforcement (flagged inputs and outputs up to 2 years) and legal requirements. (source, source) |
| OpenAI: ChatGPT Free, Plus and Pro | Kept in your account until you delete the conversation, then removed from OpenAI's systems within 30 days unless it was already de-identified or must be kept longer for security or legal reasons. Temporary chats: up to 30 days. (source) |
| OpenAI: ChatGPT Business, Enterprise and Edu | Controlled by your workspace administrator; deleted conversations are removed within 30 days unless OpenAI is legally required to keep them. (source) |
Retention by INNORIX
| Information | Retention |
|---|---|
| Connection record and hashed refresh token | Until the connection ends, or 90 days after it was last used |
| Sign-out record | Until the signed-out access token expires |
| Workspace selection | 90 days after it was last used, or until you choose another workspace |
| MCP server usage logs, web server logs and error logs | Up to 30 days |
| Demo data | 7 days after it was last used |
| Record of your consents (provision to a third party and transfer outside Korea: account, AI Assistant and recipient, version of the consent text, time, IP address) | While the connection lasts, then 90 days after it ends (a period INNORIX sets to handle disputes about the consent) |
| Access record of what your AI Assistant did in INNORIX Platform (account, time, workspace, AI Assistant, requested function, result, IP address) | 2 years (INNORIX's retention period for these records) |
| Audit Log entry that a member used an AI Assistant in a workspace (shown to the workspace owner; at most once every 30 days per member, workspace and AI Assistant) | 1 year, as other Audit Log entries |
Information deleted from our systems may remain in backups for a limited time, as described in "Backups".
Your choices
You can end a connection at any time:
- ask your AI Assistant to sign out of INNORIX (the sign_out tool);
- remove the INNORIX connector in your AI Assistant's settings;
- contact us.
What ending a connection does:
- Signing out or asking us ends the connection immediately and deletes its connection record and refresh token from our active systems. In apps such as Claude and ChatGPT, one connection is shared by all your conversations and devices in that app, so all of them will need to connect again. Connections from other apps are not affected.
- Removing the connector in your AI Assistant's settings stops further transfers, because that AI Assistant no longer calls the connector. The connection record is deleted after 90 days without use, or immediately if your AI Assistant revokes its token when you remove the connector. To delete it right away, sign out or contact us.
- When what you consented to changes (for example, a new recipient for an AI Assistant), that connection stops and you are asked to consent again when you reconnect.
- What stays: ending a connection does not cancel scheduled transfers, flows or transfers already in progress, and does not delete your transfer history in INNORIX Platform, which is kept as described in the other sections of this Privacy Policy. The record of your consent is kept for the period in "Retention by INNORIX". INNORIX has no technical means to delete information that has already been sent to your AI Assistant provider. You can delete it with that provider's tools or by contacting the provider, and you can also contact INNORIX for help with your request.
You choose which permissions to grant each time you connect. To access, correct or delete other information, see "Your Choices and Rights".
Demo mode
You can try the connector without an INNORIX account. In demo mode, the connector uses simulated sample data and does not call INNORIX Platform. The sample data is tied to a random demo session identifier and is deleted 7 days after it was last used. The sample data contains no real personal information, but demo requests are recorded in the same service usage logs and web server logs as other requests (including the IP address and user agent) and kept for the same period.
Contact
For privacy questions about the connector, or to ask us to end a connection or delete information, contact:
INNORIX, Privacy Manager
- Email: general@innorix.com
- Addresses and phone numbers: see Global Offices
On-Premises & Customer-Managed Environments#
For Customer-managed deployments, the Customer controls its own:
Infrastructure
Storage
Network
Operating systems
Local databases
access permissions
Personal Data stored exclusively in Customer-managed Infrastructure remains under the Customer's direct technical control unless it is transmitted to an INNORIX-managed Service.
Air-Gapped Environments#
Air-Gapped deployments may operate without routine online communication with INNORIX Cloud.
Information may still be provided to INNORIX when the Customer chooses to submit:
support information
license information
signed usage information
diagnostic data
Such information is handled according to this Privacy Policy and applicable agreements.
Children#
INNORIX Services are designed for organizations and business use and are not directed to children as consumer services.
Changes to This Privacy Policy#
INNORIX may update this Privacy Policy to reflect changes in:
Services
data-processing practices
legal requirements
Material changes will be communicated through appropriate website, Account or contractual channels where required.
Privacy Questions#
Questions concerning this Privacy Policy or INNORIX's processing of Personal Data can be submitted through the Contact channel provided on the INNORIX website.
Where the request concerns Customer Personal Data processed on behalf of an INNORIX Customer, the request should generally be directed to that Customer first.
Privacy contact. INNORIX has designated a Privacy Manager who is responsible for the processing of personal information and for handling related questions, requests and complaints.
- Company: INNORIX
- Contact: Privacy Manager, general@innorix.com
- Addresses and phone numbers: see Global Offices
Related Resources#
Security
Security architecture and safeguards for INNORIX Services.
Data Processing Addendum
Terms governing Customer Personal Data processed by INNORIX on behalf of Customers.
Subprocessors
Service providers involved in processing data for eligible INNORIX Services.
Cookie Policy
Information about Cookies and similar technologies.
Cookie Preferences
Controls for non-essential Cookies.
Terms
General terms governing use of INNORIX Services.