Debitorix

Privacy Policy

Company-wide legal documents

1. Who We Are

This Privacy Policy is provided by Uniqortex (referred to as “we”, “us”, or “our”). We act as the controller of personal data we process for our own purposes, including managing accounts and responding to enquiries. Each product notice explains that application’s processing and the relevant roles of the parties involved.

The controller’s legal identity and our contact details are provided in section 14.

2. What This Policy Covers

This is our company-wide privacy policy. It does not, by itself, replace the privacy notice required for the particular data practices of an individual application. It applies to our corporate website and to applications, websites, and digital services that link to it (the “Services”). It describes the shared practices and the common third-party technologies we use across our business.

Different applications can collect different user-created content, offer different sharing features, and apply different retention or deletion rules. Their individual websites or in-app notices provide those product-specific details. The applicable product notice and this Policy together form the privacy information for that Service. We do not imply that every application uses every category or provider described below.

We make this Policy available at https://debitorix.com/privacy-policy/. If a product requires an additional collection-time disclosure or a separate consent, it will be provided where needed.

3. Information We Process

3.1 Account and authentication information

Where a Service offers user accounts, users may be able to register or sign in with an email address, Sign in with Apple, or Sign in with Google. We process the information needed to authenticate the user and maintain secure access, which may include:

  • An internal account or user identifier, login method, authentication status, session credentials, and security events;
  • A one-way-derived identifier based on an email address for email-based account lookup, rather than retaining the email address in plain text in our application authentication databases;
  • Email addresses supplied for one-time verification-code sign-in and delivery of requested authentication messages; the original address is processed temporarily so the code can reach its intended recipient; and
  • Unique account identifiers, authentication tokens, and any other information returned by Apple or Google according to the permissions and sign-in method used.

We do not store email addresses in plain text in our application authentication databases. For email sign-in, we use a one-time verification code and a one-way-derived email identifier associated with the account. The original email address is nevertheless temporarily processed for sending the code. Amazon Web Services (AWS) provides the email-delivery infrastructure used for application authentication and other system messages. AWS may process email recipients, message content and delivery metadata as needed for this purpose. AWS processes the recipient address and delivery-related information in the locations applicable to our configured email-delivery service. Emails sent to our support mailbox contain the sender’s email address and message. Derived identifiers that remain linkable to an account are treated as personal data.

3.2 Information users provide within applications

Depending on the Service, we process the information users choose to enter, store, upload, or share, including records, files, notes, settings, and information about other people. These categories and their purposes are explained in the relevant product-specific privacy notice, rather than enumerated in this company-wide Policy. When a Service offers sharing or collaboration, its notice explains who may access shared information.

3.3 Application backend infrastructure and hosting

We use Hop One Networks to provide dedicated server infrastructure for the backends of our applications. Our dedicated application backend server is hosted by Hop One Networks in the United States. Uniqortex manages the application software, databases and access permissions; Hop One Networks supplies the underlying dedicated hosting infrastructure. Depending on the application, the backend systems process account identifiers, authentication-related information, user-submitted content, synchronization data, and operational or security logs. Hosting is separate from the use of Cloudflare for our corporate website.

We use Backblaze B2 Cloud Storage for off-server backups of application backend data. These backups are stored in the United States. Depending on the application and backup configuration, copies may contain user records, account-related identifiers, server configuration, or other data required for recovery. The applicable product’s notice explains its record-retention and account-deletion arrangements. Other providers may process technical or account-related data in additional locations.

3.4 Email correspondence and privacy requests

The company website does not provide a contact form. If you email us at contact@uniqortex.com, we receive your email address, message, any attachments, and subsequent correspondence. We use Google Gmail to receive, send, and store our business email correspondence, including messages forwarded from our company address. Google may process message content, attachments, email addresses and delivery-related metadata under the terms that apply to the Gmail service. We use this information to respond to you, handle support, security, legal, or privacy requests, and retain a record of the communication where justified.

If you submit a privacy-rights request, we may also process the information reasonably necessary to verify your identity or authority and document the response.

