Privacy Policy
Privacy Policy
Last updated: 18 October 2026
Adithana Marketing LLC (“AIMAR”), a limited liability company incorporated in Bulgaria under UIC 205958514, with registered office and address of management at 11 G Prof. Hristo Vakarelski Str., 1700 Sofia, Bulgaria, operates AIMAR (“AIMAR”, “we”, “us”).
This Privacy Policy explains how we process personal data when you visit aimar.chat, use the AIMAR platform at app.aimar.chat, contact us, take part in an Expert session or receive business communications from us.
For any privacy question or request, email support@aimar.chat with “Privacy” in the subject line. This address reaches the person responsible for data protection at AIMAR and can also be used to request any applicable data protection officer or representative contact details.
This Policy informs you about our practices. It is not a contract, and you are not asked to agree to it. Where we need your consent, we ask for it separately for that purpose; reading this Policy, using AIMAR or continuing to use AIMAR after an update does not itself give consent. Our Terms of Service govern use of the Service.
1. Our Roles
Controller. We are the controller for personal data about visitors to our website, people who sign up for or use AIMAR, billing contacts, people who contact us or take part in Expert sessions, and business contacts we approach about AIMAR. This Policy covers that processing.
Processor. When we process personal data in customer content, Outputs or connected-service data on a business customer’s instructions, that customer is the controller (or a processor acting for another controller) and we act as its processor or subprocessor. Our Data Processing Addendum governs that processing, and this Policy gives us no independent permission to reuse that data. If your data is in an AIMAR customer’s account, please contact that customer to exercise your rights. If you contact us, we will refer you to the customer and tell the customer where we can identify it.
The same item of data may be used in different roles for different purposes. For example, we administer an authorized user’s account as controller while processing a customer’s contact list solely on that customer’s instructions.
2. Personal data we collect and where it comes from
Account data
What it includes: Name, business email address, company, job title, user role and sign-in method. Passwords are stored only in hashed form by our authentication provider.
Source: You; Google, if you sign in with Google (name, email address, profile picture)
Business information
What it includes: Company details, goals, positioning, marketing plans, documents, prompts and other content you submit, and the Outputs generated for you
Source: You
Billing data
What it includes: Billing name and address, VAT number, plan, invoices and payment status. Card details are entered with our payment processor, Stripe; AIMAR never receives or stores full card numbers.
Source: You; Stripe
Usage and technical data
What it includes: IP address, device and browser type, sign-in times, features used, error logs, and records of approvals and actions taken through connected services
Source: Your device and our systems, automatically
Integration data
What it includes: Access tokens and account identifiers for services you connect, and the data you allow us to read from them (Section 5)
Source: The connected service, with your authorization
Communications
What it includes: Support requests, feedback, survey answers, Expert-session bookings and notes
Source: You; our scheduling provider, Calendly, when you book a session
Website analytics data
What it includes: Pages viewed, referring site, approximate location (country or city), device and browser
Source: Your browser, through Google Analytics, only if you accept analytics cookies
Business contact data
What it includes: Name, job title, company, business email address, professional profile URL and public company information
Source: Public sources such as company websites, professional networks and business directories; events; referrals
Testimonials
What it includes: Name, photo, job title, company and your quote
Source: You, with your consent
Personal data of other people inside business information or integration data, such as your contacts, CRM records or campaign recipients, is customer data that we process as processor under our DPA (Section 1).
Required and optional information. Account identification, sign-in and necessary billing information are required to provide an account or paid service, and Bulgarian law requires billing details on invoices; without them we cannot provide that service. Integrations, promotional emails and optional cookies are voluntary. Declining them does not prevent access to core services.
3. Why we use personal data and our legal bases
This section covers processing for which AIMAR is the controller. Generating Outputs and running integrations with personal data that customers submit or connect is processing on the customer’s instructions under our DPA, so it is not listed here. Where one activity involves both roles, we use an account user’s own data as controller only for the purposes listed here.
Provide AIMAR to account users: create and run accounts, authenticate users, provide support and deliver Expert sessions
Data used: Account, usage, communications
Legal basis (GDPR Art. 6(1)): Contract (b) where you are our contracting party. Otherwise, our legitimate interest (f) in providing the service your organization bought
Billing, invoicing, accounting and tax
Data used: Billing, account
Legal basis (GDPR Art. 6(1)): Legal obligation under Bulgarian accounting and VAT law (c); contract (b), or our legitimate interest (f) in managing organizational accounts
Support and service messages about security, billing, renewals, changes and outages
Data used: Account, communications
Legal basis (GDPR Art. 6(1)): Contract (b); legitimate interests (f)
Security, fraud and abuse prevention, enforcing our Terms and usage limits
Data used: Usage, account, integration
Legal basis (GDPR Art. 6(1)): Legitimate interests (f) in protecting users, customers and AIMAR; legal obligation (c) where a specific duty applies
Improving AIMAR, fixing errors and producing aggregated statistics that identify no one
Data used: Usage, account
Legal basis (GDPR Art. 6(1)): Legitimate interests (f) in developing our product. Statistics from customer content are created only on the customer’s instruction in Terms Section 9(b) and DPA Section 2.3
Website analytics on aimar.chat (Google Analytics)
Data used: Website analytics data
Legal basis (GDPR Art. 6(1)): Consent (a), given in our cookie banner; withdraw at any time in Cookie settings
News and offers about AIMAR
Data used: Name, email address, company
Legal basis (GDPR Art. 6(1)): Consent (a). For existing customers, where the applicable electronic-marketing law (in Bulgaria, the Electronic Communications Act) allows email about similar AIMAR products without consent: legitimate interests (f), with an opt-out in every message
Contacting business prospects about AIMAR
Data used: Business contact data
Legal basis (GDPR Art. 6(1)): Legitimate interests (f) in business-to-business marketing, and only through channels that the electronic-marketing rules of your country allow without prior consent; otherwise we ask for consent first. You can object at any time and we will stop
Publishing testimonials
Data used: Testimonials
Legal basis (GDPR Art. 6(1)): Consent (a); withdraw at any time
Legal compliance, claims and requests from authorities
Data used: Any relevant data
Legal basis (GDPR Art. 6(1)): Legal obligation (c); legitimate interests (f) in establishing, exercising or defending legal claims
Where we rely on legitimate interests, we assess the purpose, necessity and impact on your rights and apply appropriate safeguards. You may ask for information about the assessment and exercise your right to object under Section 11.
Business prospects. If we obtain your details as a business prospect, we obtained them from the public or professional sources listed in Section 2. We give you the information in this Policy within one month of obtaining your details, and at the latest in our first message to you, which links to this Policy. Tell us at any time that you do not want to hear from us: we will stop and keep only your email address on a do-not-contact list.
Automated decisions. We do not make decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. Automated security checks, such as blocking repeated failed sign-ins, may temporarily restrict access; you can ask a person at AIMAR to review any such restriction. AIMAR’s marketing suggestions are produced for human review and are not decisions about individuals.
4. Artificial intelligence and anonymous information
AIMAR uses Anthropic’s language models. To generate an Output, we send the inputs and relevant context to the provider under our documented processing arrangements. We prohibit model training with Customer Personal Data. Ordinary API retention runs for up to 30 days from receipt or generation; some flagged data and safety scores may be retained longer, as described in Section 9 and DPA Annex 1. We review each model and stored-data feature before enabling it for customer data.
Authorized AIMAR personnel and contractors bound by confidentiality, including Experts, access content only where necessary for service delivery, support you request, security, enforcing our Terms or legal compliance, and always subject to our DPA and the integration restrictions in Section 5.
We do not use identifiable customer content to train AIMAR’s or third parties’ generative AI models, and we do not allow our AI subprocessors to use Customer Personal Data to train or improve their own or other models. No optional program can override these restrictions or Google’s requirements.
Encoded, de-identified or pseudonymized information remains personal data where an individual can still be identified or linked to it by means reasonably likely to be used. We treat information as anonymous only where individuals can no longer be identified. Anonymization is itself processing and, where we act as processor, follows the customer’s documented instructions.
5. Integrations and Google API data
You choose whether to connect a third-party account. We access it only within the permissions you grant and to perform the actions you request, approve, schedule or configure. The connected provider also processes data under its own terms and privacy notice; a connection alone does not make it AIMAR’s subprocessor.
Gmail
The Gmail integration uses only the gmail.send scope. It lets AIMAR send emails from your account; it cannot read your inbox, emails or contacts. AIMAR sends only messages that you approve, either one by one or through a schedule or recurring workflow that you set up and approve under Section 10(d) of our Terms, and you can cancel a scheduled message before it is sent. AIMAR processes the message content, recipients and sending instructions to send the email, and a copy stays in your AIMAR conversation history.
Google Analytics and Search Console
These integrations use the read-only scopes analytics.readonly and webmasters.readonly to retrieve reporting data for the properties you select, such as traffic, engagement, impressions, clicks and search queries. They cannot change your settings. We use the data only to give you the performance insights and recommendations you request. We store the reporting data we retrieve, and the insights generated from it, in your AIMAR workspace (for example in conversation history and saved reports) until you delete them or your account closes, when Section 7 of our DPA applies.
These customer integrations are separate from the Google Analytics we use to measure visits to our own website, which our Cookie Policy covers.
LinkedIn and HubSpot
Depending on the permissions you grant, the LinkedIn integration lets AIMAR read your basic profile and publish posts or other content that you approve or schedule, and the HubSpot integration lets AIMAR read and, where you instruct it, create or update CRM records such as contacts, companies and deals. We use this data only to perform the actions you request, approve or schedule and to give you related insights. Personal data obtained this way is processed for you under our DPA.
Who receives integration data
We disclose integration data to the service providers that process it for us to deliver these features, mainly our hosting provider (Replit) and our AI model provider (Anthropic), under contracts that prohibit other uses, including training AI models. It may also appear in support requests you send or in error logs that the Service generates, which our providers process for us. AIMAR personnel and Experts access it only as Section 4 and the Google restrictions below allow, including when you ask for a review.
AIMAR’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google API data for advertising or other prohibited purposes, and we do not use Google Workspace API data to develop, improve or train generalized AI or machine-learning models. People at AIMAR, including Experts, read Google user data only with your affirmative agreement for a specific review, for security purposes, to comply with law, or in aggregated, anonymized form for internal operations. These restrictions also apply to information derived from Google user data, including aggregated or anonymized information. We do not use Google API data for profiling.
You can disconnect an integration in AIMAR at any time or revoke access in the provider’s settings, including your Google Account permissions. When you disconnect, we stop accessing the service and disable use of its access token. Tokens no longer needed for an authorized purpose are revoked where supported and deleted without undue delay; any residual protected backup copy expires under Section 9 and cannot be used to reconnect. Data already retrieved stays in your workspace until you delete it or your account closes, subject to the DPA.
6. Who we share personal data with
We do not sell personal data, share it for cross-context behavioral advertising, or use it for targeted advertising. We share it only with:
- Service providers that process it for us under contract: hosting and database (Replit, Inc.), sign-in (Clerk, Inc.), AI processing (Anthropic Ireland, Limited), payments (Stripe), Expert-session scheduling (Calendly), email and office software, our website host, our cookie-consent tool (CookieBot by UserCentrics) and, if you consent, Google Analytics (Google Ireland Limited). Stripe also acts as an independent controller for its own fraud-prevention and legal duties. Providers that process customer data for us are listed, with locations and safeguards, in Annex 4 of our Data Processing Addendum.
- Experts who deliver Expert sessions: AIMAR staff or independent contractors bound by confidentiality.
- Resellers and marketplaces you bought through, for the purchase and account details needed to provide and bill the Service.
- Professional advisers, such as lawyers, accountants and auditors, under confidentiality.
- Authorities, courts and other parties where the law requires it, to establish, exercise or defend legal claims, or to protect anyone’s safety.
- A buyer or successor if all or part of our business is sold, merged or reorganized, subject to this Policy and applicable platform requirements.
- Anyone else with your consent or at your direction, for example when you connect an integration.
7. Cookies and similar technologies
We use strictly necessary technologies for requested functions such as sign-in, security and remembering privacy choices. Optional website analytics requires your prior consent; browsing, inactivity or closing the banner does not give consent. The Cookie Policy describes providers, purposes and durations. Use Cookie settings in the footer to accept, reject, customize or withdraw consent. The app uses only technologies necessary for its requested functions. Any optional feature that needs device access beyond that exemption must remain off until the required choice has been offered and valid consent obtained.
8. International transfers
AIMAR is established in Bulgaria. Our disclosed processing arrangements include the European Union and the United States, and providers may process data in the other countries identified for the relevant processing chain. AIMAR does not offer an EU-only or US-only processing commitment unless expressly agreed in a binding service arrangement supported by the actual deployment. A customer with residency, public-sector, health, financial or other sector requirements should confirm compatibility before submitting affected data. Hosting location alone does not establish the location of support access or downstream processing.
Where a transfer outside the European Economic Area requires a safeguard, we rely on a European Commission adequacy decision (including the EU–US Data Privacy Framework, only for actively certified recipients and covered data) or on the EU Standard Contractual Clauses (Commission Decision (EU) 2021/914), with additional measures where needed. Where UK or Swiss transfer rules apply, we use the UK or Swiss mechanism included in the relevant provider’s terms. Contact support@aimar.chat for information about these safeguards or a copy, subject to lawful redactions. For customer data, Annex 4 of our DPA lists each subprocessor, its locations and its safeguard.
9. How long we keep personal data
Account data and business information
How long we keep it: While the account is open and for any applicable 30-day Retrieval Period or longer switching/retrieval period under Terms Section 18. We then delete active data without undue delay, subject to the specific lawful exceptions below. AIMAR-controlled database backups expire within 7 days after active deletion; restored data is re-deleted before ordinary use. Copies held by our providers are described in DPA Section 7 and Annex 1. Anthropic’s ordinary API period is up to 30 days from receipt/generation. Its published exceptions include flagged inputs/outputs for up to 2 years and associated safety scores for up to 7 years, legally required retention and limited retention/review for certain models. Stored-file features require separate deletion. We do not submit customer data through feedback features allowing additional retention or model improvement.
Billing and accounting records
How long we keep it: The periods in Article 12 of the Bulgarian Accountancy Act, counted from 1 January of the year after the reporting period: 10 years for accounting registers, financial statements and documents needed for tax and audit checks; 3 years for other accounting documents
Support correspondence and Expert-session notes
How long we keep it: For AIMAR’s own administrative correspondence, up to 3 years after the request or session closes, unless a specific legal duty or documented claim requires longer. Customer content and personal data processed on a customer’s behalf, including attachments, ticket content and Expert notes, follow the customer’s instructions and DPA Section 7; the 3-year controller period does not override them.
Security and operational logs
How long we keep it: Up to 12 months; longer only while needed for a specific investigation or legal claim
Records of approvals and actions taken through your account (who approved what, and when; not message content or recipient lists)
How long we keep it: 5 years after the action, the general limitation period under Bulgarian law, to establish or defend legal claims
Integration data, conversation history and saved reports held for a customer
How long we keep it: As described in Section 5, then deleted under Section 7 of our DPA
Website analytics (Google Analytics)
How long we keep it: User-level and event-level data: 14 months. Google keeps aggregated reports longer
Cookie consent records
How long we keep it: Up to 5 years, to show that we respected your choice
Business contact data (prospects)
How long we keep it: Until you object or, if earlier, 24 months after our last contact. If we have not contacted you within one month of obtaining your details, we delete them unless another specific lawful purpose permits retention. On objection, we keep only the minimum suppression information needed to respect your choice, review it periodically and use it solely to prevent further marketing.
Marketing email subscriptions
How long we keep it: Until you unsubscribe or object; then we keep only a suppression record
Testimonials
How long we keep it: Until you withdraw your consent
At a customer’s choice, we return or delete data processed on its behalf after the end of the services, as Section 7 of our DPA sets out; general controller purposes do not override those instructions. When law requires particular records to be kept, we protect them, use them only for that requirement and delete them when it ends.
10. Security
We protect personal data with measures appropriate to the risk, including encryption in transit (TLS) and at rest, encrypted storage of integration tokens, need-to-know access with multi-factor authentication for administrative access, logging, regular backups, timely security updates and a documented incident-response procedure. Annex 2 of our DPA sets out the measures for customer data. No system is completely secure. This statement does not limit our obligations or your rights under applicable law. If a personal data breach is likely to put you at high risk, we will tell you without undue delay.
11. Your rights
Under the GDPR you can ask to access your personal data and receive a copy, correct it, have it erased, restrict how we use it, and receive it in a portable format or have it sent to another provider, subject to the conditions in the law.
Your right to object. You can object at any time, on grounds relating to your particular situation, to processing based on our legitimate interests; we will stop unless we have compelling legitimate grounds or need the data for legal claims. You can object to direct marketing at any time, without giving a reason, and we will stop using your data for that marketing.
Where we rely on consent, you can withdraw it at any time, without advance notice and without affecting processing before you withdrew. Use the Cookie settings link for cookies, the unsubscribe link in our emails, or contact support@aimar.chat.
We respond without undue delay and within one month of receiving your request. If a request is complex, or there are many requests, we may extend this by up to two further months; we will tell you within the first month and explain why. We may ask for proportionate information to confirm your identity. Requests are free unless they are manifestly unfounded or excessive. For data we process solely for a customer, we refer your request to that customer and assist it.
You can complain to a data protection authority. Ours is the Commission for Personal Data Protection, 2 Prof. Tsvetan Lazarov Blvd., 1592 Sofia, Bulgaria, www.cpdp.bg. You can also complain to the authority in the EEA country where you live or work, or where the alleged infringement took place. You do not have to contact us first.
12. If you are in the United States
When we process information for a customer, DPA Section 10 governs applicable US processor and service-provider duties. For information AIMAR controls, you may contact support@aimar.chat to request access, a copy, correction or deletion, and to ask about the categories, sources, purposes and recipients described in Sections 2, 3 and 6. We do not sell personal information, share it for cross-context behavioral advertising, use it for targeted advertising or use sensitive personal information to infer characteristics about you. Where US state law applies, we honor the rights, verification requirements, authorized-agent rules, response deadlines and exemptions it provides without discrimination. You may appeal a refusal by replying with “Appeal” in the subject line; our response explains any applicable route to the competent state authority. We apply a one-month initial response target, with any extension explained within that month and limited by the law that governs your request. We do not require an account to make a request. Verification is proportionate and information collected for it is used only for verification, security and the request. A state-specific notice, notice at collection or opt-out mechanism required for the relevant processing is provided before that processing begins; this general section does not replace a legally required supplement.
13. Age and restricted data
The Service is for business and professional users aged 18 or over, as our Terms state, and is not directed at children. Customers must not submit children’s data, special-category data, criminal-offence data or other restricted information unless AIMAR has expressly agreed in writing and our DPA permits it. If such information is submitted without authorization, contact support@aimar.chat so we can deal with it under applicable law and the relevant instructions. If you believe we hold a child’s personal data, contact us and we will delete it.
14. Changes to this Policy
We update this Policy when our practices or legal requirements change, and we revise the date at the top. We give customers additional notice of material changes by email or in the Service before they take effect, and we ask for new consent where required. An update alone does not give consent for new processing.
15. Contact
Adithana Marketing LLC, 11 G Prof. Hristo Vakarelski Str., 1700 Sofia, Bulgaria. For questions or requests about this Privacy Policy, email support@aimar.chat with “Privacy” in the subject line.