Privacy and connected-account data.

AVENQORA Privacy Notice

Information you provide

AVENQORA receives information submitted through its forms and workspaces to assess requests, deliver agreed services and provide support.

• This can include your name, organization, contact details, project requirements and support messages.
• Do not submit passwords, one-time codes, API keys or financial credentials through a public form.

AVENQORA Privacy Notice

Connected social accounts

When an authorized operator connects a business account, AVENQORA processes the account or channel identifiers, names, granted permissions and access credentials needed for that connection.

• Social workflows can store draft text, media, account selections, schedules, approvals, recent account posts, publication identifiers, provider responses and activity records.
• Permissions and information available depend on the connected provider and the access actually granted.

AVENQORA Privacy Notice

How information is used

Information supports the requested service: connecting and verifying accounts, preparing drafts, checking recent content, carrying out individually authorized publishing actions, reviewing publication status and handling support or security incidents.

• Connecting an account does not itself authorize a post.
• Provider acceptance is recorded separately from confirmed publication.
• Social drafting currently uses prepared service themes; it does not require sending connected-account credentials to an AI model.

AVENQORA Privacy Notice

Providers and publication

A configured integration exchanges information necessary for the authorized action with Meta, LinkedIn or Google/YouTube. Hosting and configured service providers may process information needed to run the requested service.

• Content authorized for publication may become public on the selected platform.
• Media prepared for publication can be made accessible through an unguessable HTTPS link so the selected provider can retrieve it.
• Optional website assistants or other integrations have their own configured processing paths when those features are used.

AVENQORA Privacy Notice

Access, protection and retention

Private workspace records require authorized access. Connected-account credentials are encrypted at rest in the connector vault. Technical and security records may be retained to operate and protect the service.

• Records are retained for the relevant service, security, dispute-handling or applicable obligations.
• Disconnecting a native connection removes its stored access credentials; related workflow and audit records can remain.
• No system can promise absolute security.

AVENQORA Privacy Notice

Your choices and requests

Use the Contact page to request access, correction, disconnection or deletion. Identify the relevant service and account without supplying passwords or tokens. AVENQORA reviews identity and authority before changing private records.

• The Data Deletion page explains the request steps and the distinction between stored AVENQORA records and content already published on a provider.
• A privacy request is reviewed by a person; submitting a request does not automatically delete data.
• Any justified retention limits are explained during review.