Built for site operations
Construction workflow data
ARCHOS processes operational records such as site diaries, vendor activity, cost logs, material movements and project health signals.
Collected data
Account, site and usage records
We collect only the information reasonably required to operate the ARCHOS platform, secure accounts and support project collaboration.
Security
Operational safeguards
Customer workspaces are isolated logically and access to production systems is limited to authorized personnel with business need.
Payments
Processor-handled transactions
Card and UPI payment credentials are handled by our payment partners. ARCHOS stores billing references, invoices and subscription status only.
Information we collect
We collect information directly from you, from your organization’s administrators and from normal use of the platform.
- Identity details such as name, work email, mobile number, company name, business role and user permissions.
- Workspace records such as project names, site identifiers, attendance markers, budgets, vendor details, expenses, materials, reminders and reports entered into ARCHOS.
- Support and communication records including onboarding notes, implementation emails, product feedback and customer support conversations.
- Technical usage information such as browser type, device attributes, IP address, session activity, timestamps and security logs.
Account information
When an account is created, we store the minimum information needed to authenticate users, assign permissions, maintain audit trails and deliver account notifications.
Organization administrators may invite team members, configure access roles and manage workspace-level settings. They are responsible for ensuring invited users have authority to access the relevant project data.
Authentication records
Login timestamps, password-reset events, invite acceptance history and session verification details are stored to protect accounts and investigate suspicious activity.
Profile information
Names, role designations and company contact details are displayed within the workspace so operational teams can identify who created or approved project records.
Project and site data
ARCHOS is designed for construction project management, so customers may upload or record project execution data such as site diaries, petty cash entries, labour logs, material activity, vendor records, document references and completion updates.
This data remains under the control of the customer organization that submitted it. We process it to provide reporting, collaboration, analytics and operational workflows requested by that customer.
Customer control
Each customer is responsible for confirming that the project, workforce and vendor information entered into ARCHOS is accurate and that it may lawfully be shared with the platform.
Device and location data
Some ARCHOS features rely on device context to support site verification and operational integrity.
- Approximate or precise location data may be processed when a customer enables geo-verification, attendance validation or site-based actions.
- Device and browser information may be collected to maintain security, prevent abuse, optimize mobile usability and troubleshoot service issues.
- IP addresses and request logs may be used to identify unauthorized access attempts, enforce rate limits and investigate suspicious account behavior.
Cookies and analytics
We use cookies and similar technologies to keep users signed in, remember preferences, secure sessions and measure product performance.
Analytics data is used in aggregated or event-based form to understand feature adoption, diagnose friction points and improve reliability across desktop and mobile experiences.
Essential cookies
Required for authentication, navigation continuity, fraud prevention and workspace access controls.
Product analytics
Used to understand feature usage, page performance, activation bottlenecks and general customer behavior trends.
Preference storage
Used to remember settings such as display preferences, navigation state or recently used project context.
Cookies
Session and preference controls
Browsers can usually manage cookie settings directly. Disabling essential cookies may affect sign-in and product functionality.
Payment information
ARCHOS uses payment service providers such as Razorpay to process subscription charges, renewals and related billing events. Payment instruments are captured and secured by the payment provider according to its own compliance obligations.
ARCHOS may store transaction references, invoice details, tax information, subscription status, plan type, billing address and payment history necessary for accounting, support and compliance.
How we use data
- To provide and maintain the ARCHOS platform and deliver requested services.
- To authenticate users, manage permissions and protect customer accounts.
- To generate project insights, operational alerts, dashboards and customer-requested reports.
- To process subscriptions, issue invoices, detect failed payments and maintain billing records.
- To communicate service updates, respond to support requests and coordinate onboarding.
- To monitor reliability, investigate incidents, prevent misuse and improve product performance.
- To comply with legal obligations, enforce our terms and resolve disputes.
Data protection
ARCHOS uses administrative, technical and organizational measures designed to protect customer information.
Encryption and transport security
We use standard transport-layer protections for data in transit and secure infrastructure controls for stored application data.
Access management
Internal access is limited by role, reviewed periodically and restricted to personnel supporting infrastructure, security, finance or customer operations.
Monitoring and backups
Operational monitoring, error tracking and backup practices are used to maintain platform continuity and support service restoration when needed.
Security reminder
No internet-based platform can guarantee absolute security. Customers should also use strong passwords, role-based access controls and secure internal device practices.
Third-party services
We may rely on specialized third-party providers for hosting, data storage, customer communications, analytics, error monitoring, authentication and payment processing.
These providers receive access only to the information reasonably necessary to perform services on our behalf and are expected to protect that information appropriately.
Examples
Infrastructure and enablement partners
Examples may include cloud hosting providers, authentication vendors, transactional email systems, customer support tools, analytics vendors and payment gateways.
User rights
Subject to applicable law and the role of the requesting user within a customer organization, you may request access to your personal information, correction of inaccurate data, deletion of information that is no longer required, or export of certain account data.
Where an organization controls the relevant workspace, ARCHOS may direct data-related requests to that organization so the request can be validated and handled correctly.
Request channel
How to exercise rights
Email privacy@archos.in with your name, organization, request type and any supporting details. We may request identity verification before acting.
Retention policy
We retain personal and operational data for as long as needed to provide the service, maintain legally required records, resolve disputes, enforce agreements and support legitimate backup and restoration processes.
If a subscription ends, the customer may request export or deletion of eligible data. Billing, compliance and security logs may be retained for a reasonable period where required for legal, accounting or fraud-prevention purposes.
Contact information
For privacy-related questions, data requests or billing-data clarifications, contact ARCHOS at privacy@archos.in.
Business contact details for formal notices: ARCHOS, Attention: Privacy Team, [Insert Registered Business Address], India. Phone: +91-XXXXXXXXXX.