Privacy Notice

Controller and scope

The controller responsible for the processing described here is:

Marcel Derau (Owner & Founder)
Upbiddr – Ranking & Visibility Platform
Schnepperter Str. 15
42719 Solingen
Germany

Privacy contact: contact@upbiddr.com.

This notice covers Upbiddr’s website, account and profile functions, ranking cards and links, payments and rewards, communications and the processing we perform as operator of official Upbiddr social-media profiles. Our currently operated social-media profile is Upbiddr on X. This notice also covers our own corresponding processing on additional official profiles that we may establish; relevant platform-specific details will be provided when a channel is added. It does not state that unidentified platforms are currently used.

Independent destinations, social-media platforms and payment providers also process data under their own notices. The respective roles depend on the processing, not merely on a link to this notice.

Hosting and email

Upbiddr uses Keyweb hosting infrastructure and SMTP on the Keyweb server for application email. This includes the technical processing necessary to deliver pages, operate the application and database, maintain security and send requested or service-related messages. Hosting and email infrastructure can process network and technical connection data in addition to the information stored by the application.

The purposes are to provide the service, perform contracts and communications, protect availability and security and meet applicable obligations. Depending on the purpose, the legal basis is Article 6(1)(b), (c) or (f) GDPR. Our legitimate interests include secure and reliable operation and prevention of misuse.

Account access and devices

We process your email address, account identifiers, login requests, protected code/link verification data and associated security records to create accounts, send and verify sign-in messages and prevent misuse. Sign-in uses email rather than a profile password.

Sessions keep you signed in and protect forms and requests. The application’s database session handler does not store the request’s IP address or browser user-agent in the corresponding session metadata fields. Your IP address is still processed when a request is handled, for example by the hosting infrastructure and, in keyed form, by short-lived limits that protect sign-in, referral, campaign and code functions against misuse. This is separate from the visitor estimates described below.

Staying signed in on a device is optional. If you choose “Keep me signed in”, a device cookie named “upbiddr_device” is stored in your browser. It contains an encrypted sign-in token; the service stores only a hash of its secret part, together with your account and the expiry time. The saved sign-in ends 90 days after the sign-in at which you chose it and is not extended by use. A new sign-in in the same browser replaces it. When you sign out in that browser, Upbiddr tries to end the saved sign-in by deleting its server record; if this does not succeed, the saved sign-in can remain valid until it expires. If you only delete the cookie or other site data in your browser, the server record remains until it has expired and is removed by a later cleanup.

During sign-in, the email address you entered is kept in encrypted form in the session of this sign-in so that the code step can show it. It is removed from the session when the sign-in is completed or replaced or when you sign out, and at the latest when a sign-in page is shown after the sign-in can no longer be used. Keeping it does not mean that a message was delivered or that an account exists.

If you still need to agree to the Terms and Rules when you sign in, your confirmed sign-in is held in an intermediate step for up to 10 minutes. This step also keeps a referral, campaign, point action or ranking action, such as Claim #1, that you started, so that it can continue after you agree. This intermediate step does not itself complete sign-in or create a new account. After the 10 minutes the step can no longer be used; this does not by itself delete the related sign-in request, which is removed under the retention rules below.

When you agree, we record your account, the version of the agreed Terms and Rules package and the time of your agreement. No IP address, browser information or device fingerprint is stored with this record. It documents your agreement to the Terms and Rules; it is not consent to advertising or to the processing of your data.

Contractual processing relies on Article 6(1)(b); necessary security, abuse prevention and evidence of agreements rely on Article 6(1)(f), and specific legal record duties on Article 6(1)(c).

Public content, images and visibility

We process the profile/card information and images you submit, such as display name, handle, descriptions, destination links, categories, market information and ranking-related data. We store and technically prepare images for the requested display and sharing features. Public profile and card information, such as a display name, handle, profile address or public ID, can relate to you even if you use a pseudonym. Information about a business or project is personal data only where it relates to an identifiable person.

Public visibility follows the relevant profile, card and moderation settings. Card status and profile visibility are separate. An eligible active card may remain public even when a profile is not publicly listed. Independent search engines and other recipients may copy or cache public information outside our control.

The purposes are to provide the presentation features you request and operate the public platform, based on Article 6(1)(b) and, where applicable, our legitimate interest in maintaining a useful, secure public service under Article 6(1)(f).

Ranking values, points, referrals and favorites

We process account/card references, increases, balances, redemption and reward records, campaign/referral relationships and integrity records to provide the relevant features, prevent duplicate processing and address manipulation. Temporary continuation information may preserve a requested referral, campaign or point action across sign-in.

