Dcycle has an identifiable company behind it, official product documentation and a public security centre. Spanish company notices also support the identity given on its website. Taken together, those are good reasons to treat it as a real software business.
That answers the first part of “Is Dcycle legit?”. Whether you should trust it with your company’s data needs a closer look at the service, the paperwork and the way your team would use it.
If you’re the person who gets asked to approve a new business tool, that distinction matters. You need enough information to explain the decision to someone else, especially when the tool will hold invoices, supplier records or other company information.
This article uses official company pages and Spanish public registry notices. It is a document-based assessment, not a hands-on product review or an independent security audit.
Who is behind Dcycle?
Dcycle’s current legal notice identifies the business as The Wake Up Movement, S.L., trading as Dcycle. It lists a Madrid address at Calle Luis Cabrera, 55, and the tax identifier ESB88511373.
There is a useful check outside the company’s own website. Spain’s Official Gazette of the Mercantile Registry, known as the BORME, published a company formation notice for The Wake Up Movement SL in November 2019. A notice published on 28 April 2025 records its move to Calle Luis Cabrera, 55.
The registry reference M-707822 also matches the one in Dcycle’s legal notice. That makes the company identity more concrete than a brand name and a contact form.
These are records of particular company events, not a fresh certificate of the company’s current financial position. They support the identity check without telling you whether the software will suit your business.
Is there enough detail to understand the product?
The official product information describes software for collecting and organising business data, including sustainability and emissions information. There is also a separate developer documentation site.
Those documents describe an API for connecting software, command-line tools for tasks such as bulk uploads, and an integration for AI assistants. They include examples involving facilities, vehicles, logistics and invoices.
You don’t need to understand the code to see why that matters. A technical colleague has something specific to inspect before agreeing to connect another system. They can ask questions about the data involved and how the proposed connection would work.
Documentation is useful evidence of a defined product. It doesn’t show how smoothly your own setup will run. That still needs a demonstration using a task and records that resemble yours.
What does Dcycle say about security?
Its public Trust Center says the platform runs on Amazon Web Services in Ireland. It also describes encryption for stored data and data moving between systems, alongside separate development, staging and production environments.
The same page states that Dcycle holds ISO 27001 certification issued by TÜV Rheinland. It says third-party penetration testing takes place and that results and remediation evidence are available on request.
Those are Dcycle’s published statements. This review has not independently checked the certificate or examined a penetration-test report. If your approval depends on either, request the documents and have the relevant person in your team review them.
Be specific about what you need to understand. Ask which service the documents cover, when they were issued and whether there are limits relevant to your intended use. A general description of security is a starting point for that conversation.
The website privacy policy isn’t the whole picture
Dcycle’s privacy policy makes a distinction that is easy to miss. It covers personal data handled by the company as a controller, including information about website visitors, prospects and account administrators.
The policy says personal data uploaded by customers and processed on their behalf is governed by a separate Data Processing Agreement, available on request.
So, if you are reviewing the platform for work, ask for that agreement. Reading the public privacy page alone won’t answer every question about the information your company plans to upload.
Bring a short list of the records you expect to use. An electricity bill, a supplier invoice and a staff travel record may raise different questions for your team. Knowing what you intend to send makes the discussion much easier.
The public Trust Center also lists subprocessors, including AWS, Anthropic, Cloudflare and OpenAI. Ask which providers are involved in your particular use and what information they handle. A name on that list doesn’t tell you that every file passes through every provider.
Check which terms you are actually reading
The public Website Terms of Use, updated on 17 September 2026, explicitly cover Dcycle’s marketing and information website. They say use of the platform is governed by separate Platform Terms and Conditions and an applicable Master Offer, supplied when contracting.
This matters if you’re trying to work out what you would be buying. The website terms are not the place to establish your subscription price, service commitments or cancellation arrangement.
Get the proposed agreement before making a decision. Check the contracting company, included services, payment schedule, renewal process and what happens when the relationship ends.
If the quote includes help setting up your project, ask what that help covers. There is a practical difference between showing someone around the platform and taking responsibility for preparing historical records. Put the agreed work in writing so both sides expect the same thing.
A demonstration should answer an ordinary question
Once the identity and paperwork are clear, choose one task you want to see. For example, you might ask how a colleague would add a record, spot an error and explain the resulting figure.
Keep the first example simple. Use a made-up or suitably anonymised sample until your team has agreed what information can be shared. You can learn about the process without starting a full migration.
Then ask to see what happens when something is incomplete. Who notices? Who fixes it? Does the person reviewing the work understand what changed?
These are evaluation questions, not claims that this review has tested those actions. The useful result is a clear account of what your team can do, where help is needed and which questions remain open.
Keep a short record of the answers, including anything still waiting on a document or a demonstration. That makes it easier for finance, IT and the eventual users to review the same proposal.
What about reviews and customer claims?
A customer story can give you ideas for questions to ask. It is still a story selected by the supplier, and another company’s experience may involve a different project, team or level of support.
This assessment doesn’t assign Dcycle a review score or repeat customer counts as independently verified facts. It also doesn’t assume that a published success story predicts your result.
If references matter to your decision, ask whether a customer with a comparable setup is available to speak. Useful questions are often quite ordinary: what took the most time to set up, which jobs remained manual, and how did support work when something needed fixing?
You’ll get more from that conversation if you explain your situation first. A small team answering occasional customer requests has different needs from a group gathering information across several locations.
What is the fair conclusion?
The official material gives a reasonable basis for treating Dcycle as an identifiable software provider. Its stated company identity is supported by public company notices, and there are product documents and security information to examine.
That is enough to move beyond the basic question of whether there is a real business behind the name. It is not a guarantee about every feature, every security claim or the outcome of your project.
Before approving it, get the platform agreement, review the relevant data and security documents, and see the task your team needs to complete. If those checks give you clear answers, you can make a decision based on something more useful than a reassuring homepage.