1. About this policy and who is responsible
This policy explains how PostLimn handles personal information when you use our website and visual content planning, collaboration, scheduling, conditional publishing and AI features. Personal information identifies someone or can reasonably be linked to them. Read this policy alongside our Terms and Conditions.
PostLimn is operated by AUTOTHINK SOLUTIONS TECHNOLOGIES, a private company registered in South Africa under registration number 2026/876619/07. PostLimn is the product brand.
Company address: 10 Pancras Road, Homestead Park, Johannesburg, Gauteng, 2092, South Africa.
For account administration, security, support and our own operations, we act as the responsible party or controller. When a business customer determines how personal information in its workspace is used and we process it on that customer’s instructions, the customer generally acts as controller and we act as operator or processor. That customer’s notice also matters for its information.
Contact privacy@postlimn.com for privacy questions or requests and support@postlimn.com for product help. Please do not send passwords, access tokens or payment-card details.
2. Information you provide
- Account and profile: name, email address, sign-in credentials, authentication identifiers and preferences. We use an authentication provider to process sign-in details; Google sign-in also provides the profile information authorised in that flow.
- Workspace and publishing: campaign and blueprint names, captions, canvas nodes and connections, destinations, schedules, media, publishing conditions and delivery results.
- Collaboration: invitation addresses, names, roles, delegated permissions, messages, content references, review feedback, approval decisions and related activity records.
- AI assistance: prompts, responses and workspace context used by the assistant, which may include draft content, account names, platform identifiers and schedules.
- Conditional inputs: locations and time zones selected for weather or air-quality checks, product or service-status URLs, condition settings and resulting observations. A selected location is not necessarily your current device location.
- Support and privacy requests: contact details, message contents, and information you choose to send. Account closure records include the requesting account, confirmation time, cleanup progress and outcome.
Information needed to authenticate you is necessary to provide an account. Connecting a platform, using AI and configuring publishing conditions are optional. You must have permission to provide other people’s information and content.
3. Information from connected services
A connected service’s authorisation screen describes the permissions requested. OAuth lets you authorise access without giving PostLimn your social or cloud account password. We receive account information and access tokens, and refresh tokens where provided, to perform the connected features.
The table explains information used by connected features. Availability depends on provider approval, account type and permissions; listing a platform does not mean every feature is enabled or approved.
| Service | Information used for connected features |
|---|---|
| Facebook Pages | Authorised Page names and identifiers, permissions and tokens, publishing instructions and results, and available Page or post metrics. |
| Professional-account identifiers and usernames, tokens, selected media and captions, publishing results, and available account or post insights. | |
| Threads | Account identifiers and profile information returned by the API, tokens, post content and results, and available insights. |
| LinkedIn Pages | Organisations you are authorised to manage, their identifiers and names, permissions and tokens, and content, publishing results or metrics available to the integration. |
| TikTok | Account identifiers and profile information, tokens, selected videos and publishing settings, and upload or publication results, subject to the permissions granted. |
| Google Drive and Dropbox | Connected-account information, tokens, selected file identifiers, names, types and metadata, and file contents needed for previews, importing or publishing. Cloud permissions may permit broader read access than the files you select. |
| YouTube, where enabled | Channel identifiers and details, tokens, videos and publishing instructions, publication results, and available channel or video statistics. YouTube functionality is still being prepared; this is not a promise of current availability. |
Cloud-file access can involve retrieving file contents through our infrastructure and making delivery copies needed by the destination platform. Provider metrics may include followers, views, impressions or engagement where available; their definitions and reporting delays differ.
Facebook, Instagram and Threads information is used for the connections, publishing and reporting you authorise. Reports identify the platform and account. A snapshot records an available count at collection time; observed change compares compatible daily snapshots and is a net difference between those checks. Missing or unavailable metrics are shown separately from zero. Reporting does not establish the exact time of each view, follow or other interaction.
Google sign-in and Drive access are separate choices. Google API data is subject to the Google API Services User Data Policy, including applicable Limited Use requirements. Where enabled, PostLimn uses YouTube API Services; see the Google Privacy Policy and YouTube Terms of Service. Revoke Google access through your Google account permissions.
4. Technical and usage information
We and our service providers process request and connection information, including IP addresses, browser or device information supplied with requests, timestamps, pages requested, errors and security events. Activity records may identify an account, workspace, action or publishing job.
These records support service operations, troubleshooting, abuse investigations and user support. Retention depends on the purpose of the record and the systems that hold it.
Our contact form also uses an anti-abuse check that processes browser and connection information to distinguish genuine requests from automated abuse.
5. How and why we use information
- Create accounts, authenticate requests, maintain sessions and remember functional preferences.
- Save workspaces, retrieve or preview media, and carry out authorised publishing instructions.
- Evaluate configured conditions and record whether they permit delivery.
- Provide connected-account reporting, invitations, permissions, messages and content reviews.
- Generate requested AI assistance, restore saved conversations and apply service safeguards.
- Send operational communications, respond to support requests and resolve failures.
- Protect accounts and systems, enforce agreements, resolve disputes and meet legal obligations.
Where applicable law requires a legal basis, we rely on performance of a contract for requested services; legitimate interests in operating, troubleshooting and securing the service; legal obligations; and consent where required for a particular activity. Our legitimate interests include preventing unauthorised access and resolving failures. Customer-controlled information is processed on the customer’s instructions under the applicable processing agreement.
Authorising an integration is not blanket consent to unrelated uses. A materially different use must be addressed through any required notice or consent before it begins.
7. AI assistance and conversations
The Studio assistant sends prompts and relevant workspace context to our AI service provider for generation and safety checks. PostLimn stores conversation history for saved drafts. Studio requests disable gateway payload logging and response caching.
Use Clear conversation in Copilot to erase that chat. Disconnecting a social account also starts cleanup of Copilot conversations that received its details. Older conversations whose source cannot be established may also be cleared. Whole-account deletion includes saved Copilot conversations.
PostLimn does not use workspace content or connected-service data to train general-purpose AI models. Our AI inference provider does not use customer content to train its models.
Do not include credentials or sensitive personal information in prompts. Review AI output and proposed canvas changes before use or publication: output may be inaccurate or inappropriate. Connected-platform data-use restrictions still apply.
8. Cookies and browser storage
Cookies and browser storage support sign-in, secure connection of accounts, preferences, workspace navigation and the interface. Some invitation and pending-message information is held in the browser tab’s storage. Your browser and third-party sign-in providers may maintain their own state.
Browser controls let you restrict storage, but blocking or clearing necessary cookies can sign you out or disrupt features. Clearing browser storage does not delete server-side records. Optional tracking or marketing technologies, if introduced, require updated disclosures and any legally required choices before use.
9. Retention, disconnection and deletion
We keep active account and workspace records to provide the service. Retention of delivery, security and support records depends on whether they are needed to investigate a failure or abuse, resolve an open request or dispute, or meet a legal obligation. Retention also varies between active records, operational logs and recovery copies. Some copies require separate cleanup rather than automatic expiry. Contact our privacy mailbox about retained information and the period or criteria applicable to your request.
- Deleting a draft or media item differs from deleting your whole account or every historical record.
- When you disconnect a social account, we remove its stored connection credentials and associated publishing and Insights records from the active database. The disconnect preview shows affected delegates and scheduled deliveries. Related saved assistant conversations are also queued for cleanup; independently authored drafts and original uploads remain. Use the provider’s settings to revoke authorisation there, and contact us about other information you want removed.
- Published posts and copies held by other participants or destination platforms may require separate action there.
- Media copies, scheduled work, conversations, logs, caches and backups must be considered in deletion requests. Specific legal requirements may justify retaining some records.
Confirm permanent account closure and deletion in Settings → Privacy & data. New publishing and collection stop, your browser is signed out, and cleanup across our services runs automatically with retries for interruptions. Existing in-flight requests and short-lived media links may take time to expire. We retain minimal closure/security records to prevent old sessions or work from reopening the account. For access, deletion of particular data, or help when you cannot sign in, email privacy@postlimn.com. See our data deletion instructions for the scope of each option.
10. Protecting information
Safeguards include sign-in checks, access permissions and encryption for stored connection credentials. Visibility also depends on the feature and permissions used. No system provides absolute security. This policy does not claim certifications or independent testing that has not been completed.
Report suspected account or service security problems to support@postlimn.com without including credentials. Duties to investigate and notify affected people or authorities depend on the incident and applicable law.
11. International processing
PostLimn operates from South Africa and uses providers that may process information in other countries. Processing locations can differ between service delivery, support, backups and operational records.
Contact privacy@postlimn.com for information about processing locations and applicable transfer safeguards.
12. Your rights and choices
Depending on applicable law, you may request access, correction, deletion, a copy, restriction or portability, or object to certain processing. Where processing relies on consent, withdrawal does not change the lawfulness of earlier processing.
Email privacy@postlimn.com with your account email and request, even if you cannot sign in. We may need proportionate information to verify identity or authority, never your password or token. A business customer may need to handle requests about information it controls, with our assistance under the applicable agreement.
We handle requests promptly and within the time required by applicable law. If verification, an extension or an exception applies, we explain the reason and any available next steps.
- South Africa: POPIA provides applicable access, correction, objection and other rights. Complaints can be directed to the Information Regulator.
- EEA and United Kingdom: where GDPR or UK GDPR applies, relevant rights, legal bases and transfer requirements apply. You may complain to your competent data-protection authority.
- California and other US states: where state privacy law covers our processing, rights may include access, correction, deletion, portability, authorised-agent requests, opt-outs and appeals. You can contact our privacy mailbox to exercise applicable rights.
Applicable identity checks, exceptions and statutory response requirements apply. If marketing communications are introduced, required choices must be provided; opting out of marketing does not necessarily stop essential account or security messages.
13. Children’s privacy
PostLimn is intended for users aged 18 or older acting for themselves or an organisation they are authorised to represent. It is not directed at children. If you believe a child has provided information through the service, contact privacy@postlimn.com so the circumstances and appropriate action can be assessed.
14. Updates and contact
We date updates to this policy and provide notice or seek consent where required by the change.
Privacy: privacy@postlimn.com. Support: support@postlimn.com. Acceptance of contractual terms and consent to optional processing are separate matters.