Aurvandil Marketing Hub · Privacy
Your content.
Your publishing decisions.
This policy explains how Aurvandil Marketing Hub handles information used to prepare, approve and publish company marketing content.
Effective date: November 1, 2026
1. Scope and responsible organization
Aurvandil Marketing Hub is a Windows desktop application currently used internally by Aurvandil in California, United States, to organize marketing content, review and approve posts, prepare content for individual platforms, and manage publishing workflows. This policy covers the Hub and its intended LinkedIn connection. The Hub is also intended to support Aurvandil’s YouTube, Instagram, Facebook, TikTok and Pinterest accounts. Naming a platform here does not mean its connection or live publishing is active. Platform-specific data and permission disclosures will be updated before those connections are activated. This policy does not describe the separate privacy practices of other Aurvandil products or the hosting website.
The organization responsible for this processing is Aurvandil Technologies Inc. Contact: Inquiries@Aurvandil.Tech. Postal address: 1010 Helen Power Dr #1082, Vacaville, CA 95687, United States.
2. Current LinkedIn status
The intended initial destination is the Aurvandil Technologies company Page. Local development and testing have been completed for the planned channel expansion. Live LinkedIn authorization and publishing have not been activated. The descriptions below explain the intended connection once access is granted and the relevant functions are enabled. They do not indicate LinkedIn approval or endorsement.
3. Information handled
- Operator and security records: local operator account details, password hashes, sessions and activity records.
- Marketing work: brands, products, campaigns, destination-account mappings, draft captions, uploaded media, planned publishing times, review decisions and approval history. Content may contain personal information supplied by an operator.
- LinkedIn connection records, once connected: organization identifiers, granted authorization scopes, token-expiry information and access credentials.
- Delivery records, when applicable: publishing jobs, attempts, errors, reconciliation records and publication identifiers.
Operators supply account and marketing information through the Hub. Connection and delivery information is received or generated during authorization and platform operations. Platform analytics are currently unavailable. The Hub does not currently collect LinkedIn impressions, engagement analytics, messages, contacts or unrelated member-profile information.
4. Why information is used
The Hub uses this information to control operator access, organize content and campaigns, record review decisions, and manage approved publishing work. Once connected and separately enabled, LinkedIn access is intended to verify the administrator’s required Page role and granted permissions, upload approved media, publish content covered by an exact saved approval, record outcomes, and resolve failed or uncertain delivery. Connection information is handled during authorization and relevant checks; delivery records arise when those operations run.
5. LinkedIn permissions
The implemented authorization flow requests rw_organization_admin and w_organization_social. Access has not yet been granted. LinkedIn describes these permissions as covering Page administration and reporting, and organization posting, commenting and liking, respectively. These permission capabilities are broader than the Hub’s intended use described here: checking Page authorization and publishing approved company content. Reporting, commenting and liking are not described as current Hub features.
Available access depends on LinkedIn’s approval, the administrator’s role and the permissions actually granted. Authorization does not by itself enable live publishing in the Hub.
6. Storage and safeguards
The operational database and media library are stored locally on the Windows computer running the Hub. The Hub’s local service listens on that computer’s loopback interface. Aurvandil’s public website does not host the operational Hub database.
LinkedIn access tokens are encrypted using Windows protection tied to the selected Windows account, with restricted filesystem access. Tokens are not stored as plaintext in the database or returned through the dashboard API. These protections do not mean that the entire database or media library is encrypted at rest. No security measure guarantees absolute protection.
7. Sharing and service providers
Once authorization and the relevant functions are enabled, approved content and the authorization information necessary for selected operations are transmitted to LinkedIn. Content published to the company Page becomes available according to LinkedIn’s service settings and practices. LinkedIn handles information under its Privacy Policy.
Encrypted backup files are stored in Aurvandil’s Microsoft 365 SharePoint library and synced through OneDrive. Microsoft therefore provides storage and synchronization for those backup files.
The Hub does not use AI services, additional cloud storage, analytics services or error-reporting services beyond the social-platform operations and Microsoft backup arrangement described here. Website hosting and any website-specific cookies are separate from the Hub’s operational data practices.
8. Retention and backups
We apply the following retention schedule. Cleanup is managed manually unless a specific application function provides otherwise; these periods do not mean automatic deletion is implemented.
- Final marketing assets, approvals and internal publication history: up to five years after campaign completion where needed to document business activity and publishing decisions. Records no longer needed for that purpose are removed sooner.
- Unused drafts and unused uploaded media: deleted after 12 months of inactivity through manual cleanup.
- Operator accounts: retained while authorized access is needed. Access is removed when no longer needed; related approval and activity records follow their separate retention periods.
- Sessions and routine technical logs: sessions expire according to the application’s settings. Routine technical logs are retained for up to 90 days. Selected publishing evidence retained for business history follows the schedule above only where platform requirements permit.
- Platform credentials and API-derived information: retained only as needed for an authorized connection and permitted operations, subject to the relevant platform’s storage and deletion requirements. The five-year business-record period does not override those requirements.
For LinkedIn, we will immediately delete information collected through its APIs on a user’s behalf, including associated tokens, when that user requests deletion or closes their Hub account, except where deletion would violate a law or an obligation imposed by a governmental authority. This commitment applies to affected copies as well as active records. Separately supplied marketing content is assessed under its own retention category.
The selected backup policy is a manual encrypted backup each week, with a Sunday-evening reminder and a 30-day retention target. Backup creation and cleanup require manual action. Automatic expiry or deletion is not implemented, so a backup may remain beyond the target until cleanup is performed.
Backups contain the database, registered media and limited safe configuration. Credential-vault files are excluded. The 30-day backup target does not define how long operational records remain in the Hub.
9. Disconnecting and revoking LinkedIn access
Local disconnect removes the active LinkedIn grant metadata and credential reference, pauses scheduled work, and attempts to remove the encrypted credential file. Cleanup failures are reported. Local disconnect is separate from revoking the authorization held by LinkedIn.
To revoke access at LinkedIn, open Me → Settings & Privacy → Data privacy → Other applications → Permitted Services, then choose Remove beside the service. LinkedIn provides current removal instructions.
Disconnecting does not automatically delete drafts, media, approval history, audit records, existing backups or posts already published on LinkedIn. Published posts must be managed separately on LinkedIn. For information held by Aurvandil, use the request process below.
10. Privacy and deletion requests
Send privacy questions or requests for access, correction or deletion to Inquiries@Aurvandil.Tech, with the subject “Marketing Hub privacy request.” Identify the account or content involved and describe your request. Do not send passwords or access tokens.
The person responsible for operating the Hub currently handles requests received at this address, checks identity and authority using only necessary information, identifies affected active records and backups, carries out required action, and confirms the outcome or explains any lawful limitation.
We aim to acknowledge privacy requests within five business days and respond within applicable legal deadlines. Where platform terms require earlier action, including immediate deletion of LinkedIn API-derived information in the circumstances described above, we act according to those requirements rather than waiting for the acknowledgement period.
Requests are handled manually through the privacy contact above. We assess affected active records and backup copies and take steps to prevent information deleted in response to a request from being reintroduced during a restore. If a request cannot be completed, we explain the reason and any available next steps.
The Hub does not currently offer a self-service account-deletion function. A privacy request is distinct from using local disconnect or revoking access at LinkedIn.
11. Applicable privacy rights
Depending on the law that applies to your information, you may have rights to access, correct or delete it; restrict or object to processing; receive a portable copy; withdraw consent where processing relies on consent; or complain to a relevant authority. These rights and any exceptions depend on the applicable jurisdiction. Use the contact above to make a request.
The Hub is currently used internally in California, United States. This policy does not extend its availability to customers. For a concern about our handling of a request, contact us at the address above. You may also contact a privacy regulator where applicable law provides that option.
12. Policy changes
We will update this page and its effective date when practices change. We will notify affected operators before material changes take effect and obtain any authorization required for a new use of LinkedIn information.
Privacy contact: Inquiries@Aurvandil.Tech · Aurvandil Technologies Inc · 1010 Helen Power Dr #1082, Vacaville, CA 95687, United States.