Privacy policy

The CariX platform is operated by Appy Solutions EOOD, a company registered in Bulgaria, registered office: ul. Ivan Susanin 45, vh. A, et. 3, ap. 9, Sofia 1618, Bulgaria, UIC (EIK) 206612061, VAT No. BG206612061 (“CariX”, “we”).

For any question or request about your personal data, write to us at privacy@carix.app.

• CariX is the controller for account data, driver profiles and cars, reviews, contact and feedback messages, security and statistics.
• The shop you choose is an independent controller for the data you send it in a booking request and for its own records (customers, jobs, estimates, invoices). For this data you can also contact the shop directly.
• For the data shops enter in the CariX dashboard (customers, cars, jobs, estimates), CariX is the shop's processor: we store and process it only to provide the service, following the shop's instructions.
• Fiscal invoicing: for a shop's fiscal invoices, issued through CariX invoicing or through its own invoicing program, the shop is the controller and CariX is its processor. Details in Fiscal invoicing for shops.
• Reminders from your car service: if a car service that uses CariX has turned on automatic reminders, we may email you on its behalf about your ITP (roadworthiness test), servicing, the seasonal tyre change or the end of a job's warranty. We use only data the service already holds about you: your name, email address, car (make, model, plate), ITP expiry date, and the dates of jobs and warranties. For these emails the service is the data controller and CariX is the processor that sends them. Every email has an unsubscribe link: one click and a confirmation stop that service's reminders, without affecting your account or booking messages.
• Tyre hotel: when you leave your tyres at a shop that uses CariX, the shop records the set (season, brand, size, DOT, quantity, rims, tread depth, shelf, label), photos of the set and internal notes, linked to your customer record and to the car in its records. The shop is the controller of this data; CariX hosts it on the shop's behalf, photos are kept private and are deleted together with the set. If you booked that shop through CariX for a car with the same licence plate, your account shows where your tyres are on that car's page (shop, season, size, shelf). Your data export includes the sets stored for your cars, without the shop's internal notes and without photos.

