Our approach
Aurinko IT Solutions Pvt. Ltd. develops ArcheVault to help organisations automate data engineering workflows, including data ingestion, profiling, classification, schema discovery, Data Vault 2.0 modelling and data loading.
Protecting customer information requires appropriate application controls, infrastructure configuration, operational processes and customer-side safeguards. Security depends on the specific deployment, its configuration and the data being processed.
This page describes the scope of the service and the security information currently available. It is not a certification, independent audit report, penetration-test attestation or guarantee that all risks have been eliminated.
1. Deployment and data flow
ArcheVault's service architecture can involve application compute, a relational database, cloud object storage, connected source systems, destination databases and third-party services used for AI-assisted classification or notifications.
Depending on the workflow, source data may be processed in application memory, staged in cloud object storage, written to Parquet checkpoints and loaded into a configured destination. Processing metadata, classification results, execution records and related operational information may also be retained.
Customers should not assume that ArcheVault processes only metadata or that source data remains exclusively within customer-controlled infrastructure. The applicable deployment and data-processing agreement should be reviewed before sensitive data is submitted.
2. Authentication and access
ArcheVault currently uses application-level authentication and permission controls. The available authentication and administrative features may differ by version and deployment.
Enterprise single sign-on through SAML 2.0 or OIDC should not be assumed to be available unless it is expressly confirmed in the applicable order form or deployment documentation.
Customers should assign accounts only to authorised users, protect credentials, promptly remove access when it is no longer required and notify Aurinko of suspected account compromise.
3. Customer data handling
ArcheVault may process source records and create temporary processing artefacts to support schema discovery, classification, pipeline execution and resumability.
The types of data processed may include source files, sampled values, schemas, column classifications, execution metadata, generated DDL and destination records. Retention and deletion practices depend on the type of artefact, its storage location and the applicable service configuration or agreement.
We do not promise a universal 24–48-hour purge period. Customers who require a specific retention limit, verified deletion schedule, customer-managed storage or dedicated deployment must obtain written confirmation before submitting affected data.
4. AI-assisted processing
Certain classification functions use AWS Bedrock to access Anthropic Claude models. These workflows may transmit column names, data types, dataset context and sampled source values to the AI service. Sample values may contain personal or confidential information.
Customers must assess whether the relevant dataset may be used with this functionality. Data residency and processing location should be confirmed before use where geographic restrictions apply.
We do not claim that all source samples are automatically masked or that all AI inference is confined to a single AWS region.
5. Encryption and key management
Encryption and key-management protections depend on the relevant cloud-service configuration and deployment. Customers requiring specific encryption standards, customer-managed keys or per-tenant key separation should obtain written confirmation of the controls enabled for their deployment.
We do not represent that dedicated customer-managed encryption keys are enabled for every tenant.
6. Logging and monitoring
ArcheVault may generate application, execution, diagnostic and audit records to support operations, troubleshooting and security investigations. These records can contain identifiers and operational details.
The available log types, retention periods, access restrictions and integrity protections depend on the deployment. We do not claim that every audit record is stored in immutable WORM storage or retained under a universal 365-day policy.
Customers with specific audit, evidence-preservation or regulatory-log requirements should confirm these requirements in the applicable agreement.
7. Shared-responsibility model
Security responsibilities are shared between Aurinko, its infrastructure and service providers, and the customer.
Operating the service according to the applicable agreement, maintaining appropriate controls within its area of responsibility, managing service incidents and communicating relevant information as required.
Customer responsibilities include:
- Using only data the customer is authorised to process.
- Configuring source and destination credentials with the minimum permissions required.
- Reviewing generated schemas, classifications, SQL and data transformations before production use.
- Managing the security of customer-controlled source systems and destination databases.
- Applying customer-specific privacy, retention, residency and regulatory requirements.
- Avoiding real personal, regulated, confidential or production data in the demonstration environment.
The precise allocation of responsibilities is defined by the applicable deployment and customer agreement.
8. Demonstration and pre-production environment
The environment at demo.archevault.com is a pre-production demonstration environment, not a substitute for an approved production deployment.
Do not upload production datasets, real personal information, regulated records, credentials or confidential customer data to this environment. Use synthetic or appropriately anonymised test data unless Aurinko has approved another arrangement in writing. Demonstration features, availability and stored test data may change as the product is developed.
9. Security incidents and vulnerability reporting
If you suspect unauthorised access, exposure of customer information or another security incident involving ArcheVault, contact:
Security contact: [email protected]
Please include a concise description of the issue, the affected environment and the approximate time observed. Do not include passwords, access keys or unnecessary personal or customer data.
We will assess reports and respond in accordance with the applicable agreement and legal requirements. Do not attempt to access another customer's data or conduct intrusive testing without written authorisation.
10. Certifications and independent assessments
Any security certification, independent audit, penetration test or compliance attestation will be stated only where it has been completed, is current and applies to the relevant service scope.
Unless separately documented and verified, customers should not assume that ArcheVault holds SOC 2 Type II or ISO/IEC 27001 certification, or that a particular independent security assessment has been completed.
11. Contact
Aurinko IT Solutions Pvt. Ltd.
For technical security evaluations, vulnerability disclosures, or infrastructure questions:
Corporate Address: Cohort Co-working, 1st Floor, MR Prime, Opp. BKP Homes, Near AMB Mall, Whitefields, Kondapur, Hyderabad, Telangana 500081, India