Encryption, access controls, secure connectivity, and independently assessed controls protect your data and credentials across every Skyvia product.
Skyvia has completed a SOC 2 Type 2 examination covering controls relevant to security, availability, and confidentiality.
Data transmitted to and from Skyvia is protected using TLS. Private data stored by Skyvia is encrypted using AES-256.
Skyvia supports customers’ GDPR obligations through a Data Processing Agreement and contractual safeguards for personal data.
Protect every Skyvia account with two-factor authentication, account-wide MFA requirements, and sign-in allowed only from trusted IP addresses.
Decide who can see and change what. Assign standard or custom roles in each workspace and limit endpoint access to specific users and IP addresses.
Monitor your data operations with activity logs and execution history to review results and troubleshoot issues.
Use Skyvia’s managed cloud, securely connect databases located inside private networks, or choose dedicated and hybrid processing options for workloads with additional infrastructure requirements.
Run your workflows in Skyvia’s fully managed cloud environment hosted on Microsoft Azure in the United States. Skyvia manages the processing infrastructure, platform operations, monitoring, and maintenance. Customer-selectable regions and cloud providers are not currently available.
Connect supported applications via OAuth without sharing application passwords with Skyvia. Secure database connections using SSL or SSH where supported.
Connect databases located inside private networks to Skyvia through an outbound HTTPS connection. Skyvia Agent does not require exposing database ports to the public Internet.
Host Skyvia Connect SQL and OData endpoints in your infrastructure, keeping source-data traffic within your environment. Endpoint configuration is managed in Skyvia, and activity logs are sent to Skyvia for monitoring.
Run Data Integration workloads on a VM dedicated to your organization. Processing compute is separate from the shared execution environment, providing dedicated capacity for high-volume and business-critical workloads.
Data processing and retention depend on the Skyvia product and the workflow you configure. Select a product to understand how data is processed and what information Skyvia retains.
Skyvia transfers data from the source system to the target system according to the integration workflow configured by the user. During an operation, Skyvia may temporarily cache portions of the processed data. This cache exists only while the operation is running and is deleted immediately after it finishes.
Skyvia stores integration run history and operational logs. Per-record error logs may contain portions of the processed data. For certain integration types and data sources, Skyvia may also store per-record logs for successfully processed records.
Downloadable export files are retained for seven days and can be deleted earlier by the user. Users can also manually clear integration run history and associated per-record logs for a selected period.
Skyvia Automation executes the triggers, actions, and workflow logic configured by the user across connected systems.
Skyvia stores automation execution history and detailed execution logs for monitoring and troubleshooting. Execution details may include input and output data values processed by Trigger, Action, and Set Variable components.
Automation logs are retained for seven days on the Free plan and 60 days on the Standard plan.
Skyvia creates snapshots of the data selected in the backup configuration.
Backup snapshots are encrypted and stored in Azure geo-redundant storage. Customers can manually delete snapshots or configure Skyvia to automatically remove the oldest snapshots when the storage limit included in their subscription is reached. All remaining backup snapshots are deleted when the Skyvia account is deleted.
Queries are executed against the connected data source.
Skyvia may temporarily cache portions of the queried data while the operation is running. This temporary cache is deleted immediately after the operation finishes.
Skyvia Connect provides live API access to the objects and operations exposed through the configured endpoint.
Skyvia stores the endpoint configuration and activity logs. Activity logs include the request date and time, execution status, transferred data volume, HTTP method, remote IP address, and requested URL. Activity logs are retained for as long as the Skyvia account remains active and are deleted together with the account.
Among the results of implementing, Skyvia helped us remove redundancies in the processes, reduce data gaps, and thus save overall cost.
“I definitely think that Skyvia has very good flexibility.”
“By leveraging the strengths of FieldAx and Skyvia, the company has not only streamlined its job management processes but has also positioned itself for long-term growth.”What Skyvia retains depends on the product and workflow being used. See the “Understand how Skyvia handles your data” section for product-specific information.
Skyvia uses OAuth for supported applications. OAuth tokens, database credentials, and other stored connection parameters are encrypted.
Internal access is restricted to authorized personnel with a legitimate business need and is governed by role-based and least-privilege controls.
Skyvia’s managed cloud environment is hosted on Microsoft Azure in the United States. Skyvia does not currently provide customer-selectable hosting regions or cloud providers.
Yes. Users can enable two-factor authentication, and account administrators can require account users to use MFA.
Yes. Skyvia supports account-level IP filtering. Skyvia Connect endpoints can also have their own IP restrictions.
Skyvia Agent securely connects a database inside a private network to the Skyvia cloud through an outbound HTTPS connection. Connect Hybrid Deployment runs the SQL or OData endpoint runtime inside the customer’s infrastructure. It is currently available only for Skyvia Connect.
Enterprise Dedicated VM provides processing compute dedicated to one organization and separates its Data Integration workloads from Skyvia’s shared execution environment.
Skyvia collects audit information, but a customer-facing audit log interface is not currently available. Audit information may be provided upon request.
Custom management of execution-log retention is not currently available.
The full Skyvia SOC 2 Type 2 report is available to customers and prospective customers upon request and after an NDA is signed. Request the SOC 2 Type 2 Report
All customer data is then deleted from all Skyvia resources permanently.