• Account data: name, email, phone (if you add it), whether you added a repair shop or another car business to the account, language (the one you last used CariX in, so we can send you emails in that language), the date you accepted the terms, your marketing preference and your profile photo, if you have one: you upload it, or, if you sign in with Google or Facebook, we take it from them at each sign-in. The photo is seen only by the other CariX users you deal with (the shops you booked with, the people you share a car with), never publicly. You can hide or delete it in Settings, and it is deleted with your account.
• Sign-in codes: we use no passwords. You sign in with a one-time 6-digit code that we email to your account address; you also confirm the deletion of your account with such a code. We do not keep the code itself, only a fingerprint of it (a hash computed with a secret key), together with the email address, the expiry time and the number of tries. A code is valid for 10 minutes and can be used only once.
• Signing in with Google, Apple or Facebook: if you choose to sign in this way, we keep, linked to your CariX account, the provider, the identifier of your account with it and the email address it gave us, plus the date it was connected and last used, so we recognise you next time. We delete them when you disconnect the provider in Settings or delete your account. If Google or Facebook has a profile photo of you, we copy it at each sign-in with them and when you connect them in Settings, and use it as your CariX profile photo unless you have hidden it; Apple gives us no photo. When you sign in this way in the CariX app, we keep a one-time code (only its cryptographic fingerprint), linked to your account, for 2 minutes to open the session in the app; expired codes are deleted daily.
• Driver profile and cars: city and gender (optional), licence plate, make, model, year, VIN and mileage if you add them, expiry dates for the roadworthiness test (ITP), mandatory and comprehensive insurance (RCA, CASCO) and road toll, and the documents you upload (for example, your insurance policy).
• My documents and other deadlines: if you add them, the type of your documents (driving licence, ID card, passport, medical and psychological certificates, professional certificates, tachograph card), licence categories, issue and expiry dates, your notes and, optionally, a photo or PDF of the document, stored privately and visible only to you; we don't keep document numbers. For cars we also keep the first-aid kit and fire extinguisher expiry dates, the year you marked the vehicle tax as paid and whether you want tyre reminders.
• Free period: the free months granted to your account and your shop (at sign-up, through invites or by the CariX team), with their dates, the account that added the shop, and the notices sent before the period ends.
• The "Invite and get free months" programme: your invite code and, when someone signs up through your link, who invited whom, the sign-up date, the invite status (pending, qualified, rejected, expired), the reason for a rejection and the months granted. The browser remembers the link for 30 days through the necessary cookie carix-invite. The person who invites never sees the invited person's name or email, only whether they joined as a driver or as a shop, and the invite status.
• Fill in from a photo: when you tap "Fill in from a photo", the photo or PDF of the document (RCA, CASCO, ITP, rovinietă, registration certificate, driving licence, identity card) is sent to Anthropic, which reads it with the Claude model only to fill in the form. Before sending, the photo is resized in your browser and its metadata (including location) is removed. CariX keeps neither the photo sent for reading nor the details read: they only go into the form, and you decide what to save.
• The CariX app (Android and iOS): if you turn on app notifications, we keep for each phone a notification identifier (FCM token), the platform, the app version, the date you turned them on and the date it was last used, to send you the reminders, alerts and booking updates you chose. Notifications go through Google Firebase Cloud Messaging and, on iPhone, through Apple's notification service. The identifier is deleted when you sign out on that phone, turn notifications off, delete your account, or when Google tells us it is no longer valid. Your data export lists your phones (platform, version, dates) without the identifier. Location and camera are used only when you ask (parking, accident, documents) or, if you turn on automatic parking, when the phone leaves the car, with the phone's permission.
• Where I parked: when you tap "I parked here", your phone's exact position at that moment (with its accuracy) and, if you add them, the car, a note, a photo and the time your paid parking runs until. We never track your position in the background or take it without that tap, except for automatic parking below, if you turn it on. Only you see your saved spots; we do not share them with shops or partners.
• Automatic parking (only in the CariX app, if you turn it on): when your phone disconnects from the car's Bluetooth or CarPlay or, on Android, when Android Auto ends, the app notes the time and, if the phone has it, the position, and saves them as a parking spot, just like "I parked here", with the car chosen in the settings. The Bluetooth device you choose stays only on your phone; we don't send it to our servers. We don't ask for background location access. Spots are deleted after 30 days.
• OBD reading (only in the app, when you start it): the app connects over Bluetooth to the OBD adapter in your car and reads the mileage and trouble codes. On Android, classic-Bluetooth adapters paired in the phone's settings work too; the list of paired devices is read only on the phone and never sent to us. The mileage is saved to the car's history only when you tap "Save km". For explanations we send Anthropic only the trouble codes (for example P0301) and the language, with no name, car, plate or other personal data; explanations are stored per code, for all users, not per user. We don't keep the reading itself.
• Your car's mileage: the odometer readings you add, the ones taken from shop jobs and from costs, the ones read from the car with an OBD adapter, if you save them, and your answers to the monthly email question ("How many kilometres does the car have?"), each with its date. From them we work out the monthly average and the estimated date of deadlines set at a number of kilometres. You can turn the monthly question off in settings or from the link in the email.
• Car expenses: if you add them, the type, amount, date, mileage, note and, for fuel, the litres. From them we work out the totals, fuel consumption (l/100 km) and cost per kilometre, which only you see.
• Service recalls: when a manufacturer or an authority (for example RAR) announces a recall campaign for your car's make, model and year, we link it to the car in your account, show it on the car page and send you a single email if email notifications are on. We keep only the link between the campaign and the car, when we emailed you and when you marked it done or not applicable.
• Shared cars: if you give someone access to a car, we keep the email address you invited, the invite date and the date it was accepted. People with access see the car's documents, reminders, expenses, mileage, warranties and recalls, can add expenses, documents and mileage, and get the car's reminders according to their own notification settings. They don't see your personal documents or your accident reports. You can remove access at any time, and an invited person can leave at any time. Invites that aren't accepted expire after 14 days.
• After an accident: if you fill in a report, the date and place of the accident (your phone's position only if you tap the button, and the address), the car, the description, whether anyone was injured, whether you called the police or filled in the joint accident report, the photos (with their time and, if you allow it, the place) and what you note about the other driver: name, phone, licence plate, insurer, policy number. Only you see the report, and you can download it as a PDF to send to your insurer; we never send it to anyone.
• Partner buttons and roadside assistance: when you tap a partner button (for example rovinietă, RCA, parking), we go through carix.ro/go and count only the click: which link and from which part of the app; these statistics store neither who you are nor your IP address. You pay on the partner's site, under its own privacy policy. A roadside assistance number you add to an RCA or CASCO policy is kept with the car's documents so we can show it on the car page.
• Booking requests and jobs: the shop chosen, the requested service, date and time, the description of the problem, the status of the request, and after the job the estimate, the warranty on parts and labour, job status and photos uploaded by the shop.
• Reviews: the rating, the text, the shop's reply and any reports.
• Shop data: company name and identification details, address, contact details, opening hours, services and indicative prices, photos, and the details of the person managing the account. For the CariX plan, the shop's VAT ID: we send it to the European Commission's VIES service to confirm it is valid (reverse charge), and we keep the result of the check and its date.
• Messages: data sent through the contact form (name, email, subject, message) and through the feedback button (the message, its type, the rating and screenshot if you add them, your email if you are not signed in, plus the page, browser, operating system, screen size, time zone and technical errors on the page).
• Technical and security data: IP address, browser type, date and time of access, sign-in sessions and server logs.
• Usage statistics, only with your consent: pages visited and interactions with the site, collected through Google Analytics 4, and what you do on the home page, counted by us without cookies and without any way to recognise you (see our Cookie policy).
• Statistics for listed businesses, only with your consent: if you accepted “Analytics”, we count visits to a business's public profile and clicks on its phone, website and directions, to calculate the business's fees and its monthly report. We do not keep your IP address or browser details: from them, together with the date, we compute a cryptographic code that changes daily, only lets us count the same visitor once a day and is deleted after 2 days; the code cannot be linked to you. We also keep only the approximate country, the date, the type of action and the page you came from (search, category or profile).

We do not need special categories of data (for example, health data); please do not include them in descriptions or messages.

A shop chooses in Settings → Fiscal invoicing how it issues its fiscal invoices: through CariX invoicing, through its own invoicing program or not from CariX at all. For the data on the invoices, the shop is the controller and CariX is its processor (Art. 28 GDPR). If you are a shop's customer, you can also contact the shop directly.

• CariX invoicing (only for shops in Romania): CariX prepares the invoice in the shop's name, under the shop's own series and numbering, renders the PDF and the e-Factura XML file (UBL, CIUS-RO) and uploads the XML to ANAF, the Romanian tax authority, in the e-Factura system (SPV). We keep the invoice (the shop's and the buyer's details, the lines, the VAT, the amounts), the PDF, the XML and ANAF's answers (the message signed by ANAF, or the errors). If the shop chooses, we email the PDF to the buyer.
• The buyer's details: name or company name, address, email and the phone from the customer's record, if there is one, and for companies the tax ID (CUI) and trade register number. For a private person, the personal identification number (CNP) is asked for only when the shop invoices with CariX invoicing; it is optional and is added only if the buyer asks for it. We store it encrypted and show it only masked (the last 4 digits). It appears only in the e-Factura XML: at ANAF and in the invoice files the shop receives (the XML in the accountant export and the one behind the link sent by webhook). It never appears on the PDF and we never send it to invoicing programs, in the SAGA file or in webhook data.
• Billing details filled in by the customer: on the public estimate approval page, the customer can fill in their own invoice details, as a private person or as a company. They are saved as the customer's billing profile at that shop, so they need not be typed again.
• Lookup by tax ID: when the shop or the customer types a company's tax ID (CUI), we send it to ANAF's public web service and take the company's public details from there (name, address, whether it pays VAT, whether it is registered in e-Factura).
• ANAF authorisation: to send invoices to e-Factura, the shop authorises us at ANAF (OAuth), with its own account and digital certificate; the certificate never reaches us. We store encrypted the access token (valid for about 90 days, renewed automatically) and the refresh token (about 365 days, after which the shop authorises again), together with the tax ID and the authorisation details. Sending invoices and checking ANAF's answers run automatically every 5 minutes. The shop can disconnect ANAF at any time in Settings; the authorisation in SPV ends when it expires or when the shop removes the CariX app in SPV.
• The shop's invoicing program (SmartBill, Oblio, FGO, Keez, factureaza.ro): if the shop connects its account, we store its API access details (for example, the email and API key) encrypted and use them only to issue the invoices the shop asks for. The program receives the buyer's details (name or company name, tax ID and trade register number for companies, address, city, county, email, phone), without the CNP, and the estimate lines; the program sends the invoice to e-Factura. The program is an independent provider of the shop and works under the contract between them. CariX keeps a copy of every invoice issued this way (the buyer, the lines, the amounts, the series, the number and the link), for the invoice register, the accountant export and webhooks; the copy holds no CNP.
• The shop's billing details: company name, tax ID, trade register number, address, IBAN and bank, share capital, whether it pays VAT, its invoice series and its accountant's email address.
• Accountant export: every month, if the shop has set its accountant's address and has not turned the monthly export off, we email the accountant a signed link to a ZIP archive with last month's invoices: the register (CSV and Excel) and, for the invoices issued with CariX invoicing, also the PDFs, the XML files, ANAF's answers and an import file for SAGA. The link is valid for 14 days. The shop can also ask for an export of another period.
• Webhooks: if the shop sets web addresses (URLs), we send them the data of invoicing events (estimate approved, invoice issued, accepted or rejected by ANAF, paid or reversed), signed with HMAC-SHA256. The data covers the shop, the invoice or estimate (the lines, the amounts, the car's plate number, the customer's name) and the buyer (name, tax codes, address), without the CNP and without the phone, and, for invoices, links to the PDF and XML valid for 7 days. If the address does not answer, we retry for up to 24 hours.
• "Your program isn't listed?" requests: the name of the invoicing program, its website, the notes and the country, together with the shop and the account that sent the request. We use them only to decide which programs we connect next.

• Creating and managing your account, including sign-in with a code sent by email

  Data

  account data, sign-in codes

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• Sending your booking request to the chosen shop and messages about the booking

  Data

  account data, car, request

  Legal basis (GDPR)

  performance of a contract and steps taken at your request before entering into a contract with the shop – Art. 6(1)(b)

• Driver account features: cars, your own and your car's documents, expiry reminders (including the vehicle tax and tyre changes)

  Data

  profile, cars, documents, my documents

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• The management dashboard for shops

  Data

  shop data, customers, jobs, estimates

  Legal basis (GDPR)

  performance of the contract with the shop – Art. 6(1)(b); for customer data, CariX is a processor (Art. 28)

• Shops' fiscal invoices: CariX invoicing and sending to e-Factura, the link with the invoicing program, the register, the accountant export, webhooks and the lookup by tax ID

  Data

  the shop's billing details, the buyer's details (including the CNP, if given), the lines and amounts, ANAF's answers

  Legal basis (GDPR)

  for the shop, its legal obligation to issue and transmit invoices – Art. 6(1)(c); CariX processes the data on the shop's behalf, as its processor (Art. 28), and under the contract with the shop – Art. 6(1)(b)

• "Your program isn't listed?" requests, to decide which invoicing programs we connect

  Data

  the program's name, website, notes, country, the shop and the account that sent the request

  Legal basis (GDPR)

  legitimate interest – Art. 6(1)(f): building the connectors shops ask for

• Asking for a review after a completed job and publishing reviews

  Data

  display name, rating, text

  Legal basis (GDPR)

  legitimate interest – Art. 6(1)(f): genuine reviews for other drivers

• Answering contact and feedback messages; automatic classification of feedback

  Data

  messages, technical data

  Legal basis (GDPR)

  legitimate interest – Art. 6(1)(f): replying to you and improving the platform

• The account's free period and the notices before it ends

  Data

  account data, free months

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• The "Invite and get free months" programme: granting the months and preventing self-invites (at sign-up we compare the email address and the device cookie with those of the person who invited)

  Data

  account data, invite data, the carix-invite and carix-device cookies

  Legal basis (GDPR)

  performance of a contract (the programme rules) – Art. 6(1)(b); for fraud prevention, legitimate interest – Art. 6(1)(f)

• "Where I parked": saving where you left the car, walking directions back to it and, if you start the timer, one notice before your paid parking runs out

  Data

  the exact position at the moment you tap the button (for automatic parking, at the moment the phone leaves the car), the car, the note, the photo, the time the parking is paid until

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• Your car's mileage and expenses: the monthly average, fuel consumption, cost per kilometre, the estimated date of deadlines set at a number of kilometres and the monthly email question

  Data

  odometer readings and their dates, expenses (including litres), the car, your email

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• The accident report: the steps to follow, your own record and the PDF for your insurer

  Data

  the report details, the photos, the position (if you tap the button)

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• The other driver's details in your accident report, so you can make your claim

  Data

  the other driver's name, phone, licence plate, insurer and policy, as you note them

  Legal basis (GDPR)

  legitimate interest (yours, for your insurance claim) – Art. 6(1)(f)

• Shared cars: the email invite, access to the car and the car's reminders sent to people with access

  Data

  the invited email, the inviter's name, the car, the invite and acceptance dates

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• Service recalls: linking campaigns to your car, showing them and a single email per car

  Data

  the car's make, model and year, your email, when we emailed you and the recall's status

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• Filling in a form from a photo of a document, only when you tap the button

  Data

  the photo or PDF of the document and the details on it

  Legal basis (GDPR)

  performance of a contract – Art. 6(1)(b)

• Security and abuse prevention (for example, limiting sign-in attempts)

  Data

  technical data

  Legal basis (GDPR)

  legitimate interest – Art. 6(1)(f)

• Refusing a new free period or invite rewards after an account or a shop was deleted

  Data

  a fingerprint (hash) of the email address and, for a shop, of the fiscal ID and VAT ID; for a shop added again to the same account, the fact that the deleted shop was added by that account

  Legal basis (GDPR)

  legitimate interest – Art. 6(1)(f)

• Usage statistics (Google Analytics 4 and our own home page statistics)

  Data

  usage data; cookie identifiers, for Google Analytics only

  Legal basis (GDPR)

  consent – Art. 6(1)(a) GDPR and Art. 5(3) of Directive 2002/58/EC (in Romania, Art. 4(5) of Law No. 506/2004)

• Statistics for listed businesses: visits and clicks on a business's profile, for its fees and monthly report

  Data

  the type of action, the date, the approximate country, the page you came from and a daily code computed from the IP address and browser, without keeping them

  Legal basis (GDPR)

  consent – Art. 6(1)(a) GDPR

• Checking the shop's VAT ID in VIES, for the CariX plan

  Data

  the VAT ID, the result and date of the check

  Legal basis (GDPR)

  legal obligation – Art. 6(1)(c) (the VAT rules on reverse charge)

• Invoices and credit notes for the CariX plan, issued by Appy Solutions EOOD

  Data

  name or company name, address, country, email, tax ID and VAT ID, the plan, the period, the amounts, the VAT and the payment identifiers

  Legal basis (GDPR)

  legal obligation – Art. 6(1)(c) (the Bulgarian Accountancy Act and the VAT rules)

• CariX news and offers by email

  Data

  name, email

  Legal basis (GDPR)

  consent – Art. 6(1)(a), given separately at sign-up

• Complying with legal obligations (for example, requests from authorities)

  Data

  the data needed in each case

  Legal basis (GDPR)

  legal obligation – Art. 6(1)(c)

Where we rely on legitimate interest, you can object at any time (see Your rights). You can withdraw consent at any time without affecting earlier processing: for statistics in Cookie settings, and for marketing by writing to privacy@carix.app or using the unsubscribe link in the email.

We do not sell personal data. We share it only with:

• the shop you choose, when you send it a booking request: your name, phone, email, car, requested service and description;
• the public, for reviews (with a shortened display name) and shop profiles; a car passport becomes visible to anyone with the link only if you choose to make it public; it shows the mileage history (mileage recorded by shops at jobs, with the shop's name, and separately the mileage you declared), without your name or contact details;
• public authorities, only where the law requires it;
• the European Commission (the VIES service), only the VAT ID of a shop buying a CariX plan, to check that it is valid;
• ANAF, for shops that use CariX invoicing: the e-Factura XML of each invoice, with the buyer's details, on the shop's instruction and for its legal obligation; we also send ANAF a company's tax ID, to take its public details;
• the invoicing program the shop connected (SmartBill, Oblio, FGO, Keez, factureaza.ro), an independent provider of the shop: the invoice data, without the CNP, on the shop's instruction;
• the accountant the shop names: the link to the monthly invoice export;
• the web addresses the shop sets (webhooks): the data of invoicing events, without the CNP and without the phone;
• providers that help us run the platform (processors), under contracts in line with Art. 28 GDPR:

• Vercel Inc.

  What it does

  application hosting

  Details

  EU region (Frankfurt); US company

• Supabase

  What it does

  PostgreSQL database

  Details

  hosted in the EU (Frankfurt)

• Cloudflare (R2)

  What it does

  file storage: car documents, your personal documents, parking spot photos, accident report photos, profile photos, job photos, photos of tyres stored at a shop and the files of shops' fiscal invoices (PDF, XML, ANAF's answers, accountant exports)

  Details

  private storage in the EU jurisdiction; US company

• Resend

  What it does

  sending transactional emails

  Details

  US company

• Google (Google Analytics 4)

  What it does

  usage statistics, only with your consent

  Details

  Google Ireland Limited; data may reach Google LLC (USA)

• Anthropic

  What it does

  automatic classification of feedback messages, reading documents for "Fill in from a photo" and explaining OBD trouble codes (the codes only)

  Details

  US company

• Google (Firebase Cloud Messaging)

  What it does

  sending notifications in the CariX app, only if you turn them on

  Details

  Google Ireland Limited; data may reach Google LLC (USA)

• Apple (Apple Push Notification service)

  What it does

  delivering the app's notifications on iPhone

  Details

  Apple Distribution International (Ireland); data may reach Apple Inc. (USA)

• BulkGate

  What it does

  sending text messages, only if the feature is switched on

  Details

  EU company

• Stripe

  What it does

  online payment processing

  Details

  not active at launch; receives no data

The application and the database are hosted in the EU (Frankfurt). Some providers are US companies (Vercel, Cloudflare, Resend, Google, Apple, Anthropic) and may process data outside the European Economic Area. In those cases the transfer relies on the European Commission's adequacy decision for the EU-US Data Privacy Framework, for certified providers, or on the standard contractual clauses approved by the European Commission (Art. 46 GDPR), together with additional security measures. You can ask for information about these safeguards at privacy@carix.app.

• Your account and related data: while the account is active and for 30 days after it is deleted; then we delete or anonymise it.
• Invoices and credit notes for the CariX plan (name, address, country, email, tax ID): 10 years from issue, as accounting records required by the Bulgarian Accountancy Act, even if you delete your account.
• The fingerprint of a deleted account: after an account is deleted we keep an irreversible cryptographic fingerprint (hash) of its email address (and, for a shop, of its fiscal ID and VAT ID), only to refuse a new free period or invite rewards when someone signs up again. The address or the ID cannot be recovered from it. We keep it with no time limit.
• Deleting a shop: only the owner can delete it, from Settings, after confirming the shop's name and a code sent by email, and choosing whether to keep their account or delete it too; before that they can download the shop's data (a JSON file). The public profile, the search listing and online booking disappear at once, for the shop and its branches; future bookings are cancelled and the drivers are told. While future bookings paid online exist, the shop can't be deleted: it cancels and refunds them first. Jobs, estimates and km readings that concern a driver with a CariX account stay in that driver's account, with the shop's name, as part of their car's history; for these we keep the shop's name, city, country and fiscal data. After 30 days we erase the rest of the shop's file for good: clients without a CariX account and their cars, their bookings, jobs that concern no CariX driver (with parts, photos, estimates and reviews), internal notes, the tyre hotel (the sets a CariX driver sees stay in their account, without the shop's notes and photos), reminders sent to the shop's clients (a CariX driver's own reminders stay), the team and the shop's contact details. We keep the fingerprint (hash) of the shop's fiscal ID and VAT ID. We keep the fingerprint of the owner's email only if they delete their account too. If they keep the account, our record of free months keeps the fact that the deleted shop was added by their account, so a shop added again to the same account gets no free months, however much time passes. What happens to the shop's fiscal invoices is explained below, under "Shops' fiscal invoices". The invoices Appy Solutions EOOD issued for the shop's CariX plan are kept for 10 years.
• Shops' fiscal invoices (issued through CariX invoicing, or the copies of those issued from the invoicing program), with the PDF, the XML and ANAF's answers: as long as the shop exists in CariX. The obligation to archive them for the period the law requires is the shop's; CariX is only its tool. When a shop is deleted, we email the owner (and the accountant, if set) an export of all its invoices, keep them for another 90 days, then delete them with their files. An invoice issued from the invoicing program also stays in that program, under its own rules.
• The ANAF authorisation (SPV tokens) and the invoicing program's access details: until the shop disconnects ANAF or the program, or deletes the shop. On deletion, the program's access details are deleted at once, and the ANAF tokens also at once or, if an invoice is still on its way to e-Factura, once it gets there, and at the latest after 90 days.
• Billing profiles of a shop's customers (including the encrypted CNP): as long as the customer is in the shop's records; they are deleted together with the customer and, when the shop is deleted, together with the rest of its file, after 30 days.
• "Your program isn't listed?" requests: as long as the shop exists; when the shop is deleted, they are deleted together with the rest of its data, after 30 days.
• Accountant exports: the link in the email is valid for 14 days, and the ZIP archive is deleted after 90 days.
• The webhook log (the event sent and the answer received): 30 days from the event.
• Booking requests and jobs: shops keep them as their own records, for the period they set and their legal obligations require; from your driver account they disappear together with the account.
• Sign-in codes: a code's record is deleted within two days after the code expires.
• Profile photo: while you keep it in your account; you can delete it at any time in Settings, and it is deleted at once when you delete your account.
• Saved parking spots and their photos: 30 days, or less if you delete them or close your account.
• Odometer readings: as long as the car is in your account. The ones you added (by hand, from the monthly question or from the OBD adapter) you can delete at any time, and those from expenses together with the expense. Readings a shop recorded at a job stay with the shop's job. When you close your account, the ones you gave are deleted at once.
• Invites and access to shared cars: while the access is active; an invite nobody accepted is deleted 30 days after it expires, and removed access within 30 days. All of them are deleted with your account or the account of whoever gave the access.
• Recalls linked to your cars: as long as the car is in your account; they are deleted with the car or the account.
• The log of reminders sent by car services: at most 24 months after sending (type, car and date), so the same message is never sent twice.
• App notification identifiers: until you sign out or turn notifications off; a phone not used for 270 days is deleted automatically.
• Accident reports and their photos: while the account is active; we do not delete them automatically, because an insurance claim can take a while. You can delete them at any time, and they are deleted at once, with the other driver's details, when you close your account.
• Server logs: at most 30 days.
• Messages sent through the contact form: at most 12 months.
• Feedback: at most 24 months.
• Our own home page statistics: at most 12 months.
• Statistics for listed businesses: the daily code is deleted after 2 days, and the visits and clicks after at most 24 months.
• Cookies: as set out in our Cookie policy.

We may keep some data longer only where the law requires it or to establish or defend legal claims, for as long as necessary.

• right of access – to know what data we hold about you and get a copy (Art. 15);
• right to rectification – to correct inaccurate or incomplete data (Art. 16);
• right to erasure – to ask us to delete your data (Art. 17);
• right to restriction – to ask us to limit processing in certain cases (Art. 18);
• right to data portability – to receive your data in a structured format and pass it to another controller (Art. 20);
• right to object – to processing based on legitimate interest and, at any time, to direct marketing (Art. 21);
• right to withdraw consent at any time, without affecting earlier processing;
• right to lodge a complaint with a data protection authority (see below).

How to exercise them: you can download your data (“Download my data”, a JSON file) and delete your account (“Delete account”, confirmed with a 6-digit code sent to the account email) directly from the account settings. On deletion, the account is deactivated immediately and personal data is anonymised and erased within 30 days. If you added a shop to your account, you delete the shop first, from its Settings, where you can choose to delete the account too (see "Deleting a shop" in How long we keep data). For any other request, including about a shop's data, write to privacy@carix.app. We reply within one month; for complex requests this may be extended by two further months, in which case we let you know. Exercising your rights is free. See Your rights (GDPR) for details.

If you believe we process your data unlawfully, you can lodge a complaint (Art. 77 GDPR). We are established in Bulgaria, so the lead supervisory authority for CariX is the Bulgarian Commission for Personal Data Protection (CPDP, www.cpdp.bg (ανοίγει σε νέα καρτέλα)). You can also complain to the authority of the EU country where you live, work or where the alleged infringement took place; in Romania, that is the National Supervisory Authority for Personal Data Processing (ANSPDCP, www.dataprotection.ro (ανοίγει σε νέα καρτέλα)). Please write to us first so we can try to solve the problem together.

CariX is not intended for people under 16 and we do not knowingly create accounts for them. If you learn that a child under 16 has given us personal data, write to us and we will delete it.

We protect data with technical and organisational measures, including:

• encrypted connections (HTTPS);
• we use no passwords: sign-in codes sent by email are stored only as hashes computed with a secret key, are valid for 10 minutes, work once and are cancelled after 5 wrong tries;
• sign-in sessions are stored only as hashes;
• files (documents, photos) are private and open only through temporary signed links;
• role-based access: each shop sees only its own customers' data;
• limits on sign-in and form attempts, and on how many codes are sent to the same email address;
• access keys to external services (including those of invoicing programs), ANAF tokens, webhook secrets and buyers' CNPs are stored encrypted;
• data sent by webhook is signed (HMAC-SHA256), so the shop can check that it comes from CariX.

If a personal data breach occurs that may affect your rights, we will inform you and notify the competent supervisory authority (CPDP), as required by Articles 33 and 34 GDPR.

We do not take decisions based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Art. 22 GDPR). The order of search results is calculated automatically using the criteria in our Terms and conditions, and feedback messages are classified automatically only so we can organise them; the classification has no effect on you.

We use necessary cookies and, only with your consent, analytics cookies. The full list and settings are in our Cookie policy.

We may update this policy. The version and the date of the last update are shown at the top of this page, and we notify you of important changes by email or in the platform before they apply.

• Operator: Appy Solutions EOOD
• Email: contact@carix.app
• Data protection: privacy@carix.app
• Phone (RO): +40 728 858 989
• Phone (BG): +359 88 975 8989
• Address: ul. Ivan Susanin 45, vh. A, et. 3, ap. 9, Sofia 1618, Bulgaria