Registration privacy

Controller: Hans-Jochen Dethlefs, Neptunring 2, 16321 Bernau bei Berlin, Germany. Contact: kontakt@canhome.shop.

Account and shop application

To sign you in, we process your email address, a one-time code stored only as a hash, and a session. A buyer profile stores the name, delivery address and optional profile link you provide. A shop application stores operator, contact, market, location, team and design details. We use this information to prepare the account or shop you requested (Article 6(1)(b) GDPR). Shop name, description and market details may appear in the public directory as soon as the shop is created; private operator, team and review records remain protected. Buyer details are not yet sent to merchants or payment providers through this service.

CANHOME membership

When you explicitly book, we store the shop, verified owner, invoice recipient and address, the price and agreement version displayed at booking, and booking and cancellation timestamps. A confirmation goes to the verified account email; we record whether the mail server accepted it. We use these data to conclude and manage your requested membership (Article 6(1)(b) GDPR) and retain them only for contract handling and applicable retention duties. No membership invoices are issued before 2027; no bank details are requested when booking.

Operator review

After submitting a shop application, you can provide a self-certification, a merchant account ID at an external payment provider and identity evidence. An uploaded identity image is converted into a new PNG without image metadata and stored encrypted in the separate registry database. Alternatively, you can provide a reference to an externally verified electronic identity. Only explicitly enabled and email-verified CANHOME reviewers can open the private case and image; image access and review actions are logged. We do not request bank account or card data here. These details support operator review, the future contract, fraud prevention and applicable legal traceability duties. Whether trader traceability duties apply also depends on platform size and the market served.

Unzer test connection

A shop owner may voluntarily add the shop's own Unzer sandbox key pair. A separate record stores the public key and its fingerprint, the encrypted private key, verification status, reported test payment methods and change times. The private key is not displayed again after saving and is used server-side only to check the account with Unzer. Verification events contain no keys. The owner can remove the connection and stored private key; key-free audit events remain. This preparation does not enable payments. We process these details to prepare the shop as requested by its owner (Article 6(1)(b) GDPR).

PayPal test connection

A shop owner may voluntarily add the client ID, client secret and merchant ID of the shop's own PayPal sandbox app. We store a fingerprint of the client ID, the encrypted client secret, the merchant ID and verification and change times separately from the shop details. The secret is never displayed again and is sent only to PayPal's OAuth endpoint for a server-side credential check. This check does not verify the entered merchant ID, product approval or a payment. The owner can remove the connection and secret; a key-free change history remains. Processing supports the requested shop setup (Article 6(1)(b) GDPR).

Messages to shop operators

Enabled CANHOME staff can send a message to a verified shop owner in the private operator record. We store its subject and text, the accounts involved, timestamps, the mail attempt status and an explicit read confirmation made by the owner. The text is also sent to the owner's registered email address. SMTP acceptance does not prove delivery or that the owner has read it. Processing supports the requested or existing shop relationship (Article 6(1)(b) GDPR) and, where needed, documented handling of complaints or abuse (Article 6(1)(f) GDPR). Only the relevant owner and authorized CANHOME staff may view the message. We keep it while needed for case handling, the contract or applicable retention duties.

Reports about shops and offers

For a report we store the verified account and email address, the shop concerned, the selected issue type, your description, an optional page path, timestamps and case, mail and acknowledgment status. Only authorized CANHOME reviewers see the report and your identity. Where needed, they send a separate review or correction request to the shop concerned; your email address is not automatically shared. An operator response is stored in the private case. We process this information to document and handle specific complaints and abuse (Article 6(1)(f) GDPR). Our legitimate interest is investigating and remedying specific issues. We retain it for case handling and then only as required by applicable retention duties. The receipt names the case number; SMTP acceptance does not prove actual delivery.

Before sign-in, we keep the selected shop, a cleaned HTTPS page link and a description of up to 250 characters in the session and requested email challenge; the challenge is usable for 15 minutes. The sign-in email includes that link and a one-use code link. After submission, encrypted original copies of the sign-in, staff and receipt emails, including creation and SMTP acceptance times, are held in the private case for authorized CANHOME reviewers. Unfinished sign-in attempts may remain with the email challenge until technical cleanup.

An optional image is converted into a new PNG without image metadata and stored encrypted. You and authorized CANHOME reviewers can open it in the private case; image access is logged. The shop concerned sees it only if a reviewer explicitly shares it when forwarding the case. The image is not emailed. A local automated precheck records missing evidence and exact repeats from the same account. It does not decide truth, intent or case handling; people review the case. Report text and image are not sent to an external AI service for this check.

Public branches and map

Branches and sales points of a listed shop automatically appear with their names and business addresses on the shop profile and in the directory. Warehouses and other internal locations remain private. The owner can hide a sales point in the shop account. Email and phone appear only after a separate choice by the owner. An exact map pin appears only after coordinates are checked against a documented source; until then the map shows only a country position. Search engines and other parties may cache public details. CANHOME serves the world map itself; OpenStreetMap opens only through the map link.

Technical protection and email

The web server processes connection data needed to deliver the page. We limit code requests per email and IP to prevent abuse; stored IP rate keys are HMAC hashed. The basis is Article 6(1)(f) GDPR. Codes expire after 15 minutes; code records and rate counters are removed within 24 hours. The existing AZUBI42 mail server sends sign-in, team and operator messages to the registered address. Necessary session and CSRF cookies apply only to the registry.

Shop statistics

For public shop statistics, we count HTML page requests in local web server logs. These contain the shop host, time, page path, response type, IP address and browser identifier. We use IP address and browser identifier only to estimate daily visitors per shop; they are not copied into the statistics. We do not combine usage across shops, build visitor profiles, add analytics cookies or use external analytics services. Raw logs are removed after 14 daily rotations; daily aggregates remain for at most 90 days. Owners see only their own shop totals. Country and city figures come from their own Saleor orders and are displayed in aggregate. The basis is Article 6(1)(f) GDPR; our legitimate interest is understanding shop reach and operation.

Storage and rights

Your account, buyer profile, private shop applications and review evidence remain while needed for review, the contract or applicable retention duties. Encrypted evidence may also exist in protected database backups. After a contract ends, applicable periods are assessed and the data is then deleted; if trader traceability under the Digital Services Act applies, its evidence is generally retained for six months after the contract ends. You can correct your profile in the registry. Where the legal conditions apply, you may request access, erasure, restriction, data portability or object to processing via kontakt@canhome.shop. You may complain to a data protection authority. We will explain any additional data flows before enabling a payment connection.

Updated: 1 November 2026.