Favorites link your account with the cards or profiles you select; related aggregate counts may be public. Transaction and feature records are not made public merely because an aggregate count is shown.

The legal bases are performance of the requested service under Article 6(1)(b), necessary integrity and abuse prevention under Article 6(1)(f), and specific legal obligations under Article 6(1)(c).

Payments, invoices and contractual records

Stripe Checkout collects the payment and billing information required for your purchase and automatically generated invoice. This can include your name, billing address, payment details and optional business/tax information. Stripe does not use your public profile name as a substitute for the billing information you enter.

Upbiddr processes account/order/card references, confirmed amounts/currencies, provider references, payment status and records necessary for applying increases, contractual documentation and support. Full payment-card details are handled through Stripe, not entered into your public profile or ranking card. Invoice and payment confirmation are accessible through the account’s My ranking increases area.

We also process the immediate-performance declaration, the applicable text/version, agreement and service timestamps and confirmation records needed for the contract and legal documentation.

The legal bases are Article 6(1)(b) for the contract, Article 6(1)(c) for applicable tax, accounting and consumer duties, and Article 6(1)(f) for necessary security, integrity and legal claims. Stripe’s role varies by activity and it also processes data for its own legal and payment-security purposes under its own privacy information.

International processing by Stripe may involve countries outside the EEA. Applicable contractual and transfer arrangements, including relevant adequacy mechanisms or standard contractual clauses where applicable, govern such processing; this notice does not promise that all Stripe processing remains in Germany. Stripe’s own privacy information, including its information on international transfers, is available on Stripe’s website at stripe.com/privacy.

Display of contributions

Public activity does not disclose your account email. Where you pay to increase another member’s card, its owner may see your public profile name and profile link in the private activity view if your profile is publicly listed and eligible; otherwise a neutral member description is used. This does not expose your invoice name or email through that view.

The purpose is understandable account activity and attribution of contributions to the card owner, based on the requested service and the legitimate interest in transparent transaction activity. You can use a pseudonymous public profile name, but Upbiddr and Stripe still process the data needed for account and payment services.

Visitor estimates and aggregate statistics

Upbiddr estimates how many visitors use its public pages and shows rough public figures, for example estimated visitors in the last 10 minutes or on the current UTC day. These figures are estimates, not exact numbers of people: one person can be counted more than once, for example on different devices or networks, and different people can be counted as one. This measurement does not store anything in your browser, does not read cookies or browser storage and does not create a browsing history or a visitor profile linked to your account.

For an eligible request, the application briefly uses a shortened prefix of your IP address, normalised browser information and technical request headers that show whether the request is an ordinary page view. Together with a key that changes every day, it derives a short-lived value in memory, which is not stored as an individual visitor record. Only compact registers from which counts are estimated are stored on the server, together with the daily key. These registers and the key are treated as pseudonymous data, not as anonymous data. When a day has been closed, only its estimated total remains as a single number for that day; these day totals are anonymous statistics.

The purpose is to understand the overall reach and use of the public pages and to show public visitor figures. The measurement is not used to identify you or to follow you across websites. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is measuring the reach of the service while processing as little data as possible, without cookies, visitor profiles or third-party analytics services. If your browser sends the Global Privacy Control signal, your requests are not counted. You may also object to this processing using our contact details. The measurement does not maintain individual visitor records, which can limit our ability to locate information relating to a particular person. We assess requests individually under the applicable GDPR requirements.

Separately, Upbiddr counts eligible views of ranking cards and profiles and clicks or copies of card links per day, together with lifetime totals. These counters store the card or profile, the day and a number; they do not use your IP address and do not record who viewed or clicked. Card and profile view counting excludes owner views, requests carrying the Global Privacy Control signal and recognised automated requests. Link clicks and copies use the separate session-bound protection described below. Because the figures belong to a specific card or profile, they can relate to its owner and are not anonymous. They can be shown publicly, for example in lists of what is getting attention and in a card’s statistics. These figures help members understand the development of their cards and profiles and help visitors discover and compare public cards and their ranking development. The legal basis is Article 6(1)(f) GDPR, based on our interest in showing understandable activity on the platform.