3.5 Website, security, and analytics information

Our corporate website is delivered using Cloudflare infrastructure and services. When the site is accessed, Cloudflare and related technical systems may process IP addresses, request and response metadata, browser/device details, requested pages, traffic and security signals, and information needed for caching, delivery, and protection against abuse. Cloudflare operates a global network; requests may be processed outside Armenia or your country.

We use Google Analytics to measure usage of our corporate website and product websites where analytics is enabled, subject to applicable consent and configuration. Depending on the settings and permissions, Google Analytics may process page-view events, interactions, approximate location inferred from technical signals, device/browser information, cookie or other online identifiers, and similar usage information. We use this information to understand website traffic and improve our websites. The statistics include visits to individual pages and their language versions.

We do not display advertisements or sell subscriptions or other services directly on the corporate website. Website analytics are separate from advertisements in mobile applications.

3.6 Advertising in applications

Advertising-supported applications may display advertisements delivered through Google AdMob (Google Mobile Ads SDK). When enabled in a particular application, Google and its advertising partners may process data such as IP address, device or advertising identifiers (where permitted), approximate location derived from IP or other permitted signals, app interactions, ad views or clicks, diagnostic events, and related information for ad delivery, measurement, fraud prevention, or personalization where allowed.

The specific application identifies its advertising functions and any additional advertising partners or SDKs in its own privacy notice. The advertising features used by one application should not be assumed to apply to every application. We provide consent and privacy controls where required by law, Google policies, and platform rules. On iOS, Apple’s App Tracking Transparency permission is sought where the applicable tracking rules require it.

For Google’s explanation of information used in third-party sites and apps, see How Google uses information from sites or apps that use our services and Google’s Privacy Policy.

We process the information described above for the following purposes. The legal bases listed apply where the EU or UK GDPR or equivalent legislation requires them; the actual basis depends on the processing and applicable law.

PurposeLegal basis where applicable
Provide accounts, verify sign-in, and deliver requested Service featuresPerformance of a contract or steps at the user’s request
Respond to emails and provide supportPerformance of a contract or our legitimate interests in addressing inquiries
Operate, secure, protect, and troubleshoot our website and ServicesLegitimate interests in safe and reliable operation; contractual necessity where applicable
Measure usage of our corporate and product websites using Google Analytics, where enabledConsent where required for analytics cookies or comparable technology; any other applicable legal basis must be assessed separately
Deliver and measure mobile advertising using Google AdMobConsent where legally required; otherwise an applicable legitimate interest or other lawful basis where available, as detailed in the product notice
Process valid privacy requests and satisfy legal obligationsCompliance with a legal obligation
Establish, exercise, or defend legal claimsLegitimate interests or another lawful basis permitted by law

Where consent is required, we provide a way to grant or refuse it and to withdraw it. Optional website analytics are not required to browse our corporate or product websites. Advertising and subscription choices offered by individual applications are explained at the product level.

5. Cookies and Similar Technologies

The corporate website uses essential technical storage where needed for security, traffic handling, or remembering a privacy choice. Cloudflare may set security-related cookies. These technologies are used for site operation and protection.

We use Google Analytics to measure usage of our corporate website and product websites where analytics is enabled. Google Analytics may set cookies or use comparable identifiers. Where consent is required, we do not activate non-essential analytics until you choose to allow it. You can decline optional analytics and later change your choice using the Cookie Preferences control on the relevant website. Declining optional analytics does not prevent access to our corporate or product websites.

Information about the cookies and similar technologies actually used, their providers, purposes, and retention periods is available through the website’s Cookie Preferences interface. You may also restrict cookies using your browser settings, although disabling essential technical storage may affect some site functions.

The lifetime of an analytics cookie in your browser is separate from the Google Analytics user/event data retention period described in section 8.

Preferences for advertising and tracking within mobile applications are managed separately from website analytics preferences.

6. Service Providers and Other Recipients

The following providers may receive or process information to perform the purposes described in this Policy, subject to the applicable arrangements and product features. Common providers include:

