Privacy
What we collect, where it is stored, who processes it, how long we keep it, and how to make it stop. Written to be read rather than to be survived.
Last updated 2026-10-17
Who the controller is
EARTH AROGYAM INNOVATE, a sole proprietorship at Durgapur 713217, West Bengal, India, Udyam registration UDYAM-WB-23-0081393, operating the CoreCanopy service. Write to support@corecanopy.earth for any request under this policy, and it will reach a person rather than a queue. A dedicated privacy mailbox is being created and will be published here when it exists.
Where your data lives
Customer data is stored and processed in Amazon Web Services eu-central-1, in Frankfurt. It is not replicated outside the European Union. Administration of the service is performed remotely from India by the operator, and we treat that access as a transfer for the purposes of Chapter V of the GDPR. For data we process on a customer’s behalf, the transfer is covered by the EU Standard Contractual Clauses (Module Two) and the UK Addendum in our Data Processing Agreement at /legal/dpa, which is pending review by counsel.
What we collect
- Account data: name, work email address, organisation, and authentication credentials in hashed form.
- Inventory data: the activity records, readings, documents and figures you enter or import.
- Operational logs: request metadata retained for one hundred and eighty days, the period India’s CERT-In directions require of us, for reliability, abuse prevention and incident investigation, then deleted by the log service itself rather than by a job we have to remember to run.
- Error traces carrying tenant and correlation identifiers, with personal data scrubbed at source before it leaves our systems. Cookies, headers, request bodies and response bodies are never collected, and there is no session replay.
- Published plans: if you publish a Carbon Reduction Plan, the plan as you filed it, including the name and job title of the person who signed it, is public at its address on this site until you withdraw it. We publish it only on your instruction, and we keep the record of when it was published and withdrawn.
- Product-analytics events, only if you have granted analytics consent: an event name from a fixed list, counts and durations, and opaque identifiers for you and your organisation. No email, no name, no company name, no location. Consent is checked on our servers on every request, so withdrawing it stops collection immediately rather than relying on your browser.
What this website collects
This marketing site sets no tracking cookies and runs no third-party analytics. Fonts are served from this domain, not from a font CDN, so visiting a page here does not disclose your address to a third party. If you submit the working-session form we receive only what you type into it.
Payments
Payments are processed by Razorpay, a payment aggregator regulated by the Reserve Bank of India. Card details are entered on Razorpay’s own form and never touch our systems. Razorpay receives your company name, billing contact and the amount; we receive payment metadata and identifiers back, and keep them with the invoice for as long as tax law requires. Razorpay is listed on the sub-processor page.
Support access
Our staff cannot read your inventory data without your consent. Access is requested, you see the request before deciding, you may refuse it, and a refusal is recorded as an outcome rather than dismissed as a dialog. A granted session can be ended by you at any time, and every screen we opened is written to your own audit trail for you to read.
Your rights
Access, rectification, erasure, restriction, portability and objection, as the GDPR provides. Erasure is implemented in the product and has been rehearsed rather than merely designed: it returns a receipt naming what was retained and the legal basis for retaining it. An Article 15 access request is answered today by assembling the export by hand, within the statutory month; the automated surface for it is built but not finished, and we would rather write that here than let "implemented" cover both.
Retention
- Inventory data: for the life of the account, then erased on request or on closure.
- Filed reports and their audit entries: retained while the account exists, because they are the record the service exists to keep.
- Operational logs: one hundred and eighty days.
- Billing records: as tax law requires.
This policy is in review with counsel alongside our contract set. Where it is silent or imprecise, that is because we would rather leave a gap visible than fill it with language we cannot stand behind.