Privacy Policy
Privacy Policy
Privacy is an important part of building trust. This policy explains how Zaya Web Studio handles personal information in connection with website visits, enquiries, project discussions and digital services. It also explains practical steps you can take to protect your information.
About This Privacy Policy
Zaya Web Studio provides digital services that may include website development, Shopify and e-commerce setup, mobile application development, admin panels, backend systems, integrations, SEO and technical support. Depending on the service requested, we may need to receive and use certain information to communicate with you or carry out agreed work.
This policy describes the general principles for handling personal information in those interactions. It applies, as relevant, when you browse our website, submit a contact form, request a quotation, share project requirements, communicate with our team or ask for support.
A separate project agreement, platform policy or service-specific notice may also apply. If a specific feature has its own privacy notice, that notice should be read alongside this document.
If you contact us about an e-commerce website, we may use the contact details and requirements you provide to understand the project, prepare a quotation and reply to your enquiry.
Information We May Collect
The information involved depends on what you choose to share and which website features or services are enabled. We do not suggest that every category below is collected in every interaction.
Contact Information
Your name, email address, phone number, business name and the contact details you choose to submit.
Enquiry Details
The service you are interested in, your budget range if shared, project goals, questions and communication history.
Project Materials
Text, images, product lists, design references, documents and other files you provide for an agreed project.
Technical Information
Depending on the systems used, server logs may contain IP addresses, browser details, device information, page requests and timestamps.
Support Records
Bug reports, feedback, requested changes and relevant correspondence about a project or service.
Transaction References
Where relevant, payment status or transaction references needed to reconcile a service payment. Card and banking information should normally be handled by the relevant payment provider.
A client may provide product titles, descriptions, images, prices and category information. These materials can be used to set up the agreed store. Unrelated personal information is not needed simply to upload products.
Where Information Comes From
Depending on the situation, information may come from:
- Directly from you: contact forms, email, calls, messages or project files.
- Project representatives: a business owner or authorised team member coordinating work.
- Website systems: technical logs or usage data generated when supported features operate.
- Service providers: information returned by a provider when you use a relevant integration or transaction process.
- Public business information: information you direct us to use for a project, where appropriate.
We should not collect information from a source or use it for a purpose that is inconsistent with applicable law or the relevant notice provided to the individual.
How We Use Information
Information may be used where reasonably relevant to:
- Reply to enquiries and explain available services.
- Prepare quotations, proposals and project scopes.
- Build, configure, test or maintain an agreed website or application.
- Coordinate milestones, approvals, feedback and delivery.
- Provide support and investigate reported technical problems.
- Maintain website functionality and help detect abuse or suspicious activity.
- Measure website performance where analytics tools are enabled and used appropriately.
- Maintain relevant accounting, contractual or legal records.
- Handle complaints, disputes and legitimate business administration.
If you report that a checkout button is not working, we may review the relevant page, error details and technical information needed to investigate the problem. That does not mean we need unrestricted access to unrelated customer records.
Where required, we will identify the applicable lawful basis for processing. Consent may be appropriate for certain activities; other activities may rely on contractual necessity, legal obligations or another lawful basis available under applicable law.
How Information May Be Handled
The following diagram illustrates a typical enquiry workflow. It is an explanatory example, not a statement that all information follows one fixed technical route.
Information should be made accessible only to people and systems that need it for an authorised purpose. Actual access controls, hosting arrangements and deletion processes depend on the systems used and must be verified operationally.
When Information May Be Shared
We may need to involve a third-party provider to operate a website, communicate with a client or complete a requested transaction. Sharing should be limited to what is appropriate for the purpose.
| Category | Possible purpose | Example |
|---|---|---|
| Hosting providers | Website operation and storage | Hosting website files and technical logs |
| Email services | Business communication | Receiving and sending enquiry emails |
| Analytics tools | Website measurement | Understanding page visits, if enabled |
| Payment providers | Payment processing | Processing a checkout transaction |
| External APIs | Requested integration | Connecting a service to an application |
| Professional advisers or authorities | Legal or compliance purposes | Responding to a valid legal requirement |
Providers may process information under their own terms and privacy policies. Their actual involvement depends on the tools enabled for the relevant website, project or transaction.
We do not claim that every provider listed here is currently integrated into our website. Before publication, the list should be checked against the live technical setup.
If a payment gateway is used, the gateway may process the payment information needed to complete the transaction. The gateway's own privacy terms apply to its processing. The website operator should not claim that it never receives payment-related data unless the actual integration confirms that.
Cookies and Similar Technologies
Cookies are small pieces of information that a website may store in a browser. Similar technologies can be used for sessions, preferences, measurement or other functions.
Essential functionality
Some technologies may be needed for security, session handling or features explicitly requested by the visitor.
Measurement and preferences
Other technologies may help measure usage or remember choices, depending on the website configuration and applicable consent rules.
You can manage cookies through your browser settings. If the website provides a consent-management interface, you can use it to manage supported choices. Blocking certain cookies may affect functionality.
If an analytics tool is enabled, it may collect usage events that help identify which pages are visited or whether a page is experiencing errors. The exact data collected depends on the configuration and the provider's technology.
Before publishing, verify the actual cookies, analytics tags, advertising pixels, embedded media and consent controls on the live site. This section must reflect what is really enabled.
Data Security and Confidentiality
Information security depends on the systems used, the sensitivity of the information and the access provided to people or providers. Appropriate safeguards should be implemented and maintained according to those risks.
Access control
Limit access to information and project systems to authorised people who need it.
Secure communication
Use suitable secure channels for account access and confidential project materials.
Credential handling
Avoid sharing passwords in public documents or ordinary messages where safer options exist.
Incident response
Security concerns should be reviewed promptly and handled under applicable requirements.
No online service or transmission method can be guaranteed to be completely secure. Do not send unnecessary sensitive information through an unsecured channel.
Where supported, a client can create a separate staff or collaborator account with only the permissions required for the task, instead of sharing the main account password. Access should be reviewed and revoked when it is no longer needed.
How Long We Keep Information
Information should be kept only for as long as reasonably necessary for the relevant purpose, subject to legal obligations, legitimate business needs and applicable requirements.
| Information category | Retention consideration |
|---|---|
| General enquiries | May be kept while responding and for reasonable follow-up or recordkeeping. |
| Project correspondence | May be needed to document scope, approvals, delivery and support. |
| Accounting records | May need to be retained for applicable legal or tax requirements. |
| Technical logs | Retention may depend on hosting, security settings and operational needs. |
| Temporary access credentials | Should be removed or revoked when no longer needed, subject to the agreed workflow. |
These are general considerations, not fixed retention periods. Actual periods depend on the record type, system configuration and applicable law. Information that no longer needs to be retained should be securely deleted or anonymised where appropriate and feasible.
Your Privacy Choices and Rights
Depending on the applicable law and circumstances, you may have rights to request access to, correction of or deletion of personal information, object to certain processing, request a copy of information, or withdraw consent where consent is the relevant basis.
The availability and scope of these rights vary. Some requests may be limited by legal retention obligations, the rights of other people or other lawful exceptions.
- Access: ask whether relevant personal information is being processed and request access where applicable.
- Correction: request correction of inaccurate or incomplete information.
- Deletion: request deletion where the law provides that right and no valid exception applies.
- Consent withdrawal: withdraw consent for processing that relies on consent, where applicable.
- Complaint: raise a concern about how personal information is handled.
If we hold an incorrect email address for a current project, contact us with enough information to identify the relevant record. We may ask for reasonable verification before updating it.
To submit a request, use the contact details at the end of this policy. We may need to verify identity, clarify the scope of a request and explain where a legal exception applies.
Children's Privacy
Our services are primarily intended for businesses, organisations and people seeking digital services. We do not knowingly seek personal information from children where collecting it would be unlawful.
If you believe a child has provided personal information through our website inappropriately, contact us with relevant details. We will review the concern and take appropriate steps where required by applicable law.
External Websites, Platforms and APIs
Our website or a project we build may link to or integrate with third-party platforms. These may include hosting providers, e-commerce platforms, analytics services, communication tools, payment gateways or APIs, depending on the project.
Each provider may have its own terms, privacy notice, security practices and retention arrangements. Zaya Web Studio does not automatically control the provider's independent processing.
Store customer information, order information and payment processing may involve different platforms. The store owner should review the privacy responsibilities and configuration of each platform and integration used.
A third-party link or integration should not be interpreted as a guarantee of that provider's services or a claim of official partnership unless the relationship has been verified.
International Processing and Transfers
Digital services may rely on infrastructure or providers operating in different countries. As a result, information may be processed in a location different from where it was originally submitted, depending on the service configuration.
Where international transfers occur, the relevant legal safeguards and disclosures depend on the information, provider arrangements and laws that apply. The actual hosting and provider locations should be verified before making a specific claim about where information is stored.
Information Processed During Client Projects
Website and application projects can involve information that belongs to the client or the client's customers. The roles and responsibilities of each party depend on the project, the instructions given and the applicable law.
For example, a business may ask us to configure a customer registration form or connect an order-management API. The business should determine what customer information is necessary for its service and ensure that its collection and use are lawful.
- Clients should provide only the data and access needed for the agreed work.
- Clients should avoid sending real customer datasets when test data can reasonably be used.
- Project access should be limited to the required systems and permissions.
- Responsibilities for backups, retention, production access and ongoing operations should be agreed for each project.
Where practical, use fictional test accounts rather than exporting a full customer database merely to test whether the form works. If production information is genuinely needed, the parties should agree on an appropriate access and handling process.
Marketing and Promotional Messages
If we send promotional communications, the process should comply with applicable law and any consent requirements. An enquiry about a project should not automatically be treated as permission to send unrelated promotional messages where such permission is required.
If you receive a promotional message and want it stopped, use the unsubscribe mechanism if provided or contact us. Necessary service-related messages, such as a response to an active enquiry, may be handled separately from optional marketing communications.
Automated Processing and AI Tools
Some digital workflows may use automated tools or AI-enabled services, depending on the particular project or configuration. This policy does not claim that personal information is routinely processed by AI tools.
Where a project requires an external tool to process personal information, the relevant purpose, data shared, provider terms and applicable safeguards should be reviewed before that workflow is enabled. Confidential client materials should not be entered into an external tool without appropriate authorisation.
Updates to This Privacy Policy
We may update this policy when our services, website features, provider arrangements or legal requirements change. The latest published version should be available on this page.
Where appropriate, the revised policy should identify its effective date. If applicable law requires notice or consent for a material change, the relevant steps should be taken.
If a new tool changes what information is collected or how it is used, review the privacy notice, cookie settings and consent process before relying on the new configuration.
Applicable Law and Privacy Obligations
Personal information must be handled in accordance with the laws and regulatory requirements that apply to the relevant processing. The precise obligations can depend on the type of information, the people concerned, the service provided and the jurisdictions involved.
Nothing in this policy removes rights that cannot lawfully be excluded. If a provision conflicts with a mandatory legal requirement, the applicable legal requirement takes precedence to the extent of that conflict.
This page provides general information about privacy practices. It is not legal advice and should be reviewed for the specific requirements applicable to Zaya Web Studio.
Contact Zaya Web Studio
For a question about this policy, a privacy concern or a request relating to personal information, contact us through the business channels below. Please explain the nature of your request and avoid sending unnecessary sensitive information.
Email: support@zayawebstudio.com
Phone: +91 9256672764
Contact page: Contact Zaya Web Studio
Legal Information Center: View Legal & Information Center
Explore Related Policies
Important Information
Read general information about Zaya Web Studio's services and documentation.
Contact Information
Find the published contact channels for enquiries and business communication.
Client Responsibilities
Understand how clients can safely provide requirements, content and account access.
Terms of Use
Review the rules that apply to the use of the website, where published.