Provider or recipientGeneral role
CloudflareCorporate website delivery, caching, performance, network security, and related technical processing
Hop One NetworksDedicated application backend infrastructure in the United States
Backblaze B2 Cloud StorageOff-server backup storage in the United States
Amazon Web Services (AWS)Delivery of one-time sign-in codes and other application-generated emails; recipient addresses, message content and delivery metadata may be processed
Google Analytics (Google)Corporate and product website traffic and usage measurement, where enabled and subject to applicable user choice
AppleIdentity provider when users select Sign in with Apple and operator of the Apple app distribution ecosystem
GoogleIdentity provider for Sign in with Google; Google Play ecosystem; and Google AdMob advertising technology in applications that include ads
Google GmailBusiness email, support, privacy requests, and related correspondence
Additional product-specific providers, if anyIdentified in the applicable product notice, where required
Professional advisers and authoritiesOnly where necessary for legal compliance, legitimate claims, or valid legal requests

Service providers may act as processors or independent controllers, depending on their services and terms. Their own privacy policies may apply to their direct processing. Product-level notices identify any additional data recipients relevant to a particular application, including payment, analytics, diagnostics, or other integrations if used.

We require third parties with which we share personal data to provide protection at least equivalent to that described in this Policy and required by applicable app-store rules and law. A provider’s own terms or privacy policy do not reduce our obligations to you.

7. International Data Processing

Our business is registered in Armenia. We host the primary application backend server with Hop One Networks in the United States, and we use Backblaze B2 in the United States, to store application backups. Our email-delivery provider Amazon Web Services (AWS) may process email-recipient information and message delivery data in its configured service regions. Cloudflare, Apple, Google (including Gmail, Google Analytics, identity services, Google Play and AdMob), and their relevant partners may also process data in other countries depending on the service and technical configuration. We do not claim that all personal data remains exclusively in the United States or Armenia.

When a transfer of personal data is subject to specific international-transfer rules, we apply a lawful mechanism appropriate to the transfer and recipient. Depending on the circumstances, this may include a legally recognized adequacy mechanism, applicable contractual safeguards, and supplementary protective measures. We evaluate these requirements for the relevant services and jurisdictions. You may request information about the safeguards applicable to your data, including how to obtain a copy where required, by emailing contact@uniqortex.com.

8. How Long We Keep Information

We keep personal data only for the purposes and periods described below, subject to applicable law and the additional information for each Service:

CategoryRetention period or determining criterion
Account and authentication identifiersDuring the account’s operation; when an account is deleted, remaining account data is processed according to the relevant product’s deletion procedure, subject to legally required or justified exceptions.
One-time email sign-in codesValid only for a short, limited period and removed or invalidated after use or expiry. Associated security and delivery records follow the applicable security-log period and provider rules.
Ordinary support and business emailOrdinarily up to 36 months after the last substantive communication. Relevant messages may be kept longer if reasonably necessary for an unresolved dispute, legal obligation, fraud investigation, or legal claim.
Privacy-rights requestsWhile needed to process the request and to demonstrate lawful handling of it, including relevant limitation periods.
Corporate and product website Google Analytics user/event dataUp to 14 months for data covered by the Google Analytics retention setting. Aggregated reports may remain available longer according to the service’s operation.
Application server operational and security logsOrdinarily up to 90 days, unless a shorter period applies or a specific security event or legal requirement justifies longer retention.
Cloudflare technical dataAccording to the Cloudflare service, data category, and applicable configuration; access and retention of provider-managed records may differ from our own logs.
Application records and shared contentAs described in the product-specific privacy and account-deletion information.
Backblaze B2 rolling backupsA rolling 180-day recovery window. Older base backups and recovery logs are retained only while needed to restore data within that window, as explained below.
Transaction, tax, and dispute recordsFor the period required by law or reasonably necessary to establish, exercise, or defend legal rights.

Application data backups. We create backups to restore service operation and data integrity after technical failures, erroneous changes, data corruption, and security incidents, including corruption discovered after a delay.

