Privacy Policy
Published 26 October 2026
Who this describes
This policy describes personal data handled by the Imberpech website at www.imberpech.com. The operator's legal name and contact email are not published yet. They are listed at the top of this page.
People in the EU, the EEA, and the United Kingdom have the rights in the GDPR and the UK GDPR. People in Ukraine have the rights in the Ukrainian personal-data law. People in California may have rights under the CCPA/CPRA where that law applies. This page states what the site actually does. It does not claim a registration, a signed transfer contract, or an audit that has not been published.
What you type
- Quiz answers: the kind of PC, budget, games or work, case, storage, and similar choices. They are used to build the Passport.
- A build request or consultation: your name, city, the contact method you pick (Telegram, WhatsApp, phone, or email), the detail you type, your message, the market, the language, and the Passport the request refers to.
- A problem report or a partnership note: the message, the page you were on, language, market, currency, light or dark theme, and a Passport id if one was open.
Imberpech does not run a newsletter and does not ask you to subscribe to marketing email. A sign-in email is only the link or code that lets you open the profile.
What stays in the browser
The quiz, the language, the market, the display currency, the light or dark theme, and a local copy of a shared Passport are stored in the browser's local storage so the site can resume. The quiz copy expires after seven days. That storage is on your device. The Cookie Policy lists it.
A share link is also saved on the server so someone with the link can open the same Passport. Creating the link is what sends that copy.
Accounts
If accounts are switched on and you sign in, Supabase Authentication stores the email address and the sign-in session. Google receives the sign-in only if you choose Google. The profile can store the email, when you accepted the terms, and your preferred language, market, and currency. Saved Passports are tied to that profile, up to the limit shown in the product. You can delete a saved Passport yourself. There is no in-product control that deletes the whole account.
Requests and notices
Build requests, consultations, feedback, and shared Passports are stored so the operator can answer them and so a share link keeps working. When Supabase is configured, those records are stored there. When it is not, the application server keeps its own copy.
A new request or note can be forwarded to a Telegram chat used by the operator. That message contains the details you submitted. Telegram is not used to advertise to you.
Why, and the legal bases we rely on
- To produce the Passport and keep a share link or a saved copy: the steps you asked for. For GDPR, that is performance of a request you made (Article 6(1)(b)) where a contract or a requested service exists, and otherwise the legitimate interest in answering the quiz you started (Article 6(1)(f)).
- To reply to a build request, consultation, or feedback note: the same request, and the contact detail you gave for that reply.
- To keep the site secure, refuse abuse, and remember a sign-in: legitimate interest, and a legal duty if one applies.
- Account terms acceptance: the record that you accepted the terms before the profile was used.
We do not use your quiz or your contact details for advertising, analytics products, or a mailing list. There is no separate marketing consent because that processing is not running.
How long
- Quiz progress in the browser: seven days, then the stored quiz is discarded.
- A saved Passport: until you delete it, or until the profile no longer holds it. The profile caps how many Passports it keeps.
- A shared Passport: while the link is meant to keep working. No automatic expiry is published.
- An open build request or consultation: kept so it can be answered. The product copy says a refused request may have the name, city, contact detail, and message cleared after 12 months. That cleanup is not on a schedule yet, so do not treat 12 months as a job that already runs.
- Feedback notes: kept so they can be read. No shorter period is published.
- Sign-in session: for the life of the session cookie the authentication library sets.
Your rights
Depending on where you live, you can ask for access, correction, deletion, restriction, or a copy of personal data, and you can object to processing that is based on legitimate interest. You can also complain to a data-protection authority. In Ukraine that is the Parliament Commissioner for Human Rights. In the United Kingdom it is the ICO. In the EU it is the authority in your country.
There is no published email for those requests yet. Until the contact address at the top of this page is filled in, we cannot honestly promise a staffed inbox. You can still delete a saved Passport in the profile, clear this site's local storage in your browser, and sign out.
We do not knowingly sell personal information. If the CCPA/CPRA applies to you, you may ask us not to sell or share personal information once a contact address exists. There is no sale or cross-context advertising share to opt out of today.
Children
Imberpech is not directed at children under 13, and we do not knowingly collect their personal data. The site does not ask for a date of birth and does not check age. If you believe a child under 13 has sent personal data, use the contact address once it is published and we will delete what we can identify.
International transfers
Supabase, Google, and Telegram can process data in countries other than yours, including the United States. The operator has not published standard contractual clauses, a transfer impact assessment, or the region of the Supabase project. This page does not claim those safeguards are in place. If you are in the EU, the EEA, the United Kingdom, or Ukraine, that missing detail is a real gap, not a promise that a transfer is covered.
Security
The public site redirects to HTTPS and sends a strict-transport header on that host. Access to stored records is limited to the server configuration and the signed-in user for their own profile. We do not claim a security audit, certification, or that storage is encrypted beyond what the host and Supabase provide by default. No method of transmission is perfectly secure.
Changes
If this policy changes, the new text and date appear on this page. We do not email a policy update, because there is no mailing list for that.
This text describes the site as it works today. It is not a lawyer’s opinion.
