Privacy Policy.

01Who we are

We serve customers in India, the UAE and internationally. R-Series is developed by DCS Labs, a DCS AI Technologies initiative. In this policy "R-Series", "we" and "us" refer to the companies named above. We decide how and why the personal data described here is used.

This policy covers dcslabs.ai, including its R-Series pages. Privacy contact: hello@dcslabs.ai.

02The short version

• No accounts. Visits are counted without cookies; LinkedIn's advertising tag loads only if you accept optional cookies.
• We receive personal data mainly when you send the briefing form or write to us. Briefing requests are stored by our host for 365 days and emailed to our team.
• Your briefing-form answers and the emails you send us are never sold and never shared for advertising; we do not pass them to LinkedIn. If you accept optional cookies, LinkedIn's advertising tag receives data about your visit and your device (the page viewed, the referring page, your IP address, browser and device type) and LinkedIn's own cookie identifiers, which we use to measure visits that come from our LinkedIn posts and adverts.
• You can ask us to show, correct or delete what we hold about you.

03What we collect

When you contact us

Your name, email address, organisation and role, the content of your message and any attachments.

The briefing request form

The form asks for your name, work email, role, organisation and country, your organisation's type and size, when you would like to start and your role in the decision, and for your agreement that we may contact you about a briefing. Areas of interest, a budget band and a message are optional. The form also sends the address of the page it is on. When you press send, the request goes to a small service we run on Cloudflare at dcslabs.ai. It checks the answers, stores the request in Cloudflare Workers KV (our host's storage) and sends a notification containing the request to our team's Google Gmail inbox through Cloudflare Email Routing. With each request the service also stores the time, your browser's user-agent text, the country Cloudflare reports for the connection and a SHA-256 hash of your IP address, which it also uses to accept at most five requests an hour from one network. A hashed IP address is still personal data: it can be matched back to an address. Nothing you type is kept in your browser; if sending fails, your answers stay on the page so you can try again.

When you visit

The services that deliver the pages process technical data: your IP address, browser and device type, the page requested, the time and the referring page. Our host, Cloudflare, adds its Web Analytics script to the pages; it counts visits without cookies. If you accept optional cookies, the LinkedIn Insight Tag also loads, from LinkedIn. Typefaces and the site's own code are served from the site itself. We do not use this data to identify or profile you.

Operational logs

Our host also keeps operational logs for us of the requests our briefing-form service handles: every request to the form, and any page or video the service delivers itself. They hold two kinds of record. Request metadata: the time, the request method, the address requested without its query string, the response status and processing time, and the request headers and connection details our host records, which can include your IP address, your browser's user-agent and the country and network the request came from. Error events: the name and outcome of the event, a status code or error type, and a random reference that ties it to one request. We use these logs only to keep the service secure and to find and fix faults. They never contain your form answers or your message, and our service writes no password, key or other secret into them.

Demo verifier

The demo verifier runs entirely in your browser. Receipt text you paste into it is checked on your device and is not sent to us by the demo, and nothing is saved when you leave the page. Do not paste private keys or confidential data.

04Why we use it, and on what basis

05What we do not do

• We do not sell, rent or trade the personal data we hold. Your briefing-form answers and the emails you send us are never sold and never shared for advertising; we do not pass them to LinkedIn.
• The only advertising-related processing is the optional LinkedIn measurement described above, which runs only after you accept optional cookies and stops when you withdraw. We do not use personal data for profiling, or for automated decisions that have legal or similarly significant effects.
• We do not ask for sensitive data (health, biometrics, identity documents, religion, political views and similar). Please do not send it.

06Who else sees it

Only the service providers we need:

