How we handle data

The controller’s full legal name, registered office and registration details will be added before public commercial launch. Send privacy questions and requests to /help.

Account: sign-in and contact email, verified name, city, required phone number, selected workspace, account type and optional avatar. Verification: KYC/KYB status and Domster reference; for companies, legal name, registration and tax numbers, plus verified representative information. Domster profile: individual services with descriptions and prices, contact, portfolio, weekly availability and subscription validity. Marketplace: jobs, photos, responses, selected Domster, completion, notifications and reviews. Conversations: messages and photos. Packages: announcement credits, unlimited publishing and Domster subscription.

We intentionally provide no fields for street, house number, coordinates or exact location. Do not include such information in text, messages or photos unless you intend to disclose it to the other participant.

We use data to perform the account and access contract, provide features, protect the service, prevent abuse, provide support and meet legal obligations. Marketing and optional analytics will rely on separate consent where required.

You sign in with email and password or with Google; Google then shares your name and verified email address with Domster. Application data and uploaded photos are stored on the computer or server running the application. Infrastructure providers process data on the controller’s instructions. Actual processors, processing locations and international-transfer safeguards must be listed before public commercial launch.

A public Domster profile shows verified name, avatar, city, services, descriptions, prices, portfolio, activity, ratings and verification type. Member avatars and job photos appear to signed-in members with relevant posts. Conversations and attachments are visible only to the participants; an administrator may open one only to handle a safety report or a support request, and every such access is logged with its reason. Domster contact details are always free. KYC/KYB documents or biometric data must not be public and should normally remain with the selected verification provider. Exact location is not published.

Identity (KYC) and company (KYB) checks are carried out by Didit on its own secure pages. Didit processes your ID document, selfie and face comparison, and checks companies in the business register, under its own terms and a processing agreement with the controller. Domster receives and stores only the result, your verified name, a session reference and, for companies, the official name and registration number. Domster does not receive or store document images, document numbers, birth dates or biometric data. Results are re-checked with Didit before they are shown, and a result from Didit’s test environment never appears as verified.

Stripe hosts sandbox payment and identity sessions. Domster stores their references and test status, not identity documents, biometric outputs or card details. Use simulated test choices. Job drafts are private to your signed-in account and also saved on your device for recovery. Discarding or publishing clears the draft. Test jobs are visible to signed-in testers and excluded from public ratings.

Account data is retained while the account is active and then as needed for disputes and legal duties. An expired subscription hides a Domster from search but does not delete the account. Reviews may be retained for system integrity, normally pseudonymised when identification is no longer legally necessary.

Depending on the circumstances, you may request access, correction, deletion, restriction or portability, or object to processing. Consent may be withdrawn at any time. You may complain to the Information Commissioner of the Republic of Slovenia. Send requests to /help; identity will be checked before disclosure.

We use access controls, separation of private and public data and data minimisation. No system is completely secure. Where an incident creates high risk, affected people and the competent authority will be notified within legal deadlines.

Material changes will be published and users notified appropriately. An effective date and version history will be added before public commercial launch.