Privacy Notice
How personal information may be handled when businesses use the service.
01 Information involved
Depending on the enabled service, information may include account and authentication records; business and team details; campaign briefs, assets, plans and approvals; connected-account references; lead and contact information; messages and suppression records; quotes, payments and financial records; support enquiries; and technical or security logs. This list is a review baseline, not confirmation that every category is collected.
02 How information is used
Information may be used to authenticate users, administer business workspaces, plan and execute customer-approved campaigns, manage authorized connections, handle leads and eligible follow-up, process payments, provide support, prevent abuse, preserve approval evidence and provide reporting. The applicable purpose and legal basis depend on the activity and require review.
03 Sharing and providers
Information may be shared with authorized workspace users and providers needed for the selected service. The public site requests Google Fonts, and an SMTP email sender is wired into the application; actual deployment use, provider roles, data involved and processing locations must be verified before publication. A provider is not described as a subprocessor solely because an integration or package is present.
04 Our role
This Notice explains how the contracting entity that must be identified before publication handles personal information in connection with TheAdcentric. Our role depends on the activity. Account administration, support, billing and security may be managed by the platform operator. Some campaign data may be handled on documented customer instructions. Some providers may act independently under their own terms. The final role allocation requires review. If no legal entity is configured, the operator must be identified before publication.
05 AI-assisted features
Before publication, the AI provider, information sent, processing location, retention and provider training settings must be verified. Credentials and unnecessary personal information must not be sent to an AI provider. No claim about provider training or retention is made here.
06 Retention and deletion
No final retention schedule has been approved. Configured OTP, session, invitation or consent validity periods do not establish deletion periods. Retention, backup handling, provider-side copies and deletion capabilities must be verified for each data category before publication.
07 Requests and choices
Privacy requests must be verified and handled within the applicable role and legal requirements. Marketing withdrawal, provider disconnection, contact deletion, account closure and business-workspace deletion are separate actions. Contact details and the request process must be added before publication.