To limit repeated counting, Upbiddr uses temporary protection records for each card, interaction type and browser session. Verification values are stored as hashes in the database, while the corresponding temporary token is held in the session. A click and a copy can each be counted at most once per card and hour within that session. These records are not anonymous and do not prevent every misuse; the legal basis is also Article 6(1)(f) GDPR. Where shown, the timeline presents aggregate figures and milestones; the time of a milestone is when it was observed, which can be later than the exact moment a threshold was reached. Sessions, hosting data and account or security records are separate processing and do not become anonymous because public figures are aggregated.

Cookies and browser storage for requested functions

Upbiddr sets a session cookie and a request-protection cookie (XSRF-TOKEN) on its pages, including public pages. They keep a session working, protect forms against cross-site requests and are needed for sign-in. The device cookie “upbiddr_device” is set only if you choose “Keep me signed in”. Your browser’s local or session storage can keep a theme you select and temporary navigation or reload state; this information stays on your device and is not sent to Upbiddr. None of these cookies or storage entries is used for the visitor estimates.

X prompt on public pages: if you close the prompt or follow its link “Follow on X”, your browser stores an expiry time in local storage under the name “upbiddr:x-prompt-until” to hide the prompt for 24 hours; if you choose “Don't show again”, the stored expiry time hides the prompt for 30 days. Closing the prompt or following its link does not shorten a longer expiry time. When you open a public page on which the prompt can appear while it is enabled, our script may read this entry in your browser to decide whether to show the prompt; when you close the prompt, follow its link or choose “Don't show again”, it also reads the entry to keep a longer expiry time and to check that the new one was saved. If the entry has expired or is invalid, the script attempts to remove it. If browser storage is unavailable, the entry cannot be checked or removed, and the prompt does not open automatically. The entry contains only this expiry time and no identifier, is not linked to your account and is not transmitted to Upbiddr. It may remain stored after the 24-hour or 30-day period until a later visit removes it or you clear this site’s data. You can remove it by clearing this site’s data in your browser.

You can manage cookies and site storage through your browser. Blocking necessary mechanisms can affect sign-in or requested functions. Where storage/access is strictly necessary to provide a function you explicitly request, we rely on the applicable legal exception; any processing requiring consent must have its own appropriate basis. This notice does not describe all storage as analytics or all storage as automatically exempt.

Contact, reports, complaints and withdrawal messages

We process the contact information, content location, explanation and other information you send, together with necessary related service records, to answer enquiries, assess notices, handle complaints and fulfil withdrawal or other legal duties. Avoid unnecessary sensitive information, passwords or full payment-card details.

Reports can be assessed by the operator and lead to moderation and associated records. Necessary information may be sent to the affected person or a competent authority where required or permitted, subject to protection of confidential or unnecessary personal information.

Depending on the request, processing relies on Article 6(1)(b), (c) or (f). Any statutory withdrawal confirmation and contract confirmation remain service communications, not advertising consent.

Official social-media profiles

Our official Upbiddr social-media profiles are currently Upbiddr on X and Upbiddr on LinkedIn. On these profiles we process the communications and interactions you direct to them, and any information available to us from the platform, for communication and presenting the service. Do not send sensitive account or billing information through public posts; use the contact details for account-specific matters.

X and LinkedIn also process data under their own policies. The relevant roles and any jointly determined processing are assessed for the actual functions used. This notice does not imply that Upbiddr operates X or LinkedIn, that it is responsible for all processing carried out independently by those platforms, or that it replaces their own privacy information.

This notice also covers our processing in connection with every other social-media profile that we operate as an official Upbiddr channel, even if it is not named here; platform-specific information is supplied when relevant. A profile is not official merely because it uses the Upbiddr name. No social plugin, tracking or analytics integration is asserted here.

Recipients and international processing

Recipients may include Keyweb as infrastructure/email provider, Stripe for payments/invoices, the public where you publish information, the intended recipient of a requested communication, necessary professional advisers and competent authorities or courts where legally required. Access is limited to the relevant purposes and lawful basis.

Where providers act on our behalf, processor obligations apply. Where they act independently, their own responsibility and information apply. If personal data is transferred outside the EEA, the applicable requirements and safeguards must be met. Public availability can allow independent access worldwide; that is distinct from assuming all providers process only in Germany.

Retention

We keep personal data only as long as it is needed for its specific purpose, unless a legal retention duty, a pending dispute or the establishment, exercise or defence of legal claims requires longer storage. Different kinds of data have different periods; there is no single period for all data. Some removals and minimisations are carried out in maintenance steps that we start manually, so data that has become due can remain stored until the next such step; we do not promise deletion at an exact time. Manual administration does not extend the applicable retention period or remove our obligation to handle erasure requests and required cleanup without undue delay. The end of a function’s validity is not the same as the removal of the related record.

Account and submitted content data are kept while your account and the requested features are maintained. Accounts are erased by the operator, for example on your request: your profile, public content and access are removed or minimised, and your email address is replaced once no payment matter of yours is still open. Internal account, profile and card references may remain where necessary to preserve the integrity of retained payment, agreement, ranking or moderation records and the relevant historical statistics. Their continued retention is limited to the applicable purpose, legal obligation or necessity for legal claims; keeping an internal reference does not by itself justify retaining unrelated personal information. These references are not anonymous. The handle stays reserved and is not shown publicly. To prevent the same email address from receiving a registration reward again, a keyed fingerprint of it, which does not contain the readable address, is kept until the end of the third calendar year after the year of erasure.

Sign-in requests can be removed seven days after their last change once they can no longer be used; they are removed when a new sign-in is requested for the same address or in a maintenance step. A saved device sign-in ends after 90 days; its server record is deleted when you sign out in that browser and this succeeds, when you sign in there again, or after expiry during a later cleanup. A protection token for counting clicks and copies is valid only for a short time, and a counted click or copy blocks repeated counting of the same type for an hour; the protection records in the database are then removed in limited steps during later interactions, so they can remain stored longer. The token held in the session is stored with the session data. Session records are removed by the regular session cleanup after the session has expired.

For visitor estimates, minute registers are kept until the first eligible request after their ten-minute window. The day registers and the daily key of a day are kept until that day is closed by an eligible request on the following UTC day; otherwise they remain until they are removed manually. Closed day totals are kept as anonymous figures. Daily view and interaction counts of cards and profiles are needed for 35 days and are then removed in limited steps when new counts of the same kind are written, so they can remain longer. Lifetime totals support the historical statistics of the relevant card or profile. Where they remain linked to an identifiable person, their retention is subject to the purpose and legal-claim criteria described in this section. Anonymous aggregate figures may be retained independently.

Invoices and accounting vouchers are kept for eight years, commercial and business correspondence for six years, and certain accounting records, such as books and annual financial statements, for ten years. These periods generally begin at the end of the calendar year determined by the applicable rule, for example the year of receipt, dispatch or creation of the relevant record, and can be longer where the law extends them, for example while a tax assessment period has not yet ended. They apply only to records covered by the relevant duty. Other payment, order and immediate-performance records and agreement records for the Terms and Rules are kept as long as they are needed as evidence of the contract or for legal claims; the relevant limitation period is assessed for the specific record.

An open content report that is not finished within 90 days is deleted, including the reference to the reporting account. A finished report is kept for twelve months after its final decision and is then deleted. If a report led to a measure, a minimal record without reference to a person, the report or its target remains for a further twelve months after that deletion. Withdrawal declarations and the related customer messages are kept for six years from the end of the calendar year in which they were received or sent; they are then minimised by removing the personal details they contain, and a pseudonymous case record remains. Cases that cannot be reliably assigned to a purchase, and internal notes or decision reasons not covered by this minimisation step, are assessed separately. They are retained only where necessary to handle the case, fulfil an applicable legal obligation or establish, exercise or defend legal claims.

Backups of Upbiddr’s data are kept on a rolling basis for up to 30 days so that the service and its data can be restored after errors, data loss or security incidents. Data removed from the live service can remain in a backup until that backup reaches the end of this period. Server, web-server and database logs of the hosting environment are separate from backups and from the visitor estimates; they can contain IP addresses, requested addresses, browser information, times or database changes. They are used for operation, security, troubleshooting and recovery and are kept only as long as needed for these purposes under the hosting and server settings.

You may request erasure or other rights through the contact details below; any legal retention exception is assessed for the specific data. A missing self-service deletion button does not remove statutory rights.

Your rights

Subject to the conditions of applicable law, you may request access, correction, erasure, restriction and data portability, and object to processing based on legitimate interests. Where processing is based on consent, you may withdraw it without affecting the lawfulness of earlier processing. You may complain to a competent data-protection supervisory authority.

Send requests to contact@upbiddr.com. We may request information reasonably necessary to verify your request and protect other people’s data, but do not require unrelated information. We assess requests and any lawful exceptions individually.

Age and updates

Account and paid-service use is intended for people aged 18 or above. Do not submit special-category personal information, identity documents, payment-card details or other unnecessary sensitive information into public fields.

We update this notice when relevant processing or information changes and provide any legally required additional notice.

Version: 2026-11-01
Effective date: 1 November 2026