Who we are
Adilm is operated by Params Solution (Pty) Ltd, a company registered in the Republic of South Africa ("Adilm", "we", "us"). This policy explains how we collect, use, share and protect personal information when you visit adilm.ai, use the Adilm app, or otherwise use our services.
For personal information we decide how to process, we are the responsible party under the Protection of Personal Information Act, 2013 ("POPIA"). You can reach us, including our Information Officer, at pm@webparam.org.
Information you put into a workspace
Adilm is used by organisations. When an organisation puts information into its workspace — for example its customers, leads, invoices, documents, or the WhatsApp conversations its customers start — that organisation decides why and how that information is processed. For that information the organisation is the responsible party, and we process it as its operator, on its instructions and for no other purpose.
If you are a customer of an organisation that uses Adilm and you want to access, correct or delete information it holds about you, please contact that organisation directly. We will help it respond.
What we collect
Account information: your name, work email address, password (stored only as a secure hash), the workspaces you belong to and your role in each. If you sign in with Microsoft, we receive your basic profile from Microsoft.
Workspace content: what you and your colleagues ask Adilm's AI employees to do and the conversations that follow, documents you upload, and the records the service keeps for you, such as customers, leads, tasks, invoices, proposals and drafts.
Connected services: when a workspace connects another service, we access the information needed to do the work you ask for. This can include Google Gmail and Calendar, an email account connected over IMAP and SMTP, a Framer project, and a WhatsApp Business number connected through Meta and Twilio — including the phone numbers and messages of the people who contact that number. If you buy a phone number in Adilm, we record that number and the verification messages sent to it.
Social media accounts: when you connect TikTok, YouTube, LinkedIn, a Facebook Page or Instagram, we receive and store the information described under "Social media accounts and posting" below — your account's identifier, name and profile picture, the access tokens the network issues, and records of the posts you publish through Adilm.
Photos and videos: images and videos you upload or record in Adilm so they can be attached to a post, and the pictures Adilm generates for your drafts.
Website forms: when you request access or contact us, we collect your name, work email, company and the roles you are interested in, and anything else you choose to tell us.
Technical information: IP address, browser and device details, logs of requests and errors, and records of how features are used, which we need to run, secure and improve the service.
How we use it
To provide the service: to create and run your account and workspace, to have AI employees draft, prepare and organise work for you, and to carry out the actions you confirm.
To keep the service secure and working: to authenticate users, keep each workspace's data separate from every other, detect abuse, investigate errors and record who did what.
To support and talk to you: to answer requests, send service messages such as security notices, and, where you have asked for it, tell you about Adilm.
To improve the service, and to meet our legal obligations.
We do not sell personal information. We do not use your workspace content to train our own or third-party AI models.
How AI is used
Adilm's AI employees use large language models provided through Microsoft's Azure OpenAI Service. To answer a request, the relevant workspace content is sent to that service for processing. When you ask for a picture for a post, a short description of the scene is sent to Microsoft's Azure AI image service. Under Microsoft's terms, that content is not used to train Microsoft's or OpenAI's models.
AI output can be wrong or incomplete. Adilm is designed so that consequential actions — sending, booking, publishing or invoicing — wait for a person in your workspace to confirm them.
Social media accounts and posting
Adilm's social media AI employee drafts posts, and lets you publish your own photos and videos, and the posts you approve, to the social media accounts you connect: Facebook Pages, Instagram, LinkedIn, TikTok and YouTube. You connect each account yourself, through that network's own sign-in and consent screen, choosing which permissions to grant, and you can disconnect it at any time. For each network, we ask only for the permissions below and use them only as described.
Facebook Pages (Meta): when you connect Facebook through Facebook Login for Business, you choose which Pages to give Adilm. We receive and store each Page's ID and name and its Page access token (encrypted at rest); we do not store your personal Facebook profile, friends or messages. With pages_show_list we list the Pages you manage so you can pick them; with pages_manage_posts we publish to a Page the posts, photos and videos you confirm, and edit or delete them when you ask; with pages_read_engagement we read a published post's link and how it is doing. Where you turn on comment replies and grant pages_read_user_content and pages_manage_engagement, we read the comments on posts you published through Adilm and post the replies you or Adilm write.
Instagram (Meta): you connect an Instagram professional (Business or Creator) account through Instagram Login. With instagram_business_basic we receive and store the account's ID, username, name and account type, and an access token (encrypted at rest, renewed while you keep posting). With instagram_business_content_publish we publish to that account the photos and Reels you confirm, with your caption, and keep each post's ID and link. Where you turn on comment replies and grant instagram_business_manage_comments, we read the comments on posts you published through Adilm and post the replies you or Adilm write.
LinkedIn: you connect your LinkedIn member account through Sign In with LinkedIn. With openid and profile we receive your LinkedIn member ID and name to show which account is connected; with w_member_social we publish to your LinkedIn profile the posts, photos and videos you confirm, and edit or delete them when you ask. We store your member ID, name, an access token (encrypted at rest) and the ID of each post you publish. LinkedIn does not let us read your feed, connections or messages, and we do not.
TikTok: when you connect a TikTok account through TikTok Login Kit, we receive and store your TikTok account identifier (open ID), display name and profile picture (the user.info.basic scope), and the access and refresh tokens TikTok issues, which we encrypt at rest. Before each post we read the posting options TikTok returns for your account, such as the privacy levels available to you and the longest video you can post. When you publish (the video.publish scope), we send TikTok the video and caption you chose, together with the settings you selected — who can view it, whether comments, duets and stitches are allowed, and whether it is promotional or branded content — and we keep the post's identifier and its status.
TikTok stats: to show you how your TikTok account is doing, Adilm's Stats view reads, when you open it, your profile link, bio and whether your account is verified (the user.info.profile scope); your follower, following, like and video counts (the user.info.stats scope); and your most recent public videos — their title, cover image, link, date, length and view, like, comment and share counts (the video.list scope). This is read live from TikTok each time you open the view, shown only to people in your workspace, and not stored by Adilm. We do not read other people's accounts, your private videos, your followers' identities or your messages.
YouTube (Google): you connect a YouTube channel through Google's consent screen. With youtube.upload we upload to your channel the videos you confirm, with the title, description, tags and privacy setting you chose; with youtube.force-ssl we read your channel's ID and name and, where you turn on comment replies, read the comments on videos you published through Adilm and post replies; with yt-analytics.readonly we read how those videos are doing. We store the channel ID and name, and access and refresh tokens (encrypted at rest). Adilm's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Adilm uses YouTube API Services: by connecting YouTube you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google's Privacy Policy (https://policies.google.com/privacy) applies to Google's handling of your information.
We use information from these networks only to show which accounts are connected, to publish the content you select and confirm, to show you where each post went and how your account and posts are doing, and — when you turn it on — to read and answer comments on your own posts. Nothing is posted to a social media account until a person in your workspace confirms it.
We do not sell information we receive from Meta (Facebook and Instagram), LinkedIn, TikTok, Google (YouTube) or any other social network; we do not use it for advertising or to build profiles of the people who see or comment on your posts; we do not share it with anyone except as this policy describes; and we do not use it to train our own or third-party AI models.
Who we share it with
We share personal information only with service providers who process it for us under written obligations to protect it, and only as far as they need to:
Amazon Web Services (AWS), which hosts the platform and stores its data in its Africa (Cape Town) region; Microsoft, which provides AI processing through Azure OpenAI and generates pictures for drafts through Azure AI; Twilio, which provides WhatsApp messaging and phone numbers; Meta, which operates the WhatsApp Business Platform; and Google and Microsoft, when you use them to sign in or connect an account. When you connect your own email account, we exchange messages with that provider on your behalf.
Social networks you publish to: TikTok, Google (YouTube), LinkedIn and Meta (Facebook and Instagram) receive the posts, photos, videos and captions you choose to publish to your accounts with them, when you publish. Each network handles that content under its own terms and privacy policy. To write captions, the text of a draft is processed by Azure OpenAI as described above; your social media access tokens and account information are never sent to an AI model.
We may also disclose information where the law requires it, to protect the rights and safety of our users or the public, or to a successor if our business is sold or reorganised, in which case this policy continues to apply.
Transfers outside South Africa
Some of our service providers process information outside South Africa, including in the United States — for example AI processing through Azure OpenAI, and messaging through Twilio and Meta. We transfer personal information across borders only as POPIA permits: to recipients bound by law, binding corporate rules or agreements that provide an adequate level of protection, or where the transfer is necessary to provide the service you asked for.
How long we keep it
We keep personal information for as long as your account or workspace is active and as long as we need it for the purposes in this policy. Workspace administrators can set how long conversations are kept.
When a workspace is closed, or on a valid deletion request, we delete or de-identify its information within a reasonable time, unless the law requires us to keep it longer — for example financial records.
Photos and videos you upload to publish are kept only as long as publishing needs them. A video is deleted as soon as every network you sent it to has published it; if a network failed, it is kept for one more day so you can try again, then deleted. An upload that is never saved on a post is deleted after three days. After that we keep only the link to each published post, not the video itself.
Social media access tokens are kept while the account stays connected. When you disconnect an account in Adilm, we delete its tokens straight away; a token the network has revoked no longer works, and is deleted when you disconnect or reconnect the account.
How we protect it
Information is encrypted in transit. Credentials for connected services are encrypted at rest with keys held separately from the database. Each workspace's records are isolated from every other workspace at the database level, access is limited by role, and actions are recorded in an audit trail.
No system is completely secure. If a security compromise affects your personal information, we will notify you and the Information Regulator as POPIA requires.
Your rights
Under POPIA you may ask whether we hold personal information about you and request access to it, ask us to correct or delete it, object to its processing, and withdraw any consent you have given. Workspace administrators can also export their workspace's data from within Adilm.
To make a request, email pm@webparam.org. We may need to verify your identity first. If you are unhappy with our response, you can complain to the Information Regulator (South Africa) at www.inforeg.org.za.
If you are in the European Union or the United Kingdom, you have equivalent rights under the GDPR, and can exercise them the same way.
Deleting your data
To delete your Adilm account and the personal information we hold about you, email pm@webparam.org from the email address you sign in with, with the subject "Data deletion request". Tell us your name and, if you want a whole workspace deleted, the workspace's name. Only a workspace administrator can ask us to delete a workspace.
Before you ask, workspace administrators can export the workspace's data from within Adilm, and can disconnect any connected service — such as Google, email or WhatsApp — under Connections, which stops our access to it straight away.
If you connected Adilm to Facebook, Meta or WhatsApp, you can also remove Adilm's access on Facebook under Settings & privacy > Settings > Business integrations, then email us as above so we also delete the information we received through Meta.
To stop Adilm's access to a social media account, disconnect it in Adilm under Connections, which deletes its tokens straight away. You can also revoke access from the network itself:
Facebook Pages: Settings & privacy > Settings > Business integrations, then remove Adilm. Instagram: Settings and activity > Website permissions > Apps and websites, then remove Adilm. LinkedIn: Settings > Data privacy > Permitted services, then remove Adilm. TikTok: in the TikTok app, Settings and privacy > Security > Manage app permissions, then remove Adilm. YouTube: in your Google Account, Security > Your connections to third-party apps & services, then remove Adilm (https://myaccount.google.com/connections).
Removing Adilm on the network stops our access at once. To have us delete the information we received from that network as well — the account details and the records of your posts — email us as above, and we will do so within 30 days.
We confirm your request by email, may ask you to verify your identity, and complete the deletion within 30 days. We delete your account, the workspace content you asked us to delete, the credentials for connected services, and the information we received from Meta and other connected services. Records the law requires us to keep, such as financial records, are kept only for as long as required and then deleted.
If you are a customer of a business that uses Adilm — for example you messaged it on WhatsApp — please ask that business to delete your information. You can also email pm@webparam.org, and we will pass your request to the business and help it respond.
Cookies and local storage
The Adilm app uses strictly necessary cookies to keep you signed in. The website remembers your light or dark theme choice in your browser. We do not use advertising or cross-site tracking cookies.
Children
Adilm is a business service and is not intended for anyone under 18. We do not knowingly collect personal information from children.
Changes to this policy
We may update this policy as the service changes. The date at the top shows when it last changed, and we will tell workspace administrators about material changes before they take effect.
Contact us
Params Solution (Pty) Ltd — pm@webparam.org