• Cloudflare, Inc. — hosts the site; runs our briefing-form service and stores briefing requests in Workers KV; routes form notifications and messages sent directly to our published email addresses to our Gmail inbox through Email Routing; stores operational request and error logs for us; counts visits without cookies through Web Analytics; and protects the site against attacks. Cloudflare also processes some data as an independent controller for its own security purposes.
• Google LLC (Gmail) — hosts our inbox: it receives the notification of each briefing request and the messages you send directly to the addresses on this site.
• Resend, Inc. — delivers our outgoing transactional email: we send it from our Gmail inbox through Resend's SMTP service (Gmail "send mail as"). Resend receives each outbound message and its delivery metadata, and keeps delivery logs under its own terms.
• LinkedIn — only if you accept optional cookies: its advertising tag, the LinkedIn Insight Tag, receives data about your visit and your device (the page viewed, the referring page, your IP address, browser and device type) and LinkedIn's own cookie identifiers; we use it to measure visits that come from our LinkedIn posts and adverts, and LinkedIn processes this data under its own terms. LinkedIn never receives your briefing-form answers.

We may also share data with professional advisers under confidentiality, with authorities where the law requires it, or with a successor if our business is reorganised. Each provider works under its own terms and data-processing commitments; their roles and processing locations differ.

07International transfers

Our providers operate infrastructure in several countries, so your data may be processed outside your country. Where the law that applies to a transfer requires a safeguard, we use the mechanism that law recognises. Ask us for information about the safeguards for a given transfer.

08How long we keep it

How long we keep personal data depends on why we hold it. We look at whether we still need it to answer you or for an ongoing relationship with you, whether we need the record to show what was asked or agreed, and whether a law or an active matter, such as a dispute, requires us to keep it. Where a fixed period applies, it is stated below.

• Briefing requests stored by the form service are deleted automatically 365 days after they are sent. A note that a request's notification email failed is deleted after 90 days.
• Enquiry emails are kept as business correspondence for as long as the relationship or record is needed; we do not delete them on a fixed schedule. You can ask us to delete your enquiry at any time by writing to hello@dcslabs.ai. This covers the messages you send us directly and the notification email of each briefing request in our Gmail inbox, which is not deleted when the stored request is.
• Operational logs of our briefing-form service (request metadata and error events) are kept by our host, Cloudflare, for at most seven days and are then deleted automatically. We do not send them to any other service.
• Records needed for an active matter or a legal duty follow a separate documented schedule, and we review them periodically.
• Deleted messages can remain for a limited time in our providers' restricted backups before they are overwritten.

We keep restricted security and technical records where Indian law requires them, separately from enquiry correspondence, and we keep message content out of those records.

09Security

The site is available over HTTPS. Briefing requests are kept in our host's storage, which only our own Cloudflare account can read, and access to our inbox is limited to the people who need it. No system is perfectly secure; if a breach affects your data, we will notify you and the authorities where the law requires.

10Your rights

Your rights depend on the law that applies to our processing, under the Indian law that currently applies to our processing, including the Information Technology Act, 2000 and its rules, and, where they apply, the EU or UK GDPR. The Digital Personal Data Protection Act, 2023 (DPDP Act) and its Rules come into force in phases (commencement notification); its rights and procedures will apply to us as the relevant provisions commence. We help with access, correction and deletion requests now, and we will apply the DPDP Act rights as its provisions come into force. Depending on that law, you can ask us to access, correct or delete your personal data, to restrict or object to how we use it, to receive it in a portable form, or to withdraw consent at any time without affecting earlier use.

Write to hello@dcslabs.ai. We respond without undue delay and within the period the applicable law sets; where the EU or UK GDPR applies this is normally one calendar month, and we tell you within that month if we need to extend it. We ask only for the information reasonably needed to confirm it is you. You can also complain to the competent authority under the applicable law (under the DPDP Act, the Data Protection Board of India, once the relevant provisions are in force) or to the data protection authority where you live.

Privacy and grievance contact. Write to hello@dcslabs.ai with the subject "Grievance". We aim to acknowledge within 48 hours and resolve within the period the applicable law sets.

11Children

The site is meant for professionals. If you believe we hold information about a child, tell us and we will look into it promptly.

12Cookies

See our Cookie Notice.

13Changes to this policy

The version and date at the top show the latest update. Changes apply from the date shown; if we change how we use personal data in a meaningful way, we will say so on this page before the change takes effect. We keep earlier versions.

14Contact