Privacy Policy
Sales are currently closed; no trial period and no lock apply; all features are open. Paid plans will be announced on this page and in the app before sales open. The trial, plan and lock clauses below apply from that date.
This text explains how the JenUsta app (on phone, tablet and as a web app on a computer; package name com.jenusta.app) processes your personal data. In short: your business data (customers, generators, jobs, payments, rentals, quotes, photos, signatures) works on your phone; for backup and for sync between your phone and the web app it is also stored, encrypted, on our own server. No ads, no tracking, no selling. The paid plans are sold only through the Apple App Store or Google Play (sales are currently closed); we never see your card details. For data relating to purchases, see section 11; for the current state of transfers abroad, see section 5.
1. Controller
Enes Aktaş (sole proprietor). Contact: destek@jenusta.com. I am the controller for your account and purchase data. For the business data you enter in the app (including your customers' data), you, the tradesperson, are the controller; I am the processor who stores this data on your behalf.
Under Turkish Law No. 6698 (KVKK) I am the controller for your account and purchase data. For users in the EU/EEA and the UK, the GDPR information in section 13 applies in addition.
2. Business data on your phone and on the server
Customer names, addresses, generator and machine records, jobs, parts, payments, expenses, debts, rentals, quotes, document templates, receipts, job photos, signatures and your logo are stored first in the local database and app folder on your phone; the app also works without internet. When you are online, this data is additionally sent to our own server. The server is in the Austrian (Vienna) data centre of netcup GmbH (headquartered in Germany). There are only two purposes: backup, and sync between your own devices (phone and web app, app.jenusta.enesakt.com). Each user can reach only their own records.
Business data and photos on the server are stored encrypted with AES-256-GCM. The key is held only in the server environment. This is not end-to-end encryption: the data can be decrypted on the server side for operation. Access is restricted and the admin panel does not show business data. Coordinates you capture with "Get location" are synced together with the address field as part of the customer record.
- Backup: The app makes a daily local backup. A backup file you create with "Share" (for example to Drive, WhatsApp or e-mail) goes to a place you choose; that transfer is under your control.
- Android device backup: If Android's own cloud backup is on, the operating system may back up app data to your Google account. This depends on your device settings and is not done by JenUsta.
- Permissions: Camera and photos (receipts, logo), location (only when you tap "Get location", for a customer address) and notifications (local maintenance and due-date reminders) are requested only for the feature concerned. Photos are synced only when attached to a job record; location is synced as part of the customer address.
3. Data sent to the server
| Data | Purpose |
|---|---|
| Name, e-mail (from Google or Apple sign-in; if you choose Apple "Hide My Email", the relay address) | To create your account and recognise you |
| Sign-in details: provider (Google or Apple) and your account ID at that provider (Apple gives your name only at the first sign-in) | To recognise you at every sign-in and link it to your account; no password is kept |
| Session records: device ID, platform, time created and last used (the renewal token is stored only as an irreversible hash) | To keep you signed in on each device and to end the session when you sign out or remove the device |
| Business name, province, optional business phone (entered by you at first setup) | To manage your account and give you support |
| Account ID, account creation date, trial end date and access status | To determine that your account is open, your 14-day trial period (once sales open) and your access to the app |
| Purchase and subscription data: store (App Store / Google Play), the store's transaction ID or purchase token, product (plan and period), price, purchase and end dates, renewal / cancellation status, store country and currency | To assign the plan you bought to your account, to open your access on phone, tablet and computer, to follow renewal and cancellation, and to keep records as tax law requires. There are no card or payment details; details are in section 11 |
| Your business data: customer, generator, job, part, payment, expense, debt, rental, sale, quote and appointment records; receipt and job photos, signatures, logo | Backup and sync between phone and web app (stored encrypted) |
| Business details: address, tax office / number, IBAN, account holder, logo, signature (entered by you in your profile, optional) | Use in the heading of quotes and statements; backup and sync (stored encrypted) |
| Generator label (QR): label code, business name, phone, province, generator model and serial number; only when you print a label, and only what is already printed on the label | To show the person who scans the QR code on the label the tradesperson's name, phone and generator information. This information is not encrypted and can be seen by anyone who scans the QR code, without signing in. It is sent to the server only when you print a label, and only what is printed on the label; nothing you do not put on the label is sent. When you delete the generator or your account, that label's page is closed and the label information is deleted from the server; only the code is kept, so that it is not given to someone else |
| Notification token (Firebase Cloud Messaging), sent together with the daily counter | To send notifications to your device: replies to your support messages, new enquiries from your website and announcements about the app. The notification text contains no personal data: for a support reply it is "Yeni bir yanıtınız var." ("You have a new reply."), and for an enquiry from your website the title "Yeni teklif talebi" ("New quote request") and the text "Ayrıntı uygulamada." ("Details in the app."); your customers' or your website visitors' details and the text of the support message are not written into the notification. These push texts are currently sent in Turkish. Other notifications are fixed generic texts; I write announcements and notifications specific to you without personal data (see section 5) |
| Notification records: the target of a notification (everyone, a group or you), its title and text, which of your devices it was sent to and whether you opened it | To see that a notification was delivered, to prevent the same notification from reaching the same device twice, and to see how many people an announcement reached |
| Support messages: the messages you write in the app and my replies | To answer your questions. These messages are not additionally encrypted like business data; only I read them. A message may carry the app language and, for "wrong translation" reports, the screen name. Your support messages and my replies are not sent to Anthropic (Claude API, USA); message translation has been switched off since 18 November 2026 (see section 5) |
| Hourly usage: your account ID and the hour in which the app was open (one record per hour; which screen you were on or what you did is not recorded) | To see in the admin panel how many users are active at which hours of the day, and to choose support and maintenance hours accordingly |
| Trial device key: an irreversible digest of your phone's identifier, taken on the phone (digested once more on the server with a secret key), and the ID of the account that took the first trial on this device | To prevent the 14-day free trial from being obtained again on the same device by switching accounts (once sales open). The phone's own identifier is not sent to the server |
| Security and evidence records: admin actions (for example blocking an account, granting time, deleting) and which account they were applied to; admin notes specific to you; if you used a campaign code, the code, the date and region together with an irreversible digest of your sign-in identity; for an account deletion request received by e-mail or another route, the requester's e-mail, the channel, the date and the result | The security of the service and the auditability of admin actions, using a campaign code only once per person, being able to show that deletion requests were fulfilled in time |
| My website (optional): business name, city, phone, emergency phone, WhatsApp, e-mail, address and map location, opening hours, service area, social media links, logo and photos, product, service, project and FAQ texts | To publish a public website for your business. This information is not encrypted and can be seen by anyone who opens the site; I review it before it is published. If you delete the site, it goes offline at once and is deleted from the server 30 days later; if you delete your account, it is deleted at once. Visitors' taps on the phone, WhatsApp and form buttons are kept only as daily totals and do not identify the visitor. The contact page has no embedded map; the "Open in map" link opens Google Maps only if the visitor taps it |
| Requests from your website: the visitor's name, company, phone, e-mail, message, type of request and power information, the version of the privacy notice the visitor accepted and when, a keyed, irreversible hash of the IP address | To pass the request on to you. You are the controller for this data and I am the processor acting on your behalf; the visitor is informed by the privacy notice on your website. The visitor's name, company, phone, e-mail and message fields are stored on the server encrypted with AES-256-GCM, using the key used for your business data; the type of request, power information, the version of the accepted notice and the IP hash are not additionally encrypted. Only you see the requests (in the app and in the CSV export); the admin panel shows only their number. The notification sent to you contains no phone number, e-mail or message of the visitor. Requests are deleted automatically when the period you choose (6, 12 or 24 months; 24 by default) ends, and also when you delete the site or your account. The IP hash is used only to prevent abuse |
| Daily counter: random installation ID, platform (Android / iOS), operating system version, app version, app language, country code (from the app's own region setting), currency code, time zone, number of generators / machines / jobs / quotes; if the app crashes, a short crash signature (error type and code location, never the error text) and the crash count | To see that the app is working and the version distribution, and to give support; to show the right language and market statistics in my support and admin tools |
| Terms acceptance record: the version of the Terms of Use and Privacy Policy you accepted, the time of acceptance, the app version and the platform (iOS, Android, web) | To prove that you accepted the Terms and were informed by this policy. Deleted when your account is deleted. |
The daily counter contains no business data such as customer names, addresses or amounts; only the number of records is sent. The random installation ID is not an advertising ID and is not used for tracking. App language, country, currency and time zone are device and app settings, not location data: the country code comes from the app's own region setting; GPS and the IP address are not used for it. Retention periods are in section 7.
4. Advertising and tracking
JenUsta shows no ads, uses no advertising ID, does not track your behaviour and does not share your data with anyone for marketing purposes. No third-party analytics or crash-reporting service is used.
5. Service providers and transfers abroad
- netcup GmbH (headquartered in Germany; server in Austria, Vienna data centre) - hosts the JenUsta server; accounts, counters, support and synced business data are held on this server. Processor acting on my behalf; sub-processor for your business data.
- Google Firebase Cloud Messaging (USA and worldwide) and, for iPhone / iPad, the Apple Push Notification service (USA) - deliver notifications to your device; the device's notification token and the notification text are processed by these services. The notification text contains no personal data (see section 3).
- Cloudflare (USA and worldwide) - holds the DNS records of the domain names. The traffic of the app, the web app and the websites does not pass through Cloudflare; it goes directly to our server. Only the admin panel, which only I use, is currently behind Cloudflare's security service; the account data and support messages I see in the panel therefore pass through Cloudflare's network. This is being removed (see the table below).
- Anthropic (Claude API) (USA) - only translates the announcement and notification texts I write for all users. Your support messages and my replies are not sent; on the server, a text containing an e-mail address, a phone number, an IBAN or a digit sequence of 7 or more digits is refused and not sent. Processor acting on my behalf.
- Apple App Store and Google Play - sale, charging, renewal, cancellation and refund of the paid plans. The store carries out the payment under its own terms and on its own responsibility (as an independent controller); it passes the purchase information (section 11) on to me so that I can verify the purchase. For verification I send the store only the transaction ID the store itself issued.
- "Continue with Google" and "Continue with Apple" - you verify your account with your own Google / Apple account; this is between you and Google / Apple and subject to their privacy policies. The app then sends the identity token it receives from Google / Apple directly to the JenUsta server (Austria); the server checks it against Google's / Apple's public keys and issues its own session tokens. Firebase Authentication is not used: Google (Firebase) neither receives nor stores any account data from us for sign-in.
- Address lookup on your phone - when you tap "Get location", the phone's built-in service (Apple on iPhone, Google on Android) turns the coordinates into an address; this is between your phone and the operating-system provider, and the JenUsta server is not involved.
- RevenueCat (USA, former payment infrastructure) - removed. No data is sent to RevenueCat, and no call is made to RevenueCat when you delete your account either. The legacy event records left on our server from the old infrastructure are kept like purchase records (section 7).
Payment is made only through the store (Apple or Google); no other payment provider is used, and we neither see nor store your card details. I do not sell, rent or share your data with third parties beyond this; on a lawful request I may disclose it to the competent authorities to the extent the law requires.
Transfers abroad (KVKK Art. 9) and the situation today
Türkiye has issued no adequacy decision for these countries. For continuing transfers I therefore use, under KVKK Art. 9, the standard contract announced by the Turkish Personal Data Protection Board: both parties sign it and it is notified to the Personal Data Protection Authority within 5 working days of signing. Until these steps are complete, the safeguard under Art. 9 is not treated as complete. For providers where signing is not expected, I remove the transfer altogether. The table below shows the situation as it is today, honestly, and is updated with the date as each step is completed. (This is Turkish-law context; for EU/EEA and UK users, the GDPR safeguards in section 13 apply as well.)
| Recipient | What is sent | Basis | Status (21 November 2026) |
|---|---|---|---|
| netcup GmbH (server in Austria) | All data on the server | Standard contract: "controller to processor" for my own data, "processor to processor" for your business data | Both contracts prepared; netcup's signature and notification to the Authority pending |
| Google (Firebase Cloud Messaging) and Apple (notifications) | Notification token and notification text | The notification text carries no personal data; the notification token remains. Also to be written into the standard contract with Google | The notification text has carried no personal data since 18 November 2026; contract for the notification token pending |
| Cloudflare | Admin panel traffic only | Removing the transfer: the panel will be taken out of Cloudflare, and Cloudflare will hold only DNS records | The panel is currently behind Cloudflare; being removed |
| Anthropic | No personal data is transferred (only the announcement and notification texts I write for all users go) | Support messages are not sent; in future they are planned to be translated on my own computer with the browser's on-device translation | Support messages have not been sent since 18 November 2026 |
| Apple App Store, Google Play | The store's own transaction ID | The store is an independent controller; no new personal data of ours is sent | Sales are closed. This app version adds a token derived from the account ID to the purchase; our server does not read this token or write it to the purchase record; it may remain only in the raw content of store notifications, for 12 months (section 11). Before sales open, the token will also be removed from the app |
| RevenueCat | No data goes | Transfer removed | No calls are made to RevenueCat |
6. Purposes and legal bases
- Opening an account, sign-in, backup and sync of your business data, generator labels, My website, notifications, support and assigning the plan you bought to your account: establishment and performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6(1)(b)).
- Promotional notifications: explicit consent (KVKK Art. 5/1; GDPR Art. 6(1)(a)). You can withdraw it at any time with the switch under Settings > Promotions and announcements; withdrawal does not affect the lawfulness of earlier processing.
- Security, preventing abuse (for example account misuse, reopening a deleted account, obtaining the trial again on the same device, using a campaign code more than once), recording admin actions, debugging, version tracking, hourly usage and notification records: legitimate interest (KVKK Art. 5/2-f; GDPR Art. 6(1)(f)).
- Being able to show that deletion requests were fulfilled in time: establishment, exercise or protection of a right (KVKK Art. 5/2-e; GDPR Art. 6(1)(f)).
- Being able to prove that you accepted the Terms and were informed by this policy: establishment, exercise or protection of a right (KVKK Art. 5/2-e; GDPR Art. 6(1)(f)).
- Legal requests and obligations; keeping purchase records as tax and accounting law requires: legal obligation (KVKK Art. 5/2-ç; GDPR Art. 6(1)(c)).
- Requests from your website's visitors: you are the controller for this data and determine its legal basis; I process it only on your behalf (see section 3).
7. Retention
When you delete your account, your profile, your counter and usage records, notification records specific to you, your support messages, admin notes, your website with its requests and all synced business records and files are deleted from the server (see Delete account). When you delete an individual record, it is also deleted from the server through sync. When you sign out of the web app, the copy in the browser is deleted. While the account is open, the periods are as follows:
| Data | Period |
|---|---|
| Account and profile, business data and files | Until you delete your account |
| Sign-in identity (provider, account ID) | Until you delete your account |
| Sessions | Per device; they end when you sign out, remove the device, delete the account, or after 180 days without use (web app: 30 days); the record of an ended session is deleted 30 days later |
| Terms acceptance record | Until your account is deleted; deleted when the account is deleted |
| Support messages | 24 months; then deleted automatically |
| Daily counter and hourly usage records | 13 months; then deleted automatically |
| Notification records | 12 months; then deleted automatically |
| Website requests | The period you choose (6, 12 or 24 months); 30 days after you delete the site |
| Website | If you delete the site it goes offline at once and is deleted with its content and photos 30 days later; its address is not given to anyone else for a further 30 days |
| Daily scan counts of QR labels and rate-limit counters | 30 days |
| Raw content of store notifications | 12 months; then the content is emptied and only the record of the event remains |
| Purchase records | 10 years from the end of the calendar year of the last transaction; then deleted automatically (section 11) |
| Server logs (including IP address) | Short: for each application component, old entries are rotated out once about 30 MB is reached |
| Server backups (encrypted) | Deleted within 30 days at the latest, as backups rotate |
What remains after the account is deleted. These contain no name, e-mail or phone number; the one exception is the e-mail address in a deletion request received by e-mail:
- Admin action records: their personal content is blanked; only the type of action, its date and the account ID remain. The record is deleted 10 years after the action.
- A sha256 hash of your sign-in identity: to prevent a blocked account from escaping the block by being deleted and reopened with the same Google / Apple account, and to prevent the 14-day trial from being obtained again by deleting and reopening an account. The hash is irreversible but not anonymous; it is a pseudonym: anyone who knows the same sign-in identity can match it. It contains no name, e-mail or phone number. It is deleted 3 years after the account is deleted. If you used a campaign code, the same hash also remains for that code: it is deleted once 3 years have passed since the code was used and the code has been disabled or has expired. While the code is still valid, the hash may stay longer than 3 years, to prevent the same person from using the code a second time.
- The trial device key and a keyed hash (pseudonym) of the ID of the account that took the first trial on that device: when the account is deleted, the account ID is replaced by this hash. The record is deleted 3 years after the first trial on the device.
- If you sent an account deletion request by e-mail or another route: the request record and your e-mail address, to be able to show that the request was fulfilled. 30 days after the request is closed, at the next monthly cleanup (at most about two months), the e-mail address is replaced by its sha256 hash and the request notes are deleted. This hash is also a pseudonym: anyone who knows the address can match it. The record is deleted 10 years after the request is closed. A request that is still open is not changed.
Expired records are deleted automatically by a cleanup that runs at the start of every month, so a record can stay up to one more month after its period has expired. Data on your phone is under your control.
8. Security
All communication with the server is encrypted with HTTPS; business data, files and the contact fields of requests from your website (name, company, phone, e-mail, message) on the server are additionally encrypted at rest with AES-256-GCM. At sign-in the Google / Apple identity token is checked once against their public keys; after that the server verifies every request with a short-lived (15 minutes) session token that it issues itself, and stores the long-lived renewal token only as an irreversible hash; each user can reach only their own records. The admin panel is accessed with two-step verification. An encrypted backup of the database is taken every night. To protect the data on your phone, I recommend setting a screen lock on your device and keeping your backups in a safe place.
9. Your rights (KVKK Art. 11)
You have the right to learn whether your data is processed, to request information, to have it corrected, deleted or destroyed, to learn to whom it was transferred, to object, and to claim compensation for damage. Send your request to destek@jenusta.com from your registered e-mail address; it is answered within 30 days at the latest. If you are not satisfied with the answer, you keep the right to complain to the Turkish Personal Data Protection Board (Kişisel Verileri Koruma Kurulu). Rights under the GDPR are described in section 13.
10. Children
JenUsta is intended for businesses and is not offered to anyone under 18.
11. Purchase and subscription data
If you buy the PRO or the PRO + Web Sitesi (PRO + Website) plan, payment is made through the Apple App Store or Google Play. The store processes the payment and the card details; I do not see or store your card number, payment method or billing details.
Only the following reaches me from the store and is stored on our server (netcup, Austria):
- the store (App Store or Google Play) and the product (plan and period);
- the store's transaction ID or purchase token;
- purchase, renewal and end dates; the subscription status (active, cancelled, expired, refunded);
- the price, the store country and currency.
Account token: this version of the app adds a token derived from your account ID to the purchase and sends it to the store. The token contains no name or e-mail but is not anonymous; it is a pseudonym. Our server does not read this token, does not use it to link the purchase to your account and does not write it into the purchase record: the purchase is linked to the JenUsta account in which it is first verified. The token may appear only in the raw content of store notifications; that content is deleted after 12 months (section 7).
Purpose: to assign the plan you bought to your account, to switch your access on phone, tablet and computer on and off, to follow renewal, cancellation and refunds, to prevent the subscription from being used on another JenUsta account, and to comply with tax law.
Legal basis: establishment and performance of a contract (KVKK Art. 5/2-c; GDPR Art. 6(1)(b)); legal obligation for keeping the records as tax and accounting law requires (Art. 5/2-ç; GDPR Art. 6(1)(c)).
Stores: Apple and Google process the purchase under their own terms and on their own responsibility (see section 5). Before sales open, sending the account token to the store will also be removed from the app; the store will then receive only its own transaction ID.
Retention: only the purchase records (transaction ID, product, dates and status) are kept for 10 years as tax and accounting law requires (Turkish Tax Procedure Law Art. 253, Turkish Commercial Code Art. 82). The period runs from the end of the calendar year of the last transaction; records whose 10 years are over are deleted automatically. When you delete your account, these records are kept only for this obligation; the account link in the record (account ID and any legacy account token) is deleted. Deleting your account does not cancel your subscription in the store; cancel the subscription separately in the store (see the Terms of Use and Subscription Terms).
My website: if you are on the PRO + Web Sitesi plan, the content of your site and the requests from visitors are processed as described in section 3. When the subscription ends, your site goes offline and is not deleted; the deletion rules are in section 7.
12. Changes
If this policy changes, it will be published on this page and the date updated. For important changes you will be informed in the app.
13. GDPR information (EU/EEA and UK)
This section applies if you use JenUsta from the EU/EEA or the UK. It contains the content of the Turkish KVKK information notice (KVKK Aydınlatma Metni, available in Turkish only) and the additional information required by the GDPR.
- Controller: for your account and purchase data, Enes Aktaş, destek@jenusta.com. For the business data you enter in the app (including your customers), you are the controller; Enes Aktaş is the processor who stores it on your behalf and processes it only to provide the service. The duty to inform your customers lies with you. The same applies to the requests your website's visitors send.
- Data processed: name, e-mail, business name, province, optional business phone, account ID, provider and provider account ID (Google / Apple), session records (device ID, platform, time created and last used), trial end date, access status, random installation ID, platform and version information, record counts, app language, country code, currency code, time zone, crash signature and count, notification token, IP address of the connection. In addition, your business data (customer name, address, phone, location, generator, job, payment, rental and quote records, photos and signatures) and your business details (address, tax office / number, IBAN, account holder, logo, signature) are stored on our server, encrypted with AES-256-GCM, for backup and sync; not end-to-end encrypted, access restricted, the admin panel does not show this data. If you buy a paid plan, your purchase data is processed too (store, product, the store's transaction ID or purchase token, dates, subscription status, store country and currency; no card details; see section 11). Also: your support messages and, if you use My website, the website content (public) and the requests from your visitors (see section 3).
- Purposes: creating and managing your account, backing up your business data and syncing it between phone and web app, publishing your website and passing on visitor requests, sending notifications, giving support, assigning the plan you bought to your account and managing your access, ensuring security, meeting legal obligations (for example tax records).
- Legal bases: performance of a contract (Art. 6(1)(b) GDPR; including assigning the plan you bought to your account), legal obligation (Art. 6(1)(c); keeping purchase records as tax and accounting law requires), legitimate interest (Art. 6(1)(f)), as set out per purpose in section 6.
- How data is collected: Google / Apple sign-in details, for a purchase the purchase information that comes from the Apple App Store / Google Play, the profile and business details you enter yourself in the app, the daily counter the app sends automatically, and the requests visitors send through your website.
- Recipients: JenUsta server (netcup GmbH, headquartered in Germany; server in Austria, Vienna data centre, EU), Cloudflare (DNS records; the admin panel traffic, being removed), Apple App Store and Google Play (sale, charging and refund of the paid plans; we never see your card details), Anthropic (translation of announcement and notification texts only; support messages are not sent), Google (Firebase Cloud Messaging, Google sign-in, address lookup on Android) and Apple (Apple sign-in, Apple Push Notification service, address lookup on iPhone), to provide the service. Not sold and not passed on for marketing.
- Data location: the server holding your account, the daily counter and the synced business data is run by netcup GmbH (headquartered in Germany) and is in Austria, Vienna data centre (EU); business data is stored there encrypted. I operate the service from Türkiye; the admin panel I use for this does not show business data.
- International transfers: the server is in the EU, but Google, Apple, Cloudflare and Anthropic may process data on servers outside the EU/EEA, in particular in the USA. These transfers rely on the EU adequacy decision for the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the EU standard contractual clauses in the providers' data processing terms; for the UK, on the corresponding UK safeguards (UK Extension to the Data Privacy Framework or the UK Addendum). You can ask for a copy of these safeguards by e-mail.
- Retention: until you delete your account. Deleting the account also deletes all synced business records and files (Delete account); the exceptions are described in section 7. Purchase records (transaction ID, product, dates, status) are kept for 10 years as tax and accounting law requires (Turkish Tax Procedure Law Art. 253, Turkish Commercial Code Art. 82); this applies only to these records. Retention periods per data type and what remains after deletion are in section 7.
- Your rights: under Art. 15-22 GDPR you have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interest (Art. 21). Art. 22 (automated individual decisions) does not apply: no decision with legal or similarly significant effect is made solely by automated means. Where you gave consent, you can withdraw it at any time (Art. 7(3)). Within the app you can delete your account and share a backup file yourself. To use your rights, write to destek@jenusta.com from your registered e-mail address; you receive an answer within one month. For complex requests this period can be extended by two further months; you will then be told why (Art. 12(3) GDPR).
- Right to complain: you have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU/EEA member state where you live or work or where the alleged infringement took place (Art. 77 GDPR); for the UK, the Information Commissioner's Office.
- Provision of data: the account data is needed to open and use an account; without it the service cannot be provided.
See also: Terms of Use and Subscription Terms.