Alkansa Privacy Policy
Last updated on November 13, 2026.
1. Data controller
Alkansa is run by the Alkansa team. Legally, the controller of your data is Marcos Vinithius, established in Portugal. For any privacy matter, contact the team at contact@alkansa.app. We have not appointed a data protection officer (DPO), because the law does not require one for our activity; that contact handles requests.
2. Data we process
- Account: name, email, profile photo, language, time zone, theme and login sessions. If you sign in with Google, we use your Google account name, email and photo; the photo is copied once to your account, and you can change or remove it in My account.
- Team: the people in each account, their roles, invitations and who created each post.
- Connected social networks: identifier, username and name of the account or page, permissions granted, connection validity and the access tokens, which we store encrypted. When you disconnect an account, we keep for up to 1 year only its identifier on the network, the name it had in Alkansa and the projects it belonged to, so its publishing history returns to it if you connect it again; no token and no content. If you connect a Facebook Page linked to an Instagram account, we also store that Instagram account's identifier as reported by Meta, to know which Page can like comments on its behalf.
- Content: uploaded images and videos, templates, colors, texts, captions, schedule and the result of each post (for example, the address of the published post).
- Post results: the numbers of each post published through Alkansa (views, reach, likes, comments, shares and saves and, on Instagram, how many people followed and visited the profile from the post, as each network reports them), read a few times in the 30 days after publishing; each connected account's follower count, once a day; and, when the network reports them (on Instagram and Facebook, only for accounts with 100 followers or more), the account's daily totals: how many people followed and unfollowed, reach, views and profile visits. These are only daily totals: we do not know who those people are. The goals and tests you create for a brand (or approve when the AI suggests them) are stored with the account. The comments on those posts (the text, the commenter's public name or handle and the date) are read when you open them or ask for the ones waiting for a reply, and are not stored. The replies you publish go to the network, and Alkansa does not store their text. For the comments your account liked on Instagram through Alkansa, we keep only the comment's identifier and the date, because Instagram does not report this; no text. On TikTok, only on accounts where the feature is on: the numbers of the videos published through Alkansa (views, likes, comments and shares) and the follower count.
- Direct messages: only on accounts where you turn on the inbox or auto-reply: the text of the messages exchanged with each person, their public name or handle, the address of their profile photo on the network (the image is not copied; the address expires and is fetched again) and the dates, and a record of each auto-reply sent. When the auto-reply has a button and a link, we record whether the person tapped the button, whether they opened the link and when (the link goes through an Alkansa address that counts the click and leads to the destination), and whether they got the reminder. Anyone who replies STOP is marked so they get no more automatic messages.
- Phone and Telegram notifications: only if you turn them on in Settings: each device's delivery address (Web Push) or your Telegram chat, and the topics you chose. A new comment or message notification carries the name or handle of who wrote, the network and the start of the text, and goes only to the devices and Telegram you turned on.
- Billing: plan, subscription status, payment and invoice history and the Stripe customer identifier. Card details stay with Stripe and never reach us.
- Communications: emails we exchange with you and the notices we send (invitations, plan changes, waiting list confirmation).
- Technical data: IP address, browser, times and errors, and the anti-bot check at sign-up. We use the IP only for security, such as blocking repeated sign-in attempts and investigating abuse; never for advertising or profiling.
- alkansa.app website: the email and language of people who join the waiting list and, only with your consent, visit and campaign measurement data.
3. Social network data
We ask the networks only for the permissions needed to identify the connected account, publish what you approve (posts, carousels and stories), show you how those posts perform and handle their comments when you tell us to. We read the posts published through Alkansa (their numbers and their comments when you open them, without storing them) and, on Instagram, Facebook and Threads, the account's own posts published outside Alkansa, from the 90 days before the account is first read onward: the identifier, the date, the link, the start of the caption, the address of the thumbnail on the network (the image is not copied) and their numbers, to show the results of every post of the account. We also read the account's follower count and, when the network reports them, its daily totals (how many followed and unfollowed, reach, views and profile visits), which are also just numbers. On accounts where you turn on the inbox or auto-reply, the network tells us right away about each new comment and message; we use the comment only to trigger the auto-reply, the notification you turned on and the count of new comments on each post in the Dashboard. We do not store the text: we keep only how many arrived on each post, until someone opens it, and each comment's identifier for 7 days, so the same one is not counted twice. We only reply to, hide, delete or like a comment when you tell us to, on posts published through Alkansa, or when an auto-reply you turned on answers someone who commented. Direct messages are only read and stored on accounts where you turn on the inbox, and only sent when you write, or when an auto-reply you turned on answers, once, someone who commented. We do not write to people who have not talked to the account, and we do not follow, like or comment on our own, we do not know who your followers are, and we do not read third-party or competitor accounts. Data received from the networks (including Instagram, Facebook, Threads, TikTok and LinkedIn) is used only to provide the service to you: we do not sell it, use it for advertising, share it with data brokers or use it to train AI models.
Comments and messages carry data about the people who wrote them: their public name or handle and the text. We process this data only to show it to you and your team and so that you can reply, based on the legitimate interest of whoever manages the account in answering its own audience. Comments are not stored; direct messages are kept for 90 days, as section 9 says. We do not build profiles of anyone and do not use this data for any other purpose.
We handle each network's data according to its rules for developers: the Meta Platform Terms, the TikTok Developer Terms of Service, the LinkedIn API Terms of Use and the Google API Services User Data Policy. In particular: we delete data received from a network when you disconnect the account, when you ask or when the network asks; from LinkedIn, we do not store other members' profile data for more than 24 hours or the content of their posts and comments for more than 48 hours; and Alkansa's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
When you disconnect a network, we delete its tokens. You can also revoke access directly in the network, in the connected apps and websites settings of Instagram, Facebook, Threads, TikTok or LinkedIn.
4. Purposes and legal bases
- Providing the service you signed up for (account, team, creation, publishing, scheduling, post results, support and billing): performance of a contract. Results are shown to you, your team and the AI assistant you connect.
- Complying with legal obligations (invoices, taxes, requests from authorities): legal obligation.
- Security and abuse prevention (technical logs, anti-bot check, publishing limits, spam investigation) and improvements using aggregated data: legitimate interest, balanced so it does not override your rights.
- Measurement and advertising on the alkansa.app website, and launch emails to the waiting list: consent, which you can withdraw at any time.
5. Service providers
We work with providers that process data on our behalf, under a written contract that requires them to process the data only for us, under our instructions and only for the purposes above, and to delete it when we stop using their service:
- Database and sign-in: cloud provider, with data stored in the United Kingdom.
- Google (sign-in and Drive): sign-in is used only if you choose it. Drive is a separate, optional connection using the limited drive.file permission. Alkansa creates its Alkansa folder and restricts operations to that folder and the authorized project; it does not request access to your entire Drive. Only files uploaded through the app appear in the library. Tokens are encrypted; an image imported from Drive becomes a library photo, deleted after 30 days, and a video chosen for publication is copied into that publication's files. The brand kit stays on the server. You can disconnect in the library or revoke access in your Google account permissions; Drive files remain, and prepared publications retain their temporary copy. Deleting your Alkansa account revokes the connection. We do not use these files for advertising or AI training.
- Hosting, network and image storage: cloud provider with a global network, which also runs the anti-bot check at sign-up.
- Stripe: payments and subscriptions.
- Email delivery: provider specialized in the service's emails.
- Error monitoring: specialized provider, with data stored in the European Union. It receives the technical error, the screen where it happened and browser data; it does not receive your email, your name or the content of your posts and messages.
- Telegram and browser notification services (Google, Apple, Mozilla or Microsoft, depending on your browser): deliver the notifications you turn on, with their text, under their own policies.
- Google (Analytics and Ads) and Meta (Pixel): visit and campaign measurement, only on the alkansa.app website and only with your consent.
Social networks receive the content you ask us to publish, as independent controllers, under their own policies. If you connect an AI assistant to Alkansa, its provider processes the data that assistant accesses, under its own policies. We do not sell personal data. We send the list of providers, with each one's name and country, to anyone who asks at the contact above.
6. International transfers
Some providers process data outside the European Economic Area or Brazil. In those cases we rely on the safeguards provided by law, such as adequacy decisions (for example, the one for the United Kingdom), the EU-U.S. Data Privacy Framework or standard contractual clauses. You can ask for more details at the contact above.
7. Visibility
Projects, templates, posts and their results are restricted to your account and the people you invite. Post images can be reached by anyone with their address, because social networks need to fetch them. Do not upload confidential material. Deleting a record does not delete copies already published on the networks.
8. Cookies and local storage
In the app (my.alkansa.app), we only use cookies and local storage needed for login, language and theme; they do not require consent. On the alkansa.app website, we store your cookie choice and, only if you accept, load the measurement and advertising tools listed in section 5. You can change your choice by clearing the website's cookies, and the notice will appear again.
9. How long we keep data
Account data is kept while the account exists. An account that becomes read-only (the trial or subscription ended) is kept for 90 days: we email you 7 days before and, without a subscription, the account and its data are deleted. The images generated for each post are removed a few days after it is published (or after 30 days if it never is); only the cover is kept, for up to 13 months. The content of posts already published or discarded is removed after 90 days. A discarded post's record is deleted after 180 days; a published post's record (without the content) is kept with its numbers for up to 13 months, to compare each post with the account's normal. Active posts are preserved. Images uploaded for posts may be removed after 30 days; permanent design assets are kept while needed. Billing data and invoices are kept for the period required by tax law. Post numbers are kept in full for 31 days; after that we keep only the 3-day reading, the 30-day reading and the latest one, and everything is deleted after 13 months. Follower counts are kept once a day for 90 days, then once a week, and deleted after 13 months. The account's daily totals are deleted after 13 months. Posts read from the network, published outside Alkansa, and their numbers are deleted after 13 months. Direct messages are kept for 90 days and then deleted. The record of each auto-reply, with who tapped the button and who opened the link, is deleted 30 days after the rule ends or is turned off. When you disconnect an account, we delete its numbers (posts, followers and daily totals), conversations, auto-replies, recorded likes and the link between Page and Instagram; the disconnected-account record (identifier on the network, name and projects) is kept for up to 1 year and deleted earlier if the network requests data deletion or you ask us to. Devices and Telegram turned on for notifications are kept until you turn them off or delivery fails because they no longer exist. The waiting list is kept until you leave it. Providers' technical logs, caches and backups follow their own short periods; we do not promise instant deletion of every copy.
10. Your rights
Under the GDPR, Brazil's LGPD and other applicable laws, you can request confirmation and access, correction, erasure, anonymization or blocking, restriction, portability, information about sharing, and object to processing. Where processing relies on consent, you can withdraw it without affecting what was done before. You can correct or delete some data yourself in My account.
Send requests to contact@alkansa.app, without passwords or tokens. We may ask for proportionate confirmation of identity. We answer without undue delay and, as a rule, within 15 days, within the deadlines of the GDPR (art. 12) and the LGPD (art. 19). You can also complain to the competent European authority, such as the CNPD in Portugal, or to the ANPD in Brazil.
11. Security
We use encrypted connections (HTTPS), per-account data isolation in the database, encrypted social network tokens, an anti-bot check and approval by a person on your account before every post: you or your team approve, never Alkansa. No system is invulnerable: if you suspect an incident, tell us at the contact above. Duties to investigate, notify and remedy follow the law. If an incident affects data received from a social network, we also notify that network, as its rules require.
12. Children
Alkansa is not intended for people under 16, and we do not knowingly collect their data. If you know of such a case, write to contact@alkansa.app.
13. Changes
We update this policy when the data processed, the purposes or the providers change. Material changes are announced by email and in the dashboard before they apply and, where the law requires it, we ask for your consent again.