Legal
Privacy policy
Information on the processing of personal data pursuant to Art. 13 GDPR.
Last updated: October 29, 2026
This English version is provided for convenience only. The German version is the legally binding one — in case of any discrepancy, the German text prevails.
In short
This website sets exactly one cookie that requires consent: the one that credits a referral — and only if you agree to it. Opening a page contacts no third party: no embedded outside services, no external fonts, no analytics or tracking tool. Some features do pass data outward — for example the AI assistant, online payment, notifications to our team and our team's calendars; each has its own section below. We ask you on your first visit and record your answer in a single cookie — otherwise the same question would return on every page view. It holds nothing but your decision and a version number.
We process personal data only when you actively approach us: through the contact form, through the project inquiry with its appointment booking, through the partner application form, or by email. In addition, technically necessary server logs are generated when the site is accessed, as with any website.
If you arrive through a partner's referral link, their code sits in the address bar and is stored along with any form you submit. Something is placed on your device for that only if you have consented to the “Referral” category — see “Partner program and referral code”.
Controller
The controller for data processing on this website is:
- Company
- Awelior LLC
- Address
- 30 N Gould St, Ste R Sheridan, Wyoming 82801 United States
- contact@awelior.net
Hosting
This website is hosted with an external service provider. Personal data collected on this website is stored on that provider's servers.
The provider is used in the interest of secure, fast and reliable delivery of our offering (Art. 6 (1) (f) GDPR). A data processing agreement pursuant to Art. 28 GDPR is in place with the provider.
In addition, we back up the data daily, encrypted, to separate off-site storage (Hetzner Online GmbH, European Union). Backups are kept on a tiered schedule for up to seven years so that statutory retention duties are met and data can be restored after a failure.
For users from Uzbekistan: your personal data is stored on servers in Finland (European Union). Under Resolution No. 415 of 29.07.2026, Finland is among the countries that ensure adequate protection of personal data. Awelior LLC, based in the USA, accesses this data on the basis of your consent under Art. 15 of the Law of the Republic of Uzbekistan “On Personal Data” No. ZRU-547 or on the basis of standard contractual clauses. We do not process biometric or genetic data of persons from Uzbekistan, which under Art. 27¹ of that law may only be processed in Uzbekistan.
We ask for this consent wherever we collect your data — contact form, project request with appointment, registration, chat with Robora, Telegram and WhatsApp — before storing anything, and record the wording, version, language and time. Without consent we do not store your details. You can withdraw it at any time, in your customer account under “Profile” or informally by e-mail; withdrawal applies to the future. The same applies to other countries whose law requires such consent.
Server log files
When this website is accessed, the host automatically collects information transmitted by your browser. This comprises:
This data is not merged with other data sources. Collection takes place on the basis of Art. 6 (1) (f) GDPR; we have a legitimate interest in the technically error-free presentation and security of our website.
Retention period: 14 Tage.
- browser type and version
- operating system used
- referrer URL
- hostname of the accessing device
- time of the server request
- IP address
Contact form
If you send us inquiries via the contact form, the details you provide there — including the contact data you enter — are stored by us for the purpose of processing the inquiry and in case of follow-up questions.
The inquiry is additionally stored as a file on our server and sent to us by email. You receive an automatic acknowledgement at the email address you provided.
To protect against automated submissions we use an additional field invisible to you as well as a check of how long the form took to complete. For this we also store, with each inquiry, your browser identification (which your browser sends of its own accord) and the time between opening and submitting the form. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest is fending off automated bulk submissions. Both are held in the same file as the inquiry, are not passed to third parties, and are deleted together with it.
The legal basis is Art. 6 (1) (b) GDPR where your inquiry relates to the initiation of a contract. In all other cases processing is based on our legitimate interest in effectively handling inquiries addressed to us (Art. 6 (1) (f) GDPR).
For processing purposes we record internally what stage your inquiry is at (for example "answered" or "quote sent") and add a note where needed. These records are visible only to us, serve solely to process the inquiry and are deleted together with it.
There are countries from which we may not accept engagements, for example because of sanctions. If you enter such a country as your location in one of our forms, we do not accept the request and do not store it. We only count how many such requests there were per day, country and form — without name, address, IP address or any other link to you. Only the country you enter matters, not the language in which you use the website. Visiting the page still produces only the usual server log files.
Retention period: we keep the data until you ask us to delete it, withdraw your consent or the purpose ceases to apply — at the latest after 24 months. Mandatory statutory retention periods remain unaffected.
- subject (website, app, automation, AI agent, phone assistant or not sure)
- your message
- budget range (voluntary)
- name
- email address
- phone number (voluntary)
Project inquiry, attachments, and appointment booking
In the project inquiry you answer questions about your project, can attach files, and choose at the end whether to book a call right away or send the inquiry without an appointment. You then see a non-binding indicative price. The following data is processed:
- type of project, starting point, desired features and integrations
- scope (such as the number of pages or workflows), project languages and time frame
- if you book an appointment: date and time of the call as well as the language of the call
- name, email address, company, phone number, and country (required)
- voluntarily: your notes and attached files (documents, images, sketches, PDFs, voice memos)
Your details are stored on our own server: the answers as a file, the appointment in a database on the same server. No third-party booking service and no third-party calendar is involved. Your appointment may, however, appear in the calendar of the person who holds the conversation with you — what is passed to their calendar provider is described in the section "Appointments in our team's calendars".
We check attached files by their content when you upload them and store them on our own server outside the publicly accessible area, under a random name. We re-save images without metadata — the location (GPS) and camera data are removed. Only our team members authorized for inquiries have access. Files you upload but do not send with an inquiry are deleted automatically after 48 hours at the latest; attached files are deleted together with the inquiry. So you lose nothing if the page reloads, your browser keeps your answers locally on your device until you submit (local storage, 20 hours at most); none of it reaches us before you submit. If you book an appointment, you receive the confirmation with a calendar file (.ics).
On the day before the call you receive a single reminder by email stating the date, the time and how to cancel. You do not receive any further automated messages; in particular we send no newsletter and no advertising.
The legal basis is Art. 6 (1) (b) GDPR where your inquiry relates to the initiation of a contract, otherwise our legitimate interest in handling your inquiry (Art. 6 (1) (f) GDPR). The same basis covers the reminder for an appointment you booked yourself — it is part of carrying out the agreed call.
Retention period: as for the contact form, at most 24 months. After that the inquiry, the appointment and the internal notes are deleted.
Appointments in our team's calendars
People who hold appointments for us can add them to their own calendar through a private link. If your appointment is among them, it shows your name, your company if given, the date, the time and the language of the conversation — no email address, no phone number, no message and no notes.
Anyone who works with us — in the admin area, in the staff portal or as a partner — can generate a personal calendar link in ICS format for their own appointments and subscribe to it in a calendar app of their choice. The link contains a token of 32 random bytes; we store only a hash of it (SHA-256) and show the link exactly once. Anyone using a wrong or invalid token receives nothing but a "not found" response.
The calendar contains only appointments assigned to that person. For a conversation booked with you, that means: your name and, if given, your company as the title, the date and time, the language of the conversation, and a link into our admin area that reveals nothing without signing in. Your email address, your phone number, your message and our internal notes are not included. The calendar also contains internal tasks and deadlines as well as the person's own time off. Entries more than 30 days in the past drop out; a canceled appointment is shown as canceled.
The link is not fetched by us but by the calendar provider of the person concerned — for example Google, Apple or Microsoft — from that provider's servers and at intervals the provider determines. The entries then sit in that person's calendar account with that provider, which to that extent receives your details. These providers also process data outside the EU and the EEA, in particular in the United States. Which provider a person uses is their own choice. All we store is when the link was last fetched and how often; each fetch also produces the usual server log files.
In addition, team members can create their own calendar entries in the admin area and link them to a record, such as an inquiry, an order or a project; the title may then name you or your company. Instead of a subscription, a person can also connect a calendar of their own via CalDAV. We then send their entries to that calendar provider ourselves — in one direction only: we never read anything back from that calendar and import nothing. Participants appear there only as names of team members in the description, never as an email invitation. If the person deletes an entry, we remove it there as well; if they disconnect, entries already transferred stay in their account with that provider until they delete them there. We store the access details of this connection encrypted. The same legal basis and the same notes on providers apply as for the subscription.
A person can also connect their Google Calendar (Google LLC, USA; in the EEA Google Ireland Limited) or their Microsoft 365 or Outlook calendar (Microsoft Corporation, USA; in the EEA Microsoft Ireland Operations Limited). They sign in with the provider themselves and allow us to write entries to their calendar; for this we store only an access token from the provider, encrypted, and the address of the connected account. We transfer the title, time, location, online link and description of that person’s entries — the title may name you or your company. Here too it is one-way only: we do not read any appointments from that calendar; we only write and delete our own entries. Both providers also process data in the United States and are certified under the EU-U.S. Data Privacy Framework. If the person disconnects or revokes the permission with the provider, the transfer ends; entries already transferred stay in their account until they delete them there. The legal basis and the right to object are the same as for the subscription.
The legal basis for your details is our legitimate interest in making sure an appointment agreed with you is kept reliably (Art. 6(1)(f) GDPR). We have therefore limited the content to what is needed to be in the right conversation at the right time; all further details stay behind the sign-in to our admin area. You may object to this processing under Art. 21 GDPR; an informal message is sufficient.
The person can generate a new link at any time — the old one then stops working immediately — or switch the subscription off entirely. An invalid link no longer delivers any appointments. When the calendar provider removes entries it has already imported depends on its own rules; we have no access to that.
Partner program and referral code
We only set a cookie to credit a referral if you have consented to the “Referral” category in the consent notice. Without your consent the code exists only in the address bar.
Third parties may recommend us and receive a referral code for doing so. When someone opens a page through such a link, the code appears as a parameter in the address bar (for example /en/project?partner=example-code). When a form is submitted, it is stored together with your inquiry so that we can attribute the recommendation.
Since 22 September 2026 there is also an attribution cookie: it is called __Host-awelior_referral, expires after 30 days and contains the partner code and, where applicable, a campaign label — no identifier that would allow a person to be recognized. It is set ONLY if you have consented to the “Referral” category in the consent notice; the legal basis is your consent under § 25(1) TDDDG and Art. 6(1)(a) GDPR. You can withdraw it at any time via the consent notice.
Without consent things stay as before: the code exists only in the address bar, and anyone who leaves the site and returns without the link arrives without attribution. That is the weaker but more data-frugal attribution — and it remains the default.
When someone opens a partner’s promotional link, we count the click: we store the day, the partner code, a campaign label and a number. No IP address, no device identifier, no time of day. That shows which poster works, but identifies no one.
The form visibly states that a recommendation is attached. You can remove it there with one click; the parameter then disappears from the address bar and is not transmitted.
The partner who referred you or looks after you receives from us your name and the basic details needed to look after you — and exactly these: in their partner account and as a notification (by push if they wish), they learn that an inquiry has come in through their link or code, with the name you provided; that a quote has been accepted, with the quote number and your name; that an order has been created, with its title and total; and that a payment has been received, with the amount and the invoice description. If they have set up a calendar subscription, it shows the appointments with you: your name, your company if given, the date, the time and the language of the conversation. In their overview they see, for each referral, the date it came in, its status and whether it has been paid in full. If they registered you with us themselves through the partner account, they continue to see the details they entered there and whether the quote was confirmed. They do not receive your email address or phone number, the content of your inquiry, our internal notes or access to our admin area. The legal basis is Art. 6(1)(b) GDPR where the partner takes part in preparing or performing your engagement, and otherwise our legitimate interest in your partner looking after you and in settling their share (Art. 6(1)(f) GDPR). You may object under Art. 21 GDPR.
The presentation mode at /en/partners/presentation is a display page only. A partner can enter their own code there so that the onward links carry it; nothing is stored on the device for that either. No input is transmitted, and it is not recorded how long or how often the page was viewed. In the application we also process first and last name (Latin script and own script), date of birth, country of residence and city, and, voluntarily, street, house number, postal code and links to social media profiles. The purposes are verifying identity and the minimum age of 18, concluding the contract and tax obligations (Art. 6(1)(b) and (c) GDPR).
If someone applies as a partner through the form at /en/partners, we process their name and email address as well as the company, website and description of how they intend to recommend us, where given voluntarily. The legal basis is Art. 6 (1) (b) GDPR (initiation and performance of the partner agreement). These data remain stored for as long as the cooperation lasts; once it has ended or did not come about, we generally delete them after a waiting period of up to 24 months, unless a statutory retention period applies.
Directory of certified partners, badge and certificate
A partner appears in the public partner directory only with their express consent, which they can withdraw at any time in the partner account. We never publish their email address.
Partners can choose to be shown publicly as a certified partner on the page /partners/certified. We then publish the company or name, the profile picture, city, country, website, languages, industries, a short description and the program; the partner level only if we expressly enable it. The legal basis is the partner’s consent (Art. 6(1)(a) GDPR), given in the application or in the partner account. When consent is withdrawn, the entry disappears immediately; publication up to that point remains lawful.
Anyone who contacts a partner through the directory writes into a form on our website. We forward the name, email address, optionally the company and the message by email to the address of the partner account and do not store the message ourselves. The legal basis is establishing the requested contact (Art. 6(1)(b) GDPR) and our legitimate interest in a contact route protected against abuse (Art. 6(1)(f) GDPR); to prevent abuse we briefly count requests per origin without storing them. The partner is responsible for any further processing.
Every approved partner receives a certificate with number, level and date. Using the number, anyone can check at the verification address whether the certificate is valid, and see the name or company, program, level and date of issue. The embeddable badge contains only level and number; it is available only while the partner has switched it on. When an embedded badge is loaded, we receive the usual connection data of the browser (see server log files) but set no cookies.
Tax forms and tax documents (partners, staff, contractors)
As a US company we need a US tax form for payments to partners, staff and contractors: W-8BEN (individuals outside the US), W-8BEN-E (entities outside the US) or W-9 (US persons). You enter the details yourself in the partner account or staff portal: name, country, permanent address, type of entity where applicable, taxpayer identification number, and the date and name of the signature.
We store taxpayer identification numbers in encrypted form only; only the last four characters are shown. The system reads them in plain text only for the file our tax advisor needs for US reporting (Form 1099-NEC) — and only for persons with a W-9 whose payments reach the statutory threshold. Access is limited to persons with the dedicated permission, by default management.
The purpose is to meet tax obligations and to settle accounts with you (Art. 6(1)(b) and (c) GDPR, where it applies). From our documents we create an annual and quarterly summary for you; it contains no data of your customers. We keep the details for as long as tax retention periods require; a replaced form is kept as evidence.
Ads on Meta, TikTok and Google
We run ads on Meta (Facebook, Instagram), TikTok and Google Search. No pixel, tag or other script from these providers is embedded on our website, and we do not pass any personal data to them. If you arrive through an ad and send us an inquiry, the only thing we store about it is a campaign code.
Our ads lead to pages on this website. The destination address carries a campaign code of the form “ads-” plus eight characters as a parameter in the address bar (for example /en/project?campaign=ads-1a2b3c4d), together with the usual utm_source, utm_medium and utm_campaign parameters, which only name the platform, the type of ad and the campaign. If you send an inquiry through the contact form, the project inquiry or the website assistant while the code is in the address bar, it is stored together with your inquiry. We do not evaluate the utm parameters and do not store them separately.
The sole purpose is to see which ad leads to inquiries and orders and to steer budget and campaigns accordingly. The evaluation is only a count: per campaign, the number of inquiries and orders and, from that, the cost per inquiry. The legal basis is our legitimate interest in managing our advertising economically (Art. 6(1)(f) GDPR). You may object to this processing under Art. 21 GDPR; an informal message is enough. If you do not want to transmit the code at all, remove the parameter from the address bar before sending.
We set no cookie for this and store nothing on your device: the code is only read while it is in the address bar. Consent under § 25 TDDDG is therefore not required. Anyone who leaves the page and returns without the link arrives without a code. The attribution cookie described in the section “Partner program and referral code” only arises from links with a partner code — our ad links carry none.
No sharing with the ad platforms: neither the Meta pixel nor the TikTok pixel nor any Google tag (Google Ads, Google Analytics, Google Tag Manager) is embedded on our website, and we do not send the platforms any data about visitors, inquiries or customers — no encrypted or hashed email addresses or phone numbers, no customer lists and no report that a click turned into an inquiry. We choose the audience solely through attributes the platform itself offers, such as country, language, age, interests or search terms. From the platforms we receive only aggregated figures per campaign and day — impressions, clicks, costs and, where applicable, results counted by the platform itself — with no link to individual people.
When you click an ad, the platform may append its own click identifier to the destination address (for example gclid, fbclid or ttclid). We do not read it and do not store it. What happens when you view or click an ad on Facebook, Instagram, TikTok or in Google Search itself is governed by the respective provider’s privacy notice; you manage your ad preferences in your account there. On our website, opening a page only creates the usual server log files.
Retention: the code shares the fate of your inquiry and is deleted with it — as with the contact form, after 24 months at the latest; if the inquiry becomes an order, the periods stated for orders apply. The aggregated campaign figures and costs contain no personal data and remain stored for our bookkeeping.
Project status for clients
Anyone holding the link we sent can see the status of the project concerned — there is no sign-in. Here too, no cookie is set and nothing is stored on your device. You can have the link revoked at any time.
Once you have commissioned us, we set up a page at /order on request where you can check the status of your project. The address contains an access token of 32 random bytes which we send to you once. There is no account, no password and no session for it — so there is nothing for you to create, remember or have reset.
What is shown is only this: the name of the project, its state, the date it was commissioned, any planned completion date, the agreed stages with their state and due dates, and the time of the last change. What is not shown: the project fee, internal notes, the internal history, the names of the people working on it, internal identifiers and your contact details. The legal basis is Art. 6 (1) (b) GDPR (performance of the contract).
No information on your device is accessed in the process: for this page we store neither a cookie nor data in your browser's local or session storage. Consent under section 25 TDDDG is therefore not required. It is the same construction as the referral code — the token sits in the address bar and nowhere else.
Because there is no sign-in, anyone in possession of the link can view the status shown there. Please do not pass it on. With 32 random bytes the token cannot be guessed; should a link nevertheless end up in the wrong hands or become obsolete, we will revoke it on your word and send you a new one. A revoked link then produces exactly the same response as a made-up address.
The page is barred from search engines: it carries the instruction "noindex, nofollow", appears in no sitemap and is excluded from retrieval in our robots.txt. Opening it produces the usual server log files described in the corresponding section.
The project data remain stored for as long as the project runs, and beyond that within the retention period for the underlying inquiry; if that inquiry is deleted, the project including its stages and its access link goes with it. Further detail on periods and on your rights is set out in the sections "Contact form" and "Your rights".
Customer account
A customer account is optional. The previous route — the link under /order — continues to work unchanged, with or without an account. If you delete your account, your projects remain reachable through that link.
If you register for a customer account, we store your email address, a password hash (not a readable password — more on that below) and the name you provide when creating it. We also record when you last signed in, and per session technical details such as your browser's identifier, so that a sign-in can remain valid for up to 30 days without you having to sign in again during that time.
If you register yourself, the account is created only when you click the link in our confirmation email. Until then we keep a registration request: your email address, your name, the hash of your password, the order link you wanted to connect if any, and the time created and expiry time; we store the link only as a hash. It is valid for 48 hours. When you click it, the request becomes your account and is deleted; an expired request is deleted the next time anyone requests a registration, as is an older request for the same address. If an account already exists for the address, we create nothing and instead write to that address that an account already exists there. The legal basis is Art. 6(1)(b) GDPR.
We can also create a customer account for you — for example so that you can see the status of your project or a preview of your website. In that case we enter your name, your email address, your language and, where applicable, the link to your company, and our system generates a starting password. Like every password, it is stored only as a hash; the person creating the account sees it exactly once so they can pass it on to you if needed. You first receive an email with a link to confirm your address; it is valid for seven days and can be used only once, and we store it only as a hash. Until you confirm, the starting password is kept encrypted on our side; that copy is deleted when your sign-in details are sent after confirmation, and at the latest when the link expires after seven days. As long as you have not changed the starting password, your account asks you to do so. If we correct your email address while the account is not yet in use, we record who changed it, when, and from which address to which, and send a new confirmation link to the new address. We automatically delete this history after one year. The legal basis is Art. 6(1)(b) GDPR.
Once your account is in use, our team does not change your password or email address directly. If you have forgotten your password, the team can send you a reset link; it never sees the link or the new password. A new email address takes effect only when you confirm the link we send to the new address (valid for seven days); the previous address receives a notice about it. We record these events — reset link sent, address change requested and confirmed — with the time and the person acting, without links or passwords; we delete these entries, like the address history, after one year, and pending address changes when they expire. If you change your password yourself, all other signed-in sessions of your account end. The legal basis is Art. 6(1)(b) GDPR, and for recording the events our legitimate interest in the security of your account (Art. 6(1)(f) GDPR).
We do NOT store your password in plain text, but as a hash (scrypt) with its own random salt — the same method that also protects sign-in to our administration area. The password cannot be recovered from the stored value.
Through your account, you can link an existing project link (see the section "Project status for clients") to your account to see several projects in one place. What is shown is exactly the same information the individual link already shows — title, status, dates, stages and the status of any recorded payments; not the project total, internal notes, the internal history or staff names.
We temporarily count failed sign-in attempts to detect and block automated password guessing; for this, the email address used is recorded in plain text as the identifier. This record serves solely to protect your account against automated password guessing and is not linked to any other use of your address. The legal basis for this is our legitimate interest in the security of accounts (Art. 6(1)(f) GDPR); the count itself lapses after 15 minutes and is not kept separately. For creating, maintaining and linking the account otherwise, the legal basis is Art. 6(1)(b) GDPR (performance or initiation of the contractual relationship).
You can reset a forgotten password using a link we send you by email; it is valid for one hour and can only be used once. When resetting, we sign out all existing sessions of your account — on every device where you were signed in at that time.
You can delete your account yourself at any time under "My account". Doing so deactivates the account and removes the link to your projects — the projects themselves remain and stay reachable through the individual link you already have. Retention period: the account record itself is NOT removed from our database — "deleting" here means deactivating it and detaching it from your projects, not removing the row. As a direct consequence, the same email address can never be used again afterwards to register a new account.
A customer account is never a requirement: the previous route via /order/<access token> continues to work unchanged and without any sign-in. More on that is in the section "Project status for clients".
Support access to your customer account
Our support team sees your customer account only if you have authorized it beforehand — for a limited time, read-only, and with a log you can view yourself. You can revoke the authorization at any time; it then ends immediately.
If you need help, our support team may need to see what you see in your account. That happens only with your authorization at /account/support-access: for one hour, 24 hours or seven days, tied to a specific ticket if you wish. If our team asks for it on its own initiative, you receive an email with the name of the person asking and the reason; you can approve or decline only in your account.
While the authorization is active, team members with the corresponding permission — the owner, managers and support — can open a view of your account, and only by stating a reason. They see what you see: your name, your customer number and email address, your orders with the status of their payments, your tickets with the messages as they are shown to you, and the ideas you have submitted. The view is read-only: nobody can change anything in it, write in your name, download files or take over your sign-in, and nothing is stored on your device for it. An opened view is valid for at most eight hours and ends immediately when the authorization expires or you revoke it.
Every opening and every change of page within the view is logged: the time, the team member's name, the stated reason, the ticket if any, and the area viewed. You can see this log yourself in your account at the same address; within our team, the owner sees it. We also store your authorizations (start, end, revocation) and our team's requests with their reason.
The legal basis is Art. 6(1)(b) GDPR: the help in question is part of the services of your customer account, and in some cases it cannot be provided without this view. Your authorization is not consent within the meaning of Art. 6(1)(a) GDPR but the condition we have set for ourselves: without it there is no access. We keep the log under Art. 6(1)(f) GDPR; our legitimate interest — and yours — is to be able to trace every access and detect any misuse.
Retention period: we automatically delete log entries, authorizations and requests after one year. On request, we will review earlier erasure under Art. 17 GDPR.
For every account we keep an internal record with a history that cannot be changed afterwards: sign-ins (time, web or app, a rough device label such as “Chrome · Windows”, no IP address), actions our support takes on your account with a reason (for example a password reset link sent, a lock, ending all sessions) and internal notes and closing notes on your tickets and chats. The purpose is the security of your account and proof of who did what and when (legitimate interest). Only owners, managers and support may view it. When our support intervenes in your account (lock, unlock, ending all sessions, resetting two-factor sign-in), you receive an email. Entries are deleted after six years.
Preview of your website
If we build your website, you can view it before launch at its own address <name>.awelior.com — after signing in to your customer account and only if you are authorized. For this, the preview address sets its own strictly necessary cookie.
While we work on your website, we publish the current state as a preview at its own subaddress of awelior.com, on our own server with the host named above. We keep at most the three most recently uploaded versions and record who uploaded which version and when.
Access is limited to the customer accounts linked to the project or that you additionally name to us, and to team members with the corresponding permission. On every single request our server checks again whether the person is still authorized, so a withdrawn access takes effect within about half a minute at most. For customer accounts there is also a display period that we set and can extend; after it ends, the preview is no longer available to them. The preview is blocked for search engines.
How signing in works: you sign in to your customer account on awelior.com and open the preview at /account/previews. awelior.com then issues a one-time handover valid for two minutes, which the preview address exchanges for its own cookie named awelior_vorschau. It is valid for twelve hours, only for that exact preview address, cannot be read by the page's scripts (HttpOnly) and contains nothing but a random token, which we store only as a hash. Your sign-in on awelior.com never leaves awelior.com.
When you open a preview, our server determines the country from your IP address on every request and passes only that — as a country code such as "DE" — to the preview, so the future website can choose its language accordingly; this applies to previews that run as their own application. For this we use a database on our own server (IP Geolocation by DB-IP, db-ip.com, CC BY 4.0), which we update once a month without any visitor data. Your IP address is not passed to anyone, and neither it nor the country is stored for this purpose; only the usual server log files arise. The legal basis is our legitimate interest in showing the preview the way the finished website will behave (Art. 6(1)(f) GDPR).
The cookie is strictly necessary for you to view the preview you have expressly requested; under § 25(2) no. 2 TDDDG no consent is required. The legal basis for the processing is Art. 6(1)(b) GDPR (performance of the contract). Each request produces the usual server log files.
For acceptance, we provide in your customer account instructions and the logins for your preview — for example for its admin area: a label, the path on the preview, the username, the password and a note. We store the password in encrypted form; the other details are not encrypted. It is shown only on an explicit click, and we record every display — which login, by whom, when — whether by our team or by you. Our team can see this log; on request we will share it with you. When we add something new, we notify you by email and in your customer account; the email contains no login details. The instructions, logins and log have no separate deletion period: they are deleted together with the preview. The legal basis is Art. 6(1)(b) GDPR, and for the log our legitimate interest in traceability (Art. 6(1)(f) GDPR).
What the preview itself contains — such as forms or features of your future website — is part of our engagement and agreed with you; we add no analytics or advertising services. When a preview is deleted, we remove its files from the server.
Tasks and notifications in your account
In the customer account, the partner account and the staff portal you see the tasks assigned to you. You receive browser notifications only if you explicitly turn them on.
As part of a project or engagement we may assign tasks to you — for clients, for example, "deliver logo". For this we process the title, note, priority, due date, status, the link to the project or order, who created the task and who is responsible, as well as comments with at most one file each (PDF, image or Office file, up to 10 MB) and your report that the task is done. Clients see only tasks relating to their own orders. The legal basis is Art. 6(1)(b) GDPR (performance of the project or of our working relationship).
Retention period: there is no fixed period. A task remains stored until our team deletes it; its comments and files are deleted with it. Tasks attached to a company or contact are deleted together with that record.
On assignment, a new comment, a done report and before the due date, we notify those involved — in your account's list, by email and, if turned on, in the browser. You choose which of these channels you want in your account; for this we store your choice and the language in which you last used the account.
Browser notifications (web push) are available only if you click "Allow notifications" in your account and your browser agrees. We then store your browser's subscription — the delivery address at your browser maker's push service and the associated keys — and the time. Delivery goes through that push service (for example from Google, Mozilla, Apple or Microsoft, including outside the EU); the content is encrypted under RFC 8291, so the service sees only the time and the size. This applies equally to the customer account, partner account, staff portal and admin area. You can turn it off at any time in your account or in your browser settings; we delete a subscription that the push service reports as invalid, and all subscriptions of an account that is deleted or locked. The legal basis is Art. 6(1)(b) GDPR.
Payment link for clients
We note against your payment link whether the stated payment has reached us ('Open' / 'Paid on …'). For a bank transfer we enter this by hand, after we have confirmed the payment in our own account. If you pay online, the button on this page takes you to Stripe, PayPal or BitPay, and the note is then set by the payment confirmed by that provider. We never see or store your card or account details or your wallet details — they are entered with that provider only.
If a payment is due on your order, we set up a page at /payment on request where you can check the description, amount, reference and our bank details. The address contains an access token of 32 random bytes which we send to you once. There is no account, no password and no session for it — the same construction as the project status for clients.
What is shown is only this: the description of the payment, the amount, the reference, any due date, and the status. What is not shown: internal notes, the internal history, the names of the people working on it, internal identifiers and your contact details. The legal basis is Art. 6 (1) (b) GDPR (performance of the contract).
The status is deliberately kept simple: "Open" or "Paid on …", nothing in between. You can transfer the amount — then this page is the digital equivalent of a transfer slip with a handwritten note on whether it has been settled. If online payment is set up, there is additionally a button next to it that takes you to our payment provider; what happens there is described in the next paragraph.
For online payment we use Stripe (Stripe, Inc., 510 Townsend Street, San Francisco, CA 94103, USA; for data subjects in the EU: Stripe Payments Europe Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland). If you click the button, a link takes you to a form hosted by Stripe. **Your card details never reach our server** — you enter them directly with Stripe. We transmit the amount, the currency, the payment reference and the payment number; Stripe reports back whether it succeeded. The basis is performance of the contract (Art. 6(1)(b) GDPR). Stripe acts in two roles: as our processor for the settlement (Art. 28 GDPR), and as an independent controller for its own regulatory duties such as anti-money-laundering and fraud prevention. For that second part Stripe’s own privacy policy at stripe.com/privacy applies, and we have no influence over it. A transfer to the United States may occur. As long as online payment is not set up, this button is not shown and nothing is transmitted to Stripe.
For invoices in euros or US dollars you can also pay with PayPal. For data subjects in the EU the provider is PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg; otherwise it is PayPal, Inc., 2211 North First Street, San Jose, CA 95131, USA. If you click “Pay with PayPal”, a link takes you to PayPal, where you sign in and confirm the payment. **Your PayPal login details never reach our server.** We transmit only the invoice number, the amount, the currency, an internal identifier of the payment, the language of the page and the address PayPal sends you back to afterwards; PayPal reports back whether the payment is complete. Of this, we store only the identifier of the payment at PayPal, which we need for a later refund; we do not store the name or email address PayPal returns with it. The basis is performance of the contract (Art. 6(1)(b) GDPR). PayPal itself is responsible for the processing in your PayPal account; PayPal’s own privacy statement applies, and we have no influence over it. A transfer to the United States may occur. As long as PayPal is not set up, this button is not shown and nothing is transmitted to PayPal.
**Paying with cryptocurrency via BitPay.** For single invoices and installments in euros or US dollars, we may additionally offer payment with cryptocurrencies (such as Bitcoin, Ethereum or stablecoins like USDC and USDT); this option is not available for subscriptions. The provider is BitPay, Inc., 1870 The Exchange SE, Ste 220, PMB 91017, Atlanta, GA 30339-2171, USA. If you click “Pay with crypto”, a link takes you to a BitPay payment page, which is valid for about 15 minutes. We transmit only the amount, the currency, an internal identifier of the payment, the invoice number and the addresses to which BitPay returns you afterward and reports the status to us — no name and no email address. From BitPay we store only the identifier of the BitPay invoice, its status, amount and currency; they are kept like the other payment data (retention periods below). The purpose is to process the payment you chose; the legal basis is Art. 6(1)(b) GDPR. BitPay itself is responsible for what you enter on the payment page or what arises there (such as your email address, wallet address, IP address and device data) and for processing for its own legal obligations (such as identity, anti-money-laundering and sanctions checks); BitPay’s own privacy policy applies (bitpay.com/legal/privacy; for data subjects in the EEA, the EU notice at bitpay.com/about/privacy-eu, which names BitPay B.V., Keizersgracht 520H, 1017 EK Amsterdam, Netherlands, as controller), and we have no influence over it. Our transmission to BitPay goes to the United States. It is not covered by an adequacy decision: BitPay’s privacy notices do not state participation in the EU-U.S. Data Privacy Framework. The transfer is therefore based on Art. 49(1)(b) GDPR — it is necessary for the payment you chose — and, where the contract is with your company, on Art. 49(1)(c) GDPR. If you do not want this, you can pay by bank transfer or another method offered at any time. How conversion, network fees and refunds work for a crypto payment is set out in the contract terms; in short, the invoice amount remains decisive, and the invoice counts as paid once BitPay confirms the payment. As long as BitPay is not set up and enabled, the button is not shown and nothing is transmitted to BitPay.
No information on your device is accessed in the process: for this page we store neither a cookie nor data in your browser's local or session storage. Consent under section 25 TDDDG is therefore not required. It is the same construction as the project status for clients — the token sits in the address bar and nowhere else.
Because there is no sign-in, anyone in possession of the link can view the details shown there. Please do not pass it on. With 32 random bytes the token cannot be guessed; should a link nevertheless end up in the wrong hands or become obsolete, we will revoke it on your word and send you a new one. A revoked link then produces exactly the same response as a made-up address.
The page is barred from search engines: it carries the instruction "noindex, nofollow", appears in no sitemap and is excluded from retrieval in our robots.txt. Opening it produces the usual server log files described in the corresponding section.
The payment data remain stored for as long as the underlying order exists. Beyond that, we keep invoices and their correction documents for seven years, and for ten years for clients whose seat or residence is in the European Union — counted from the date the invoice was issued or, if later, paid. The reasoning is the same as for contracts (section "Signing a contract"); the legal basis is Art. 6(1)(f) GDPR. After that, the underlying inquiry is deleted together with the order, payments and access links. Further detail on your rights is set out in the section "Your rights".
**Reminders via WhatsApp.** When an agreed instalment falls due, we remind you by email. At your express request, also via WhatsApp: you can switch this on from your payment page and withdraw it there at any time. Only then do we transmit your phone number together with the description, amount, due date and the address of your payment page to WhatsApp Ireland Limited (Merrion Road, Dublin 4, Ireland) and its parent company Meta Platforms, Inc. in the USA. The legal basis is your consent, Art. 6(1)(a) GDPR; we record when you gave it and to which wording. Without consent no transmission takes place, and the email reminder is unaffected either way. The message is sent as a template approved in advance by WhatsApp — the provider does not permit such a message in any other form.
**Reminders and messages via Telegram.** On your payment page you can connect to our Telegram bot: one tap opens Telegram, and only when you press “Start” there is your chat linked to your order. From then on we send you reminders about installments due there, and you can message us there; we store the texts exchanged with the order. Send /stop in the chat or use the payment page to disconnect at any time. The bot receives from Telegram your display name, username, profile picture and the messages you send it. The provider is Telegram Messenger Inc. Which data about you is kept, and for how long, is settled before we use the channel; you can ask us about it at any time. Email reminders continue either way.
When a payment arrives we issue a receipt with its own number and send it to you by email and through the channels you have consented to. It shows no VAT; Awelior LLC is not registered for VAT in Germany or the EU. For ongoing agreements (support, maintenance) each period reached becomes an ordinary invoice on the same order — with the same details and the same payment link as any other.
**Refunds and invoice corrections.** If we refund a payment in full or in part, we record the amount, the currency, the refund method and an internal reason, as well as who requested, approved and carried out the refund and when. Carrying it out creates a correction document with its own number, which refers to the original invoice and takes over its recipient details. You receive an email about it, and the document appears on your payment page; the internal reason is not shown there. If you paid through Stripe, we instruct Stripe to refund the amount; for this we transmit the identifier of your payment at Stripe, the amount and an internal identifier of the refund, and Stripe reports the status back to us. What is said about Stripe above applies. If you paid through PayPal, we instruct PayPal in the same way; for this we transmit the identifier of your payment at PayPal, the amount, the currency and an internal identifier of the refund, and PayPal reports the status back to us. What is said about PayPal above applies. If you paid with cryptocurrency via BitPay, we instruct the refund in BitPay’s merchant dashboard — referencing the identifier of the BitPay invoice and stating the amount in the invoice currency. BitPay then asks you, usually by email, for an address for the refund and pays in the cryptocurrency of the payment, converted at the rate at the time of the refund; BitPay may deduct the network fee for the refund from the amount. What is said about BitPay above applies. The legal basis is Art. 6(1)(b) GDPR; the retention periods stated above apply.
**Bank details for ongoing services.** If you agree an ongoing service (subscription) with us, we store for that order the bank account from which the recurring payments are made — provided by you in your customer account or by our team on your behalf: the account holder, the IBAN and, where given, the BIC, or, in countries without IBAN, the account number, bank and SWIFT/BIC. We also record when you consented, the wording of the statement you agreed to, and whether the details came from you or from our team. The subscription cannot be activated without these details. We store the account holder and the account number or IBAN in encrypted form; only the last four characters of the number are shown, including in the change log. You, in your customer account, or our team can remove the bank details at any time. They are deleted automatically as soon as no subscription is running for the order and no subscription invoice is still open, and at the latest together with the order. The invoices themselves do not contain your bank details. The legal basis is Art. 6(1)(b) GDPR (performance of the contract).
**Saved payment method for subscriptions.** For recurring payments you can save a card on a Stripe page or — if you are based in the EU and billed in euros — grant a SEPA Direct Debit mandate. You enter card and account details only with Stripe; they never reach our server. For the setup we send Stripe your name, your email address and an identifier of the order, and for each charge the amount, a short description and identifiers of the invoice. We store only the identifiers at Stripe (customer, payment method and, where applicable, the mandate and its status) and, for display, the type, brand, last four digits, country and card expiration date, as well as, for each collection attempt, the time, the result and any error code. What is said above about Stripe's roles and transfers to the United States applies. The legal basis is Art. 6(1)(b) GDPR. You can remove the payment method yourself at any time in your customer account, and so can our team; we then also detach it at Stripe, which for SEPA ends the mandate. This happens automatically as soon as no subscription is running for the order and no subscription invoice is still open, and at the latest together with the order.
**PayPal as a payment method for subscriptions.** For subscriptions in euros or US dollars, you can also save PayPal instead of a card or direct debit. We take you to PayPal, where you sign in and agree that we collect this subscription’s invoices from your PayPal account. Your PayPal login details never reach our server. For the setup we send PayPal only the language of the page and the addresses PayPal sends you back to, and for each charge the amount, the currency, the invoice number and an internal identifier of the invoice. We store only the identifier of your consent at PayPal, for display your PayPal email address in shortened form (first letter and domain), and, for each collection attempt, the time, the result and any error code. With it we collect, for each subscription invoice that falls due, exactly its amount, until you remove the payment method or no subscription is running any longer. What is said above about PayPal as the provider, its responsibility and transfers to the United States applies. The legal basis is Art. 6(1)(b) GDPR. You can remove the consent at any time in your customer account — we then also delete it at PayPal — or end it in your PayPal account; PayPal then notifies us, and we ask you for a new payment method. It is deleted automatically as described above for the payment method at Stripe.
Quote and acceptance
If you accept a quote via the link we send you, we record as evidence WHO accepted WHAT and when — including your IP address and your browser identification. Without that record the acceptance could not be proven later.
We send quotes to you as a link under /offer. The address contains an access token of 32 random bytes; there is no account, no password and no session for it. As long as you neither accept nor decline, the page merely retrieves the text of the quote and stores nothing about you.
At the moment of acceptance we store: the name you entered in the form; the time recorded by our server (not by your device); the checksum (SHA-256) of the content you accepted — including line items, totals and discounts; your IP address; and the browser identification your program sends. If you decline, we store the time and, if you give one, the reason.
The legal basis is Art. 6(1)(b) GDPR (pre-contractual steps and performance of the contract) and our legitimate interest in reliable evidence under Art. 6(1)(f) GDPR.
If we withdraw a quote, the access token expires immediately; afterwards the link leads to the same error page as an invented address. Retention follows the same periods as for contracts.
Signing a contract
If you sign a contract via the link we send you, we record as evidence WHO signed WHAT and when — including your IP address and your browser identification. Without that record the signature would be worthless as evidence. We delete those two technical details after three years.
We send contracts to you as a link at /contract. The address contains an access token of 32 random bytes; there is no account, no password and no session for it. As long as you do not sign, the page merely retrieves the contract text and stores nothing about you.
At the moment of signing we store: the name and email address you entered in the form; the time recorded by our server (not by your device); the checksum (SHA-256) of the text that was signed; your IP address — in full for IPv4, only the /64 network for IPv6; the browser identification your program sends; and each individual consent together with its exact wording.
Before signing, you separately agree that the contract may be signed electronically; we record the wording of this agreement and the time. We then send a six-digit confirmation code to the email address you provided. It is valid for ten minutes and allows at most five attempts; it is stored only as a hash, together with the name, email address, time sent and number of attempts. We delete these code details after 30 days, the next time the system sends a code. The wording and time of the agreement, the address the code was sent to and the time of confirmation become part of the signature record and are kept for as long as the contract. The legal basis is Art. 6(1)(b) GDPR, and for the record additionally Art. 6(1)(f) GDPR (preserving evidence).
Legal bases: name, email, time and checksum are processed under Art. 6 (1) (b) GDPR, because they constitute the contract itself. IP address and browser identification are processed under Art. 6 (1) (f) GDPR. Our legitimate interest is securing evidence: an electronic signature under Art. 25 eIDAS Regulation is admissible in court, but it is worth only as much as what it can prove. We have weighed this up and limited those two details to what is necessary — the IPv6 address is truncated, and both are deleted after three years (1,095 days), while the contract itself remains.
We retain the signed contract from the date of signature: seven years, or ten years for clients established or resident in the European Union. Awelior LLC is a US company — the German retention obligations under § 257 HGB and § 147 AO do not apply to us directly. Seven years cover the tax retention and audit periods under US law as well as the usual limitation periods for contractual claims; we choose the longer period where there is an EU connection so that the document remains available for your own retention obligations. The legal basis is Art. 6 (1) (f) GDPR; our legitimate interest is tax record-keeping and the establishment, exercise or defense of legal claims. During this period, a request for erasure under Art. 17 GDPR does not prevail for the contract (Art. 17 (3) (e) GDPR) — it does for the IP address and the browser identification, and we delete those earlier in any case.
For this page we set no cookie and store nothing in your browser’s local or session storage. No information on your device is accessed, so consent under section 25 TDDDG is not required. The page carries "noindex, nofollow", appears in no sitemap and is excluded from retrieval in our robots.txt.
After signing, the same link becomes your copy: the contract text, the time and the checksum remain available there. You also receive a confirmation by email; it contains the time, the checksum and the link, but not the contract text itself. That lets you verify at any time that the text is unchanged — which is what the checksum is for. Anyone holding the link can view the contract; please do not pass it on. A withdrawn link then responds exactly like a made-up address.
Customer records and contact history
Once we do business with you, we keep a record of it — kept separately for the company and for the person we speak with. For the company we store the name, address, country, tax number, website and an internal note. For the contact person we store the first and last name, email address, phone number, position within the company, the language we speak with you in, and likewise an internal note. A record without a company is possible and is the normal case for private clients.
These details come from your inquiry or from our conversation with you. We do not buy in address lists, we do not fill in gaps from public registers, and we do not create a record for anyone whose details we did not receive from them directly.
We also keep a note of what was discussed between us: the kind of contact (call, email, note, meeting), a heading, the note itself and the date on which it took place. These notes are visible to us alone. Their only purpose is to let us follow the course of our business relationship in one place. The language on file also determines the language in which quotes and contracts go out to you.
The legal basis is Art. 6 (1) (b) GDPR insofar as the details serve to initiate or perform a contract with you. In all other cases the processing rests on our legitimate interest in handling our business contacts in an orderly manner (Art. 6 (1) (f) GDPR).
A record is removed in two steps. First it is archived: it disappears from the lists but remains findable for existing documents. After that it can be deleted for good, and its entire contact history and the associated internal tasks go with it. Only what has been archived beforehand can be deleted — the second step keeps an accidental click from becoming data loss.
Documents already issued — projects, contracts, invoices — do not disappear in the process. They carry the recipient details that applied when they were issued within themselves and are subject to retention periods; all that is severed is their link to the removed record. Further detail on periods and on your rights is set out in the sections "Contact form" and "Your rights".
For every final deletion we keep a note: when it was deleted, by whom, whether it concerned a company or a person, and how many history entries were removed with it. This note deliberately contains no name and no contact details — a log that preserves names preserves exactly what was meant to be deleted.
These data are not passed on to third parties — with one exception: the partner who referred you or looks after you receives your name and the basic details listed individually in the section "Partner program and referral code".
Messages via WhatsApp and Telegram
Email is part of the business relationship. WhatsApp and Telegram only if you have expressly consented — and your withdrawal ends both immediately.
We send confirmations, receipts, payment reminders and project updates by email. The legal basis is Art. 6(1)(b) GDPR: without these messages the contract cannot be performed.
In addition you may choose WhatsApp or Telegram — when filling in a form, in conversation with us, or through a partner. For that we store the number you give for it (it may differ from your phone number), the time of your consent, the way it was given, and the exact wording you agreed to. The legal basis is your consent under Art. 6(1)(a) GDPR.
If you have a customer account, you can enter, change or remove your WhatsApp and Telegram numbers there yourself and choose whether we notify you through them; we record the statement you checked. Our team can also add the numbers if you have consented in a conversation with us or through a partner — again with the time, the channel and the wording. The numbers are stored in a single place, your record in our customer database (section "Customer records and contact history"); if you enter them in your customer account and no such record exists yet, we create one for this purpose. All notifications about your orders, such as receipts and payment reminders, take the number from there. You can also withdraw your consent in your customer account by clearing the selection there.
Through these channels we send messages about your matter only — no advertising. For WhatsApp we use templates approved by the provider; for Telegram you establish the connection yourself via a link, because Telegram does not allow a bot to make the first move.
You can withdraw it at any time — on the payment page for your matter, in your customer account, with an informal message to us or, for WhatsApp, by writing "stop" in the chat with us; we then remove the WhatsApp consent for that number wherever it is recorded. Withdrawal deletes the stored number AND the consent; afterwards only emails reach you. A withdrawal applies to all kinds of messages, not only to the one in which you declared it.
If you write to us via WhatsApp or Telegram, our digital assistant Robora answers first; at any time a person from our team can take over the conversation and reply themselves, and at your request Robora hands over to a human. For this we store the conversation history — your messages, the replies from Robora and from our team, your display name, your number or Telegram identifier, and the language you write in. The history is deleted 90 days after the last message. We also keep the interim state of a request you have started (deleted after twelve hours without continuation, otherwise on booking or cancellation) and the identifiers of incoming messages so that none is processed twice (deleted after two days). Writing "stop" deletes the interim state and the language immediately, and we will not write to you again. The legal basis is Art. 6(1)(b) GDPR where an inquiry or engagement is concerned, and otherwise our legitimate interest in answering your message (Art. 6(1)(f) GDPR).
If you send us a voice message via WhatsApp or Telegram, we download it from the respective provider and store it on our server as part of the conversation history — together with its duration, file format and a transcript. The transcript is produced by the AI provider (for example OpenAI) that we have assigned to this task in our admin area; Robora uses it to answer your request in your language, and our team reads it translated. If we have set it up that way, Robora also replies to a voice message with a spoken message; for this, the same or another assigned AI provider receives the text of the reply. Our team’s voice messages can be created in the same way: a team member records them, or their written text is translated and spoken by the AI provider. We only use providers with whom a data processing agreement is in place and who do not use the transmitted content to train their models; for any transfer outside the EU and the EEA, the same applies as in the section “AI assistant”. Only team members authorized for the chat inbox can listen to voice messages; they are never publicly accessible. Voice messages and transcripts are deleted together with the conversation history 90 days after the last message, immediately after “stop”, and if you delete a voice message in Telegram, we delete it as well. The legal basis is the same as for the conversation history (Art. 6(1)(b) GDPR, otherwise Art. 6(1)(f) GDPR).
If you send us an image, a document, a video or a sticker via WhatsApp or Telegram, we download the file from the respective provider and store it on our server as part of the conversation history — together with its file type, size and file name; for images we create a small preview. There is no automated analysis: neither Robora nor any AI provider opens, reads or analyzes the file or its name, and there is no image recognition and no text recognition. Robora only confirms receipt, and a member of our team looks at the file; any caption you add is handled like an ordinary text message. Our team can send you images and files the same way. Only team members authorized for the chat inbox can view and download the files; they are never publicly accessible. Files and previews are deleted together with the conversation history 90 days after the last message, immediately after “stop”, and if you delete a file in Telegram, we delete it as well. The legal basis is the same as for the conversation history (Art. 6(1)(b) GDPR, otherwise Art. 6(1)(f) GDPR).
Recipients are WhatsApp Ireland Limited or Meta Platforms, Inc. and Telegram FZ-LLC. What these companies process beyond this is governed by their own terms.
Notifications to our team
When something from you reaches us — an inquiry, a ticket, a payment — we notify the responsible people on our team, and, if they have turned it on, by push on their phone or browser. The message is short: the type of event and, for example, your name or a subject line — no contact details and no full message text.
So that your request is not left waiting, the responsible people on our team receive a notification when, for example, an inquiry, the acceptance of a quote, a contract signature, a payment, a ticket or a reply to one, a live support request, feedback in your project or a refund awaiting approval comes in.
The notification contains the type of event and a short text — such as the name you provided, a quote or invoice number, the subject of a ticket or the topic of a question. It does not contain your contact details or the full text of your message; the details stay behind the sign-in to our admin area. We delete read notifications there after 90 days.
A notification reaches a phone through our admin app. It is delivered through the push service of Expo (650 Industries, Inc., USA), which passes it on to Google's Firebase Cloud Messaging (Android) or Apple's Push Notification service (iPhone). These services receive the text of the notification. Expo states that it holds the content only in memory until it has been handed to Google or Apple, and does not store it in a database. Notifications delivered in a browser go through the push service of the respective browser maker; their content is encrypted under RFC 8291, so that service sees only the time and the size. In both cases a transfer to the United States is possible; Expo states that it participates in the EU-U.S. Data Privacy Framework.
The legal basis is our legitimate interest in handling your request promptly (Art. 6(1)(f) GDPR). The notification about a recorded page view is described separately in the section "Visitor statistics".
Contact by email
If you write to us directly by email, your message together with all resulting personal data is stored by us for the purpose of handling your inquiry. The legal bases correspond to those for the contact form.
Our system automatically retrieves emails sent to our addresses (such as contact@awelior.net) from our mailboxes and files them — depending on the address — as a new inquiry, as a support ticket or with an existing matter; anything that cannot be matched stays in our inbox as "unassigned" until someone on our team handles it. We take over the sender address and name, the subject line and the text. We do not take over attachments, only their file names; the email itself remains in the mailbox with the provider of our mail server.
The legal basis is Art. 6(1)(b) GDPR where your email concerns preparing or performing a contract, and otherwise our legitimate interest in handling the messages sent to us in an orderly way (Art. 6(1)(f) GDPR).
Retention period: if an email belongs to an inquiry, the inquiry's retention period applies (section "Contact form"). For all other emails, we automatically clear the sender, subject line and text in our inbox after 180 days; we set this period in the admin area.
Cookies and local storage
There are no statistics cookies and no third-party cookies on this website. A single cookie serves advertising — crediting a referral — and it is set only if you consent. Only what the site needs in order to work is stored: your answer to the consent notice, the language we serve it to you in, and your color scheme. On top of that comes what you trigger yourself — your voice choice in the phone assistant demo and, if you sign in, your session in the customer, partner or administration area. The complete list appears further down. The language is recorded in the cookie on every visit; on the very first visit, before that cookie exists, we determine it first from your IP address, falling back to whatever your browser states — more on this below.
Access to information on your terminal equipment is governed by § 25 TDDDG and comparable provisions of other countries (e.g. Art. 22.2 LSSI-CE in Spain). Whatever is strictly necessary in order to provide the service you asked for requires no consent under § 25 (2) no. 2 TDDDG. Anything beyond that is set only after your express consent — and at present there is exactly one of the kind: the cookie that credits a referral (section “Partner program and referral code”).
An additional step applies to the language before that cookie exists: on your very first visit, with no cookie set yet, we first work out the likely language from your IP address, using a bundled database that is looked up purely locally on our own server. This establishes no connection to a third party, and your IP address is not stored for this purpose — it serves only the one-off, momentary assignment to a country and, from that, a language, in addition to the logging that in any case takes place as described in “Server log files”. If no country can be determined, we fall back to the language your browser sends instead. Once the cookie is set — through this determination or through your own choice in the language switcher — this step is skipped, and every further visit uses the cookie directly.
We show times in your device’s time zone. Your browser reads its time zone and stores it in the strictly necessary cookie “tz” (one year, no name, no identifier, not shared with third parties); for signed-in accounts we also keep the time zone alongside the email address so that emails — such as appointment confirmations — state the time in your local time. We delete this association 400 days after the last report. Accounting records and legal deadlines are excluded and state their time zone explicitly.
On your first visit a notice appears offering three equally weighted routes: accept all, necessary only, or open the settings. We record your decision in the cookie “awelior_consent” listed below. That cookie itself requires no consent, because it does precisely what you asked for — without it the question would return on every page view. It contains nothing but the categories you chose and a version number: no name, no identifier, no IP address, nothing by which you could be recognized. It is shared with nobody.
You can change or completely withdraw your decision at any time through “Cookie settings” in the footer of every page. Withdrawing is therefore exactly as easy as giving consent. Withdrawing deletes the cookie and brings the notice back. If the categories listed here change, the version number is raised and we ask you again; consent to a list that no longer exists in that form is not consent to the present one.
You can also delete every item at any time through your browser settings. The complete list — with name, provider, purpose and lifetime — appears here and is generated from the same file as the notice and the settings dialog:
Necessary
Always on
awelior_consent
- Provider
- Awelior (this website)
- Purpose
- Stores your decision from this notice together with the version number of this list. Without it the notice would reappear on every page view. It contains no name, no identifier and nothing by which you could be recognized — only the categories you chose and a number. It is not shared with third parties.
- Storage
- Cookie
- Lifetime
- 182 days
AWELIOR_LOCALE
- Provider
- Awelior (this website)
- Purpose
- Records which language the site was last served to you in. It is set or renewed on every page view with a language prefix. If you open the site without a language prefix and have never chosen a language yourself, we determine it from your IP address (looked up purely locally on our server, with no connection to a third party), falling back to the language your browser sends.
- Storage
- Cookie
- Lifetime
- 365 days
AWELIOR_LOCALE_WAHL
- Provider
- Awelior (this website)
- Purpose
- Set only when you choose the language yourself with the language switcher. While it exists, the site opens in that language when called without a language prefix, instead of determining it from your IP address. It contains only the language code.
- Storage
- Cookie
- Lifetime
- 365 days
awelior-theme
- Provider
- Awelior (this website)
- Purpose
- Remembers whether you chose the light or the dark color scheme. It is only written once you switch, lives in your browser's local storage and is never transmitted to a server.
- Storage
- Local storage
- Lifetime
- Until you delete it in your browser
awelior-projekt-entwurf
- Provider
- Awelior (this website)
- Purpose
- Keeps your answers in the project inquiry until you submit — so nothing is lost if you go back or the page reloads. It lives in your browser's local storage, is deleted once you submit, and is no longer used after 20 hours; none of it is sent to a server before you submit.
- Storage
- Local storage
- Lifetime
- Until you delete it in your browser
awelior-stimme-de / -en / -ru / -tg / -es / -uz
- Provider
- Awelior (this website)
- Purpose
- Remembers which reading voice you chose in the telephone demo — one entry per language. It is only written once you pick a voice there, lives in your browser's local storage and is never transmitted to a server. All that is stored is the voice identifier as your browser names it.
- Storage
- Local storage
- Lifetime
- Until you delete it in your browser
awelior-stimme-nur-lokal
- Provider
- Awelior (this website)
- Purpose
- Records that you want the telephone demo to use only voices that run on your own device. Some reading voices from Microsoft and Google convert the text on a server belonging to the browser vendor; with this entry set they are not offered at all. It lives in your browser's local storage and is never transmitted to a server.
- Storage
- Local storage
- Lifetime
- Until you delete it in your browser
__Host-awelior_kunde
- Provider
- Awelior (this website)
- Purpose
- Session identifier for the customer account. It is set only after signing in at /account and never on an ordinary visit. Without it a signed-in account is technically impossible; it serves no analysis of any kind.
- Storage
- Cookie
- Lifetime
- 30 days
__Host-awelior_partner
- Provider
- Awelior (this website)
- Purpose
- Session identifier for the partner account. It is set only after signing in at /partner-account and never on an ordinary visit. Without it a signed-in account is technically impossible; it serves no analysis of any kind.
- Storage
- Cookie
- Lifetime
- 30 days
__Host-awelior_mitarbeiter
- Provider
- Awelior (this website)
- Purpose
- Session identifier for the staff portal. It is set only after signing in at /staff-account and never on an ordinary visit. Without it a signed-in portal session is technically impossible; it serves no analysis of any kind.
- Storage
- Cookie
- Lifetime
- 30 days
__Host-awelior_admin
- Provider
- Awelior (this website)
- Purpose
- Session identifier for the internal editing area at /admin. It is set only after signing in there and never when visiting the public pages. Listed here so that this register is complete.
- Storage
- Cookie
- Lifetime
- 12 hours
__Host-awelior_device
- Provider
- Awelior (this website)
- Purpose
- Set only after a successful sign-in to the customer account, partner account, staff portal or editing area. It marks this device as already known, so that attacks on your account do not lock you out and you do not have to solve a security check. It contains no email address and no password, only a signed random identifier, and is not shared with third parties.
- Storage
- Cookie
- Lifetime
- 180 days
awelior_vorschau
- Provider
- Awelior (preview address <name>.awelior.com)
- Purpose
- Session identifier for the preview of a website we are building for a client. It is set only on that preview address — never on awelior.com — and only after an authorized person has signed in to their account and opened the preview. It contains only a random token that opens nothing except this one preview. Without it the preview cannot be accessed; it serves no analysis of any kind.
- Storage
- Cookie
- Lifetime
- 12 hours
tz
- Provider
- Awelior (this website)
- Purpose
- Remembers the time zone of your device (for example “America/New_York”) so that appointments, times and histories are shown in your local time. Your browser sets it itself; it contains only that time zone, no name and no identifier, and it is not shared with third parties.
- Storage
- Cookie
- Lifetime
- 365 days
Statistics
Nothing in it
This category is empty — so there is nothing here for you to consent to. We do count page views, but without a cookie, without an identifier and without anything being stored on your device: after a page has loaded, your browser sends a short message with the path visited to our own server. What exactly is recorded is described in the privacy notice under “Visitor statistics”.
External media
Nothing in it
This category is currently empty. All content on this website comes from our own server; opening it establishes no connection to third parties. Here too we will ask again before that changes.
Referral
Consent required
__Host-awelior_referral
- Provider
- Awelior (this website)
- Purpose
- Remembers which referral link brought you here, so that a later inquiry is credited to the right partner. It contains only the partner code and, where applicable, the campaign tag — no identifier by which a visitor could be recognized.
- Storage
- Cookie
- Lifetime
- 30 days
No tracking, no third-party services
We deliberately use no analytics tools, no tracking pixels, no advertising networks and no social media embeds. No profiles of your behavior are created. This promise covers viewing this website. There are exactly two places where you yourself can call on a third-party service — the assistant (section "AI assistant") and online payment (section "Payment link for clients"). Both are described there individually, both require an action from you, and merely opening a page establishes no connection to either.
Fonts are served from our own server and not loaded from an external provider. Accessing this website therefore establishes no connection to third-party servers.
The AI agent demos shown on this website are entirely scripted simulations that run in your browser; for these demos, no language model and no external service is called. This does not apply to the real website assistant described in the section "AI assistant" — that one does call a genuine, server-side AI language model.
The phone assistant demo has no connection to a telephony provider, and nothing is recorded, nothing is transmitted to us and nothing is evaluated — the transcript is stored text revealed in sequence. Unlike the AI agent demos above, however, it does contain audio: the audio files were pre-produced — generated once, before publication, using an external speech service, and served ever since from our own server like any other media file. What is external there is the tool used for that one-time production, not the ongoing operation: accessing the demo does not call that service. If a given turn in the conversation exceptionally has no such file, or it cannot be played, the speech synthesis built into your browser reads it instead — a feature of your own device, which we do not trigger. If an “Online” or “Natural” voice is selected there, your browser transmits the displayed conversation text to its own provider for conversion, on its own initiative; the demo's controls always name which voice is currently playing and whether it works locally or transmits. Anyone who wants to rule this out can restrict the voice choice there to voices that run exclusively on their own device.
Where this website shows reviews from our own Google Business Profile, they were fetched server-side on a schedule and cached. Visiting this website itself establishes no connection to Google, and no data about you is transmitted to Google in the process.
AI assistant
For Robora, our digital assistant on the website, we use a server-side AI language model. Without signing in, it answers your questions solely from our own published content — with no personal data involved. Inside your customer account, it additionally answers questions about your own orders and payments; it never sees another customer's data. We store conversations for 90 days so that our team can take them over if needed.
This website offers an assistant that answers your questions using an AI language model. The model is called exclusively server-side — never directly from your browser. Which provider and which model are used is configured in the admin area and can be changed there at any time.
If you use the assistant without signing in — for example on a public page — the language model receives, for your question, only this website's own published content: services, pricing and frequently asked questions. We add no personal data in the process; only what you write into your question yourself is transmitted. The legal basis is our legitimate interest in providing pre-contractual customer service (Art. 6 (1) (f) GDPR).
If you use the assistant inside your customer account (under /account), the language model additionally receives your own order and payment data — your name, the details of your orders and the status of any recorded payments ("Open" / "Paid on …") — so that the assistant can also answer account-specific questions. This is determined solely by your signed-in session; the model never receives another customer's data. The legal basis is Art. 6 (1) (b) GDPR (performance of the contractual relationship).
If you use the assistant in your partner account, the language model additionally receives your name, your partner number and whether your account has been approved; for your own quotes, the number, title, status, submission and decision dates and any reason for rejection; and for your referrals only the number of referrals, how many have been paid and the totals of your share. It does not receive the names, addresses or contact details of your clients, or line items and prices. In the staff portal it receives your name, your number, your status, whether you have an account and which documents are still missing, as well as the number, title, status, target date and your role for your own projects, and the title, project, status and due date of your own tasks — no fees, hours or credit notes. In both cases the assignment is made solely through your signed-in session; the model never receives anyone else's details. The legal basis is Art. 6(1)(b) GDPR (performance of the partner agreement or of our working relationship).
Our digital assistant is called Robora. If you would like to talk to a person, it offers you — depending on whether someone from our support team is available — the live chat or a support request. For this, your browser compiles a summary from the most recent messages of the conversation; you see it, can change it and send it yourself. Only then do we receive it, together with your name and email address — from your account if you are signed in, otherwise as you enter them. The legal basis is Art. 6(1)(b) GDPR where your request concerns a contract or preparing one, and otherwise our legitimate interest in handling your request (Art. 6(1)(f) GDPR).
If you are interested in a project, Robora can create an inquiry with an appointment together with you in the chat — using the same questions as the project inquiry. This involves your answers, the chosen appointment, your name, your email address, your phone number if given, your country and, where we serve business clients only, your statement that you are acting as a business. We use these to book the appointment, confirm it and handle the inquiry like a project inquiry sent through the website (section "Project inquiry, attachments, and appointment booking"). The legal basis is Art. 6(1)(b) GDPR. Until the booking, we store only the interim state of these details under a random token known only to your browser (the conversation itself is covered under the retention period below); it is deleted on booking or cancellation. An interim state that has not been continued for twelve hours is deleted automatically.
We use the same approach in other places: our bot on Telegram and WhatsApp answers your messages with the help of a language model; we have messages in tickets and live support, as well as documents, translated when you and the responsible person on our team use different languages; and our team uses an assistant in the admin area. In each case the provider receives the text concerned — including any names or other details it contains. We cache translations on our server so that the same text is not transmitted again. The legal basis is Art. 6(1)(b) GDPR where this serves the performance of our contract or your request, and otherwise our legitimate interest in communicating in your language and answering promptly (Art. 6(1)(f) GDPR). If you write to us in a language other than that of the responsible person on our team — whatever language it is — the language model recognizes your language; your message is translated for our team and the reply into your language, so you write and read in your own language throughout.
For each of these features we set in the admin area which provider and which model is used; the choice includes providers based in the EU, in the United States and in other countries. That is why we do not name a fixed provider here. If personal data is transmitted to a provider outside the EU or the EEA, this happens only under the conditions of Art. 44 et seq. GDPR: to a country covered by an adequacy decision of the European Commission — for the United States this applies only to companies participating in the EU-U.S. Data Privacy Framework — or on the basis of the European Commission's standard contractual clauses (Art. 46(2)(c) GDPR). A fixed rule applies: features that process personal data run only through providers with whom a data protection agreement has been confirmed; all others are blocked for these features. A direct connection to providers in countries for which none of the bases above holds is always blocked for these features. On request, we will tell you which provider is currently in use, where it is based and on what basis data is transferred; if you wish, you will receive a copy of the safeguards.
Voice input: A microphone button may appear next to the assistant’s input field. If you tap it, your browser’s speech recognition turns what you say into text. This recognition is a feature of your browser, not ours: depending on the browser, it sends the recording to its provider — Chrome to Google, Safari to Apple — possibly to countries outside your own. We only receive the recognized text, as if you had typed it; we never receive an audio recording. Before the first use, the button tells you this, and nothing is recorded without your click. The legal basis is your consent by tapping it (Art. 6(1)(a) GDPR where applicable); you can always type instead.
Retention period: we store conversations with Robora on this website — without signing in or in your customer account — on our server so that a person from our team can take them over if needed and reply to you in the same window. We store your messages, the replies, and a random identifier for your conversation that your browser keeps for the duration of the session. The history is deleted 90 days after the last message. The legal basis is Art. 6(1)(b) GDPR where your request concerns a contract or preparing one, and otherwise our legitimate interest in answering your request (Art. 6(1)(f) GDPR).
Protection against fraud and abuse: before Robora replies on this website, via Telegram or via WhatsApp, our own server checks the message against fixed rules for manipulation attempts (for example, requests to override instructions or to reveal internal information) and for fraud patterns (for example, requests to change bank details, confirm payments or disclose passwords and one-time codes); Robora’s replies are also checked before they are sent. Nothing is sent to an AI provider for this check. If a message is flagged, Robora does not answer it but offers to pass the request on to our team. We then record the time, the channel, the link to the conversation, the type and severity of the incident and a short excerpt in which email addresses, phone numbers, bank details and access codes are masked; the conversation is flagged, and the team members authorized for the chat inbox are notified. If we have set it up that way, Robora stops answering automatically in that conversation after several such attempts, and a person takes over. We delete these records after 90 days. The purpose is to protect our customers, partners and our company against fraud and abuse; the legal basis is our legitimate interest in doing so (Art. 6(1)(f) GDPR).
Email campaigns
We send email campaigns to business contacts, customers, partners and newsletter subscribers — only where the law of your country allows it, and always with sender, postal address and an unsubscribe link. An unsubscribe takes effect immediately and for good.
Partner recruitment: We write to companies whose business email address is publicly listed (for example in the legal notice of their website) when a partnership seems a good fit. We store the company, contact person, industry, country, city, language, website, where the address was found and the legal basis. Whether we write without prior consent depends on the company’s country: where consent is required (for example in Germany, Austria, Switzerland or Canada) we only write with consent; we never write to private individuals without consent. In the United States we follow the CAN-SPAM Act. The legal basis is our legitimate interest in finding business partners (Art. 6(1)(f) GDPR) or your consent (Art. 6(1)(a)).
Research before the first contact: Before we approach a company for the first time, we compile an internal dossier from publicly available business sources (website, business directories such as 2GIS, registry entries, public tenders, news, company profiles on social networks): information about the company, the name, role and professional language skills of decision makers, business contacts through whom we know the company, the sources with their date and our plan for the approach. We do not collect private information (home address, family, private phone numbers), and we do not read websites automatically. The legal basis is our legitimate interest in carefully prepared business development (Art. 6(1)(f) GDPR); in Tajikistan we observe the Law “On Personal Data Protection”. Only the sales staff responsible for the company have access, and every change is logged. Retention: if you object to being contacted or your address is on our suppression list, we delete the dossier by the following day at the latest; after a “not interested” 12 months after the last contact, and without any activity after 24 months. On request we delete it immediately and tell you what information we held.
Customers, partners, team and newsletter: Customers, partners and our team receive information about our work together (Art. 6(1)(b) and (f) GDPR). We only send marketing to customers where the law of their country allows it without consent, otherwise only with newsletter consent. Newsletter subscribers receive campaigns based on their consent (Art. 6(1)(a)).
Sending: We send campaigns through a dedicated sending subdomain, either via a sending provider — Amazon Web Services EMEA SARL (Luxembourg) with Amazon SES in the Frankfurt region, or Sendinblue SAS (Brevo, Paris) — or via our own mail server. The provider processes the address and content of the email on our behalf (Art. 28 GDPR). Amazon cannot rule out access from the United States; Amazon participates in the EU-U.S. Data Privacy Framework.
Analytics: Per campaign we only count in total how many emails were delivered, bounced, unsubscribed or reported as spam, how often a link was clicked and — as an estimate via a small image — how often an email was opened. These numbers are not linked to any person and no profile is created. In campaigns to newsletter subscribers we count neither opens nor clicks.
Unsubscribe and blocklist: Every email contains an unsubscribe link and the header for one-click unsubscribe in your mailbox. After an unsubscribe, a permanently undeliverable address or a spam complaint we never write to the address again. For this our blocklist only stores a checksum of the address, not the address itself. You can object to the processing at any time (Art. 21 GDPR).
Retention: We delete prospects’ contact data as soon as you object or we no longer need it; the sending log of a campaign (address, time, status) 180 days after it ends. The checksum on the blocklist remains so that we do not write to you again.
Visitor statistics
Only when we switch this feature on in the admin area is each page view logged — timestamp, city, country, network type and the path visited, nothing else. For this, your browser sends a short message to our own server after the page has loaded. No cookie is set, nothing is stored on your device, no IP address is stored, and no visitor is re-identified across multiple visits.
This logging is switched off by default and only takes effect once we explicitly enable it. While it is off, visiting this website creates no additional record at all — and this section itself does not appear.
When it is switched on, we store for each visit to a content page: the time, the city and the country derived from your IP address (the same local, connectionless lookup described in “Cookies and local storage”), and the path visited. We use the IP address itself only briefly in memory — for this lookup and to limit abusive numbers of messages — and do not store it, nor any identifier, cookie or other feature that could link several visits to the same person. The admin area, the customer account, the partner and staff portals, technical requests and the personalized pages at /order, /contract and /payment are not counted. A page view is only counted once the page has actually loaded and been displayed in your browser: a small script on the page then sends — after the page has fully loaded and as soon as it is visible — a short message to our own server using “sendBeacon” (or, as a fallback, “fetch” without cookies). It contains only the path visited and whether this is the first page of your visit. To determine this, the script checks two values locally in your browser: whether the previous page (referrer) belongs to our own website, and whether the browser identifies itself as automated (“navigator.webdriver”) — in that case nothing is sent. Neither the referrer nor this value leaves your browser, and nothing is stored on your device. Requests made without a browser, such as by automated programs, are therefore not counted. While the feature is switched off, this message is not sent either.
We also record whether the visit comes from an ordinary access network (home connection, mobile network, company network) or cannot be classified. This too is derived only briefly in memory from the IP address, locally using a network database on our own server (IP to ASN Lite by DB-IP), without contacting any third party. Requests from data centers (hosting and cloud networks, through which automated programs typically connect) are not counted as visits and trigger no notification; for them we store only a total per day and country — without IP address, city or path — and delete it after 35 days.
We use these figures solely for a rough sense of how much the website is visited and from which countries — for our own operations, not for marketing or profiling. The legal basis is our legitimate interest in this operational evaluation (Art. 6 (1) (f) GDPR); since no link to an identifiable person is made beyond the single visit, we see no overriding interest of yours standing against it.
If we have additionally set up a push notification for ourselves, the first page of a visit (when you do not come from another page of our website) triggers a short notification on our team's devices — regardless of whether a city or country was recognized. The number of these notifications is limited; when there are many visits, we combine them into one. The notification contains only the note that there is a new visit and, where recognized, the city and/or country derived from your IP address — no IP address, no cookie and no other identifier that could link visits to you. On phones it is delivered through the push service of Expo (650 Industries, Inc., USA), which forwards it to Google's (Android) or Apple's (iPhone) push infrastructure; in browsers through the push service of the respective browser's maker (for example Google, Mozilla, Apple or Microsoft). This means data is passed to third parties outside our own system, unlike the rest of the cookie- and identifier-free logging described in this section. The legal basis is the same legitimate interest as above (Art. 6 (1) (f) GDPR); since these providers may also process outside the EU/EEA, this transfer can involve a third country. Independently of this, the same note appears as a notification in the admin area for the team members who are allowed to see the visitor statistics. We store this notification on our own server; it contains the city and the country (where recognized), the path visited and the time — no IP address, no cookie and no identifier —, combines several visits within one hour into a single entry with their number, and is deleted 90 days after the last visit it records, even if it has not been read.
Retention: these records are not subject to a separate deletion period and are removed once we switch the feature off or clean up the database; in any case they cannot be linked to a specific person.
Your rights
You have the right at any time:
- to request information about the data stored about you (Art. 15 GDPR)
- to request rectification of inaccurate data (Art. 16 GDPR)
- to request erasure of your data (Art. 17 GDPR)
- to request restriction of processing (Art. 18 GDPR)
- to receive your data in a common format (Art. 20 GDPR)
- to object to processing (Art. 21 GDPR)
- to withdraw consent given at any time (Art. 7 (3) GDPR)
An informal message to the email address given above is sufficient for all of these requests.
Irrespective of this, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). As Awelior LLC has no establishment in the EU, there is no authority competent by reference to our seat: the competent authority is the one of your habitual residence, your place of work, or the place of the alleged infringement.
Encrypted transmission
For security reasons this site uses SSL/TLS encryption. You can recognize an encrypted connection by the browser address bar changing from "http://" to "https://". While encryption is active, the data you transmit to us cannot be read by third parties.
Invitation to the team by email
When someone on our team sends you an invitation, we process your email address, your name (in Latin script and, if given, in your own script), the intended role, the language of the invitation, the reason (for example the title of a task or project), who invited you, and timestamps. The legal basis is initiating and carrying out the collaboration (Art. 6(1)(b) GDPR) and our legitimate interest in secure access (point (f)). The invitation link is single-use and valid for seven days, and we store it only as a non-reversible hash. Until you have set up your account, the invitation gives access to no data. Invitations that are not redeemed are deleted 30 days after they expire, together with the prepared account; the person who invited you can also withdraw it earlier.
Changes to this policy
We update this privacy policy whenever the processing changes — for example because a new feature is added. The version available on this page is the applicable one.