Aura Privacy Policy
Review draft | Prepared 16 November 2026
This policy explains how Aura collects, uses, shares and retains personal data when you use our dating app, website and related support services. It also explains your choices and rights. It is separate from our Terms of Use and Community Rules, which govern conduct and purchases.
Publication note: This is a proposed replacement policy, not an effective notice. Confirm the operational details in the final internal checklist, complete any required feature-specific notices and set an effective date before publication.
1. Who is responsible for your data
Aura is operated by PRAGMATICAPPS PLLC ("Aura", "we", "us"), the controller of your personal data. Contact email: support@auradating.bg.
This policy covers personal data processed for Aura accounts, profiles, communications, purchases, verification, safety and customer support. If a feature needs additional privacy information, we provide it before collecting the relevant data. Using Aura does not by itself constitute consent to processing that requires your consent.
2. Information you provide
- Account information: registration and login details, such as your email address, phone number where requested, username, date of birth and authentication credentials.
- Profile information: photos, biography, interests, preferences and other information you choose to add. Dating preferences and profile content may reveal sexual orientation, sex life, religion, health or other sensitive information.
- Communications and content: chats, messages, photos and other content you send, upload or share through Aura. Messages remain a category of personal data we collect and process to provide the service.
- Purchases: products purchased, transaction identifiers, dates, amounts, subscription status and refund records. App stores and payment providers process payment credentials under their own notices; the information we receive depends on the payment method.
- Support and safety reports: requests, correspondence, screenshots, copies of conversations, profile identifiers and other evidence submitted by you or by someone reporting an interaction with you.
3. Information from use of the service and others
Usage and technical information. We collect activity such as logins, features used and interactions with the service, together with device and operating-system information, IP addresses, relevant device identifiers, connection records, diagnostics and crash reports. These data support service delivery, troubleshooting and security.
Other sources. We receive information from users who contact support or submit reports, payment platforms confirming transactions, and service providers supporting Aura. If you use an available third-party login or import feature, we receive the information you authorize that provider to share. We do not treat permission to access one category of data as permission to access everything on your device.
Location and device permissions. Where a feature uses device location, camera, microphone, contacts or a photo library, the relevant permission request and feature notice explain the access needed. Declining an optional permission may prevent that feature from working without preventing unrelated use of Aura. A device permission does not replace any separate consent required by law.
4. Why we use data and our legal grounds
- Provide the service: create accounts, display profiles, deliver messages, support matching and operate requested features. We rely on performance of our contract for processing objectively necessary to provide those features.
- Process purchases and requests: administer paid features, subscriptions and refunds, and answer service questions. We rely on contract performance, with legal obligations applying to required financial records.
- Protect users and Aura: assess reports, identify fraud, spam, account misuse and security incidents, enforce rules and prevent repeat abuse. For necessary and proportionate processing of ordinary personal data, we rely on legitimate interests in protecting users and the service, or a specific legal obligation where applicable.
- Maintain and improve Aura: diagnose faults, measure feature performance and evaluate service improvements. We rely on legitimate interests where appropriate, and obtain consent for tracking or other processing that requires it.
- Marketing: send promotional communications where permitted by law. We obtain consent where required and provide an opt-out. Essential account and security messages are separate from marketing.
- Legal compliance and disputes: respond to valid legal requests, maintain required records and establish, exercise or defend legal claims. We rely on the relevant legal obligation or legitimate interest, as appropriate.
We assess whether our legitimate interests are outweighed by your rights and reasonable expectations. You may object to processing based on legitimate interests. Where we rely on consent, you may withdraw it without affecting the lawfulness of earlier processing.
Sensitive data require an additional lawful condition. For optional sensitive profile information and biometric identification, our proposed basis is explicit consent. Other exceptions, such as necessity for legal claims, apply only where their legal requirements are met; a general safety purpose is not a blanket permission to process sensitive data.
5. Facial verification and sensitive information
Facial verification is optional. It involves processing a facial capture and the verification result. Depending on the technical implementation, it may also involve video frames, facial measurements or templates used to check liveness or compare faces. When used to uniquely identify a person, facial biometric data receive special protection under data-protection law.
Before verification starts, a dedicated notice must explain the actual data captured, the verification provider and its role, processing locations, the purpose of any biometric comparison, retention and deletion periods, and how to withdraw consent. These implementation details must be completed before publication or collection; this general policy is not a substitute for that notice.
Where explicit consent is required, we request it separately before processing. You may decline optional verification or withdraw consent through support. Withdrawal can result in removal of verification status and deletion of data processed solely on that consent, subject to any independently lawful and necessary retention. It does not require deletion of unrelated account data that we lawfully need to provide your account.
A verification result concerns the checks performed at that time. It does not establish a person's intentions, guarantee the truth of all profile information or prove who controls the account later. We do not use verification information for unrelated advertising purposes under this policy.
6. Reports, messages and safety investigations
When someone reports a profile or conversation, we process the report and relevant supporting information to assess what happened and decide on an appropriate response. This can include submitted screenshots, message content, account history, relevant technical records and information supplied by the reported user. A report is an allegation to assess, not automatic proof of wrongdoing.
Chats are collected content. Access to personal data for support or safety work must be limited to authorized personnel and service providers who need it for the relevant purpose. This policy does not state that all conversations are routinely read, or that messages are inaccessible to Aura. The precise access arrangements must match the implemented system.
We may ask for screenshots, copies of messages or additional context where needed to identify or investigate an incident. Please submit only relevant material and avoid unnecessary sensitive information about yourself or others. Evidence can contain personal data of the person submitting it, the reported user and other people mentioned in it.
We may retain necessary evidence and decision records to address complaints, prevent repeat abuse and handle legal claims. Disclosure to a reported user or another requester is assessed against applicable access rights and the privacy and safety of others; reporting does not guarantee absolute anonymity.
Any use of automated tools to analyse messages, score risk or make enforcement decisions must be accurately disclosed before deployment where required. A report suggesting AI-generated messages is not, by itself, conclusive evidence of automation. This policy does not authorize unrestricted reuse of private chats to train general-purpose AI models.
7. Who receives personal data
- Other users: the profile information and content you make visible, and messages or media you send to their intended recipients. Recipients may save or share content outside Aura; avoid sharing information you do not want them to retain.
- Service providers: providers supporting hosting, storage, security, analytics, communications, customer support and verification, to the extent needed for their assigned services. Processors must act under appropriate contracts and instructions, with confidentiality and security obligations.
- Payment platforms: app stores and payment services handling transactions, subscriptions or refunds. Some recipients act as independent controllers under their own privacy notices.
- Authorities and professional advisers: where necessary and lawful to comply with valid requests, meet legal duties, address serious safety concerns or establish, exercise or defend legal claims. We assess the legal basis and scope of each disclosure.
- Business transfers: relevant information may be disclosed during a merger, acquisition or transfer of Aura, subject to appropriate confidentiality, purpose limitations and any required notice.
We do not sell personal data for advertising without explicit consent. This statement does not authorize undisclosed advertising-data sharing. Any advertising SDKs, recipients, purposes and required choices must be disclosed accurately before their use. We do not assume membership in, or share data across, Match Group or any other unrelated dating-app group.
8. International transfers
Using service providers can involve access to data from outside the European Economic Area. Where such a transfer occurs, we use a legally valid mechanism, such as a European Commission adequacy decision or Standard Contractual Clauses with appropriate supplementary measures where needed. Encryption alone is not a legal transfer mechanism.
The applicable destinations, recipients and safeguards must be documented and reflected in the published notice or linked provider information. You can ask support for information about the safeguards or a copy, subject to necessary redactions to protect confidential information and others' rights.
9. Cookies, SDKs and automated recommendations
Aura and its website may use cookies or equivalent app technologies for authentication, preferences, security and measurement. Non-essential device storage or access requires consent where applicable. The published cookie or SDK information must identify the actual technologies, purposes, providers, duration and controls. You may change consent settings; browser and device controls can also restrict access.
Matching and recommendations may use your stated preferences, profile details and interactions to suggest relevant profiles. These processes can constitute profiling. We must explain any solely automated decision with legal or similarly significant effects, including its logic in meaningful terms, likely consequences, legal basis and available safeguards, before it is used. Where applicable, you may request human intervention, express your view and contest the decision.
10. How long we keep information
We retain personal data only for as long as necessary for the specific purpose. Account closure starts the deletion process; it does not necessarily require immediate deletion of every record. We apply the following purpose-based criteria, subject to the confirmed retention schedule:
- Account, profile and chat data: while needed to operate the account and requested features; after closure, only for a defined deletion process or a separately justified safety, legal or recordkeeping purpose. We also assess inactive accounts rather than retaining them indefinitely.
- Reports and security records: while an investigation, complaint or appeal remains active, and afterwards only for a documented period proportionate to the risk of repeat abuse, relevant limitation periods or a legal duty. Retaining a restricted ban-prevention identifier does not justify keeping the entire account forever.
- Purchase and accounting records: for the statutory recordkeeping periods applicable to the specific record and jurisdiction, and as needed for an ongoing transaction dispute.
- Verification material: facial captures, templates and verification results need separate retention rules in the verification notice. Raw facial data must not be kept indefinitely simply because an account remains active.
- Backups and legal holds: deleted data may remain in restricted backups until the documented rotation period expires. Relevant records may be preserved for a specific legal obligation or claim and deleted when that justification ends.
Where possible we delete or irreversibly anonymize information when its purpose ends. Pseudonymized or hashed information can still be personal data and remains subject to this policy. Specific periods or more precise criteria must be finalized before publication.
11. Your choices and rights
Subject to applicable conditions, you can request access to your data and a copy, correction, erasure, restriction of processing or portability. You can object to processing based on legitimate interests and object at any time to direct marketing, including related profiling. You can withdraw consent as easily as you gave it.
Contact support@auradating.bg and identify the account and request. We may seek proportionate information to verify identity, but will not request unnecessary documents. We normally respond within one month. If a lawful extension is needed because of complexity or number of requests, we explain it within that first month. Requests are normally free; statutory exceptions apply to manifestly unfounded or excessive requests.
Deletion and access rights are not absolute: legal recordkeeping, legal claims and the rights of other people can affect what we can delete or disclose. We explain any applicable restriction. Deleting an account and cancelling an app-store subscription are separate actions; use the relevant store controls to stop renewals.
You may complain to your local data-protection authority, including the Bulgarian Commission for Personal Data Protection: cpdp.bg, 2 Prof. Tsvetan Lazarov Blvd., Sofia 1592, Bulgaria. You do not need to contact Aura first to exercise that right.
12. Security
We use technical and organizational measures appropriate to the risks, including access restrictions, authentication protections and safeguards for data storage and transmission. The published description must reflect the measures actually implemented. No online service can promise absolute security. Please protect your login details and report suspected account compromise to support.
Where a personal-data breach occurs, we assess the risks, take appropriate remedial action and notify the relevant authority and affected individuals when legally required.
13. Adults only
Aura is intended only for people aged 18 and over. Parental consent does not make a person under 18 eligible to use Aura. If you believe a minor has an account, contact support or report the profile. We investigate and take appropriate steps to remove the account and delete associated data, retaining only what is lawfully necessary for safety or legal obligations.
14. Updates and contact
We may update this policy to reflect changes to Aura, our processing or the law. The published version will identify its effective date. We notify users of material changes through an appropriate channel, such as email, an in-app notice or a prominent website notice. Where a new use requires consent, we obtain it before starting that processing; continued use alone does not provide it.
For questions, requests or concerns about personal data, contact support@auradating.bg. Where a data-protection officer is appointed, their contact details will also be made available.