We maintain a rolling 180-day recovery window. Backups are stored in encrypted form with restricted access and are used only for recovery and testing recovery procedures. Older base backups and recovery logs may be retained while newer recovery points within this window depend on them. These older copies and logs are removed through routine expiry once those dependencies no longer exist.

After personal data is deleted from live systems, residual copies may remain in previously created backups until those backups and any technically necessary dependencies expire under the rules above. This data is excluded from ordinary use. When restoring a backup, we reapply previously completed deletions before resuming ordinary data processing.

To prevent previously deleted data from returning when a backup is restored, we retain minimal technical records of completed deletions: identifiers for the relevant application, account or records, and the deletion date. These technical records do not contain the original email address or deleted user content. They are used to reapply deletions, are treated as personal data and are accessible only to authorized personnel. We delete them after all backups from which the relevant data could be restored have expired and any ongoing restores have been completed.

Where information must be preserved to meet a legal obligation, establish, exercise or defend legal claims, or investigate a specific security incident, we retain only the necessary information separately from routine backup rotation, with restricted access and a documented retention period. Such preservation does not extend the routine retention of all backup copies. We delete or anonymize the information when the reason no longer applies, subject to mandatory statutory retention periods. If you request deletion, we review your request in light of applicable legal requirements and the rights of other users.

9. Security

We use technical and organizational safeguards proportionate to the data and risks involved, including access controls, protected authentication, secure transmission channels, controlled administrative access, and backup and recovery procedures. Product-specific safeguards and responsibilities may be explained in the relevant product notice. No system can guarantee absolute security.

10. Your Privacy Rights

Depending on your location and the processing involved, you may have rights to access, correct, delete, restrict, or receive your personal information, object to certain processing, withdraw consent, and lodge a complaint with a competent data-protection authority.

To exercise your rights or ask about our processing, contact contact@uniqortex.com and identify the relevant Service. We may request proportionate proof of identity before disclosing account information. We respond within periods prescribed by applicable law.

Account-deletion functions and product-data export or correction options are described and provided by the relevant application. A request concerning another person will be assessed with due regard to that person’s rights and the rights of other affected individuals.

11. Children and Age Requirements

Our corporate website is intended to provide general business information. Our products differ in their intended audiences and applicable content restrictions. Some applications may contain age-restricted entertainment or simulations of chance-based activities, while others may have different eligibility rules. Age requirements, any access restrictions, and the treatment of children’s information are set out for each applicable product in accordance with relevant marketplace age ratings and local law. We do not assume that all Services target the same age group, and we do not state that age-restricted applications are suitable for children.

12. Optional Information and Automated Decisions

Some information, such as a recipient email address for a one-time sign-in code, is needed to provide a feature requested by you; if it is not provided, that feature may not work. Optional analytics are not required for access to our corporate or product websites.

This company-wide Policy does not describe automated decision-making that has legal or similarly significant effects on individuals. If a particular product uses such processing, the applicable product notice provides the information required by law.

13. Changes to This Policy

We may update this Policy when our data processing or legal requirements change. The current text is published on this page. Where required by law, we will give advance notice of changes and request any necessary consent. Changes relating to an individual application will also be reflected in its privacy notice.

FieldDetails
Data controllerPAVEL MARAKAZOV, IE, an individual entrepreneur registered in the Republic of Armenia, trading under the Uniqortex name
Business address2A Aghbyur Serob St., Apt. 20, Yerevan 0019, Armenia
Emailcontact@uniqortex.com
Phone+374 55 147 473
Websitehttps://uniqortex.com

For registration details, see our Legal Notice. Application-specific privacy information is provided on the corresponding application’s website or within that application.

Specifics of Data Processing

This appendix supplements the general Uniqortex Privacy Policy with information about data processing in Debitorix. Information about accounts, common providers, advertising, purchases, international processing and general retention periods is provided in the main Policy.

Accounting data in Debitorix

The data involved depends on the types of records you keep and the information you enter.

