Privacy Policy

1. Who is responsible for your data

Individual Entrepreneur Mariia Lomidze operates both Dignity Ads and Dignity Agency. Contact: [email protected]. Identification code (TIN): 01901165760. Address: Georgia, Tbilisi, Samgori district, Samgori settlement, building 29, apt 32.

We are the controller for website inquiries, platform registration, account administration and our own business records. When we process personal data on a client's behalf as part of agency services, the parties' roles and instructions depend on the actual service and applicable law. Where a processing agreement is required, it must be agreed with that client; website registration does not replace it.

2. Information we collect

Account information: first and last name, username, email address, password hash, account settings and account verification records when you register. Passwords are hashed before storage.

Inquiries and support: name, email, telephone number, preferred contact channel and information you choose to include in an inquiry or support request.

Platform content: project details, website URLs and website content used for audits, prompts, uploaded creative materials, generated outputs, chat history and task records when the relevant features are used.

Integration information: OAuth authorization records and refresh tokens, advertising account identifiers and the advertising data described below when an account is connected. Creating a Dignity Ads account does not itself grant access to a Google account.

Technical information: IP address, browser and device information, request and security logs, page visits and consent preferences. Website analytics is separate from advertising account data obtained through APIs.

3. Google Ads API access and use

The Google Ads connection uses OAuth permission https://www.googleapis.com/auth/adwords. The person authorizing the connection must have the required Google Ads access. For agency work, an authorized team member can use access through our Google Ads manager account (MCC) and select the relevant advertising account. Linking an account to an MCC and authorizing the application are separate access steps.

Depending on the functions used, the integration reads accessible account and manager identifiers, account names, currency and time zone; campaigns, ad groups, ads and their settings; budgets and bidding information; performance statistics such as impressions, clicks, cost and conversions; conversion action definitions and aggregated conversion results; search terms, placement reports and campaign change records.

We use this information to show advertising reports, review search terms and placements, detect performance anomalies, prepare AI-assisted analysis and recommendations, and carry out supported advertising changes. Available operations include budget changes, negative keywords and placement exclusions. Actions are limited by the Google permissions, application controls and the authority granted for the relevant account.

The data and operations available depend on the connected account, its permissions and the functions enabled for that integration. Descriptions of the platform as a whole do not mean that each function is available for every advertising platform.

4. Google user data and Limited Use

Dignity Ads' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements where applicable.

Google API data is used for the disclosed advertising account features, not sold to data brokers, used for unrelated profiling, or used to train general-purpose AI models. Advertising account management and analysis are the purpose of the integration; this does not authorize reuse of Google user data for unrelated advertising or audience targeting.

Access by our team is for authorized account management, support, security and other purposes permitted by the applicable Google policies and law. Where affirmative permission for human access or transfer to an AI provider is required, that permission must be obtained before the access or transfer. A general website inquiry is not that permission.

5. AI processing and service providers

Exa supports web search and content retrieval for website and competitor research; it receives the search queries and URLs needed for those tasks. AI features send the information needed for the requested task to OpenRouter and the model providers used for that request. This can include prompts, briefs, website content, creative materials and selected campaign information or report results. AI conversations, tool results and generated answers can also be stored in our platform's task and chat records.

OpenRouter routes requests to model providers; the selected model and provider can vary by feature and configuration. External AI processing is subject to the retention and data-use arrangements applicable to the selected providers. Contact us for the arrangements relevant to your use before submitting confidential or personal information for AI processing.

Hetzner hosts our websites, application and database in Germany. We make daily backups and retain the latest seven copies. Backup rotation is separate from deletion in active systems. Migadu handles corporate email and application verification and password recovery messages. Other recipients can include providers of website analytics and anti-abuse checks, and messaging services used for inquiries or notifications. Website inquiries submitted through our contact form are sent to our team through Telegram. We do not sell personal data.

Our business is based in Georgia. Hosting, AI, email and other service providers may process data in other countries. Where data protection law requires a transfer mechanism or a processing agreement, these must be in place before the relevant processing. Contact [email protected] for information about the recipients and arrangements applicable to your data.

6. Purposes and legal grounds

We use registration and account information to provide access, verify accounts, send necessary service messages and handle support. We use inquiries to respond and discuss potential agency services. Platform and integration data supports the features and services described above.

Where GDPR applies, the legal ground depends on the purpose: steps requested before a contract or performance of a contract with the individual; legitimate interests in business communications, service operation and security where those interests are not overridden; consent where required, including optional tracking; and legal obligations. Client data processed on instructions is handled under the applicable client arrangement rather than a claim that every client data subject has a contract with us.

Standalone paid software subscriptions are not currently offered. Agency services, fees and invoices are agreed separately from platform test access.

7. Storage, security and retention

The platform stores account records, imported advertising data, project content and task history in its application databases and storage. Google Ads refresh tokens are stored in encrypted form using AES-GCM; account passwords are stored as hashes. Workspace access controls restrict access to connected accounts.

Platform account records and conversations have no automatic expiry and remain until the account or relevant conversation is deleted. We review unsuccessful inquiries and related correspondence monthly and delete them after 12 months without substantive communication, counted from receipt where no discussion followed, unless a continuing justified need requires retention. Payment, dispute and publication-approval records are handled separately. Security logs are kept as needed to investigate incidents and protect the service. Legal obligations and the establishment or defence of claims can require longer retention of specific records.

To request deletion, contact [email protected]. We assess which records can be deleted and which must be retained for a lawful reason. Disconnecting an integration does not necessarily remove earlier AI conversations, reports, operational logs or copies held by service providers. Our deletion review includes records covered by your request and takes account of applicable retention obligations.

8. Disconnecting Google Ads and withdrawing access

An authorized workspace owner or administrator can disconnect Google Ads in the platform. The disconnect operation removes the workspace's selected advertising account and its related imported account data, and removes the saved OAuth connection when no remaining account link uses it. Disconnect can be blocked while an import is active; in that case, wait for it to finish or contact support.

The Google account holder can separately revoke the application's authorization through their Google Account connections settings. A client can manage or remove the agency's manager-account access in Google Ads. Removing MCC access, revoking Google authorization and deleting copies already stored by Dignity are distinct operations. Revocation stops future authorized access under that grant; it does not by itself delete earlier records.

9. Your choices and rights

Depending on applicable law, you may request access, correction, deletion or portability of your personal data, object to processing, or request a restriction. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing. You may also complain to the competent data protection authority.

Contact [email protected] with your request. Our team passes deletion requests to the developer for administrative processing. Projects in another owner’s workspace may remain with that owner; account deletion does not promise deletion of all shared business records or external copies. We may need to verify your identity and authority over the relevant account. If we process the data for an agency client, we may need to refer the request to that client or act on its instructions. Do not send passwords or OAuth tokens with a request.

10. Cookies, external services and changes

Our website uses browser storage for consent preferences and Google Analytics with consent settings. The Google tag is loaded on the website; denying cookie storage is not a promise that no network request or cookieless measurement is made. See our Cookie Policy for controls. Data sent when you follow a link to an external service is also subject to that service's policies.

We will update this policy when our practices change. New Google data uses or additional permissions require updated disclosures and any consent required by Google policy and applicable law before the new use begins.