Hi,
An "account without login", that's the role of guest checkout, which you already have on your website. You could turn off login and registration in the settings under the Checkout tab of the HikaShop configuration to only offer guest checkout to your customers. That way, no login / activation / privacy consent would be needed.
I checked your checkout registration.
You're not using Joomla's standard GDPR plugins and privacy component to be compliant with GDPR. If you did, you would see the privacy consent toggle directly on the HikaShop registration form:
www.hikashop.com/support/forum/customers...gistration-link.html
From what I can see on your website, it seem that you're using the Akeeba DataCompliance component:
extensions.joomla.org/extension/akeeba-datacompliance/
It has a PDF freely available which explains its setup here:
www.akeeba.com/download/datacompliance/2...tacompliance-pdf.pdf
There, in the " 8.2. System plugin configuration" section, it says:
The System - Data Compliance plugin makes it possible to capture the login of users who have not yet consented
to processing of their personal information. It's advisable to keep it published at all times.
The captive login works by means of redirections. If the current user has not provided their consent (or has
withdrawn their consent) they are immediately redirected to Data Compliance's self service page. Trying to
navigate to another page causes another redirection. This way the user is captured in the self-service page until
they provide consent (they can also log out of the site if they want to).
The same trick may be used by other components to provide a captive login. For example, Akeeba LoginGuard
(our Two Step Verification component for Joomla) does the same thing. To prevent a redirection loop you must
let Data Compliance know which third party components are allowed to be accessed without the user providing
their consent. Moreover, you can specify other components here which don't collect personal information and are
therefore allowed (e.g. com_content which is the Joomla articles component).
The Exempt components / views / tasks takes one specification on each line. Each specification consists of a
component, view and task separated by dots. When you want to match any value in a position using *. For example,
to allow access to single article views in com_content use the specification com_content.article.*
By default, only Akeeba LoginGuard is allowed to be accessed: com_loginguard.*.*
So, one option would be to configure this plugin to exclude HikaShop from it so that customers would be able to proceed to the checkout without going through the DataCompliance page after the activation.
Also, on the JED page, it says:
Just like Joomla's comprivacy, the component itself does not know how to do any of that for any component's or core data. It uses plugins which tell it how to handle core Joomla and extensions' data. We ship plugins for core Joomla user data and some of our extensions. That said, DataCompliance can use the same “privacy” plugins used by Joomla's comprivacy itself.
So, apparently, instead of using this system plugin for the privacy consent, it should be possible to use Joomla's system plugin. And in that case, the privacy consent toggle would be added to the registration form automatically and that wouldn't break the workflow for the customer.
So, basically, I think that the problem here is a configuration issue in the DataCompliance plugins or the Joomla plugins for privacy consent, and I don't think you need to change something in HikaShop.