Data typeContent
Money debts, loans, instalment plans and depositsRecord titles, counterparties, amounts and currencies, dates, rates and interest accrual terms, schedules, actual payments, top-ups, withdrawals, changes to terms and comments. The app calculates balances, accruals, payments and overdue amounts.
Items lent or borrowedItem name, the person to whom it was lent or from whom it was borrowed, return deadline and history of handovers and returns.
Prepayments, passes, service packages and certificatesName, recipient or provider, price, paid and remaining service quantity, validity period, top-ups, usage and refunds.
Shared expenses and collectionsGroup name, participant names, number of people accounted for, payers, expense allocation, contributions, refunds, settlements, dates, amounts, currencies and comments. Participant balances and collection results are calculated from this information.
CounterpartiesNames of people or organisations you enter and their links to records of debts, items, prepayments and group transactions.
Calculators and accounting settingsSaved input data for financial calculators, selected currencies, amount display settings and reminder settings.

You enter the source information; Debitorix adds calculation results and technical information needed to save and sync records. A calculation requires the relevant initial terms. Comments and notes are optional.

How accounting data is used

We process this data to save the records you choose, track transactions, calculate balances and schedules, allocate expenses and contributions among participants, perform calculator calculations and provide available reminder features. Saved records and settings are also used to sync your account, export data and restore data from an imported copy.

The grounds for processing to provide features, ensure security and handle requests are set out in section 4 of the general Policy. Naming a person in a Debitorix record does not mean that the person has entered into a contract with us or agreed to the information about them.

Information about counterparties and participants

Records may concern people who are not registered with Debitorix. For example, a user may name a borrower, lender, recipient of an item or participant in shared expenses. The source of this information is the user keeping the relevant records.

Data is synced within the account in which the records are kept. Adding a person to a list of counterparties or group participants does not, in itself, give them access to that account or group or transmit its records to them.

If you send another person a generated document or exported file, the information included in that document or file becomes available to them.

Local storage and synchronisation

The Debitorix web version, including when installed as a PWA, saves a local copy of accounting data in browser storage and syncs records with the server. When offline, changes may remain in a local queue until the next successful sync.

Clearing browser storage or deleting the local copy does not constitute a request to delete server data. Unsynced changes may be lost when that storage is cleared.

JSON export is intended for saving a copy of data and restoring it later; CSV export provides accounting data in tabular form. These files may contain financial information and the names of counterparties or participants.

Retention and deletion of records

Accounting records are retained while you use or keep them in your account, until the relevant record is permanently deleted or the account is deleted, subject to the general Policy. A debt reaching its due date, a collection ending or a pass expiring does not, in itself, mean the history is deleted.

Archiving preserves a record. Moving it to the bin also preserves the data and allows the record to be restored. Permanently deleting a record and emptying the bin initiates deletion of the relevant records and associated transactions. An action performed offline must be sent to and processed by the server before server-side deletion is complete.

You can submit an account deletion request in the Debitorix web version’s settings. Access to the account is blocked while the request is processed; on completion, its accounting records, group participants, transactions, settings and account data are deleted. Request progress is shown in the app. Submitting a request requires a network connection.

Server-side deletion cannot remotely erase previously exported files or a local copy on a device that remains permanently offline. Rules for handling backups and technical information needed to prevent restoration of deleted data are set out in section 8 of the general Policy.

Account deletion without the app

To delete your account without installing the app, sign in to the Debitorix web version, open “Settings → Account and data” and select “Delete account”.

Requests about data in another user’s record

If another user has included you in their Debitorix records, you can contact us about the processing of that information even if you do not have an account. Specify which information relates to you and which record or situation is concerned so that we can locate the relevant data. The procedure for handling requests and verifying identity is set out in the general Policy; the product contact is provided in the Debitorix Legal Notice appendix.

Age requirements

Debitorix is intended for users aged 16 and over. If you become aware that an account has been created by someone under 16, notify contact@debitorix.com. We will review the request and take necessary measures concerning the account and associated data in accordance with the general Policy and applicable law.