1. Who is responsible for your data#
The controller of the personal data described in this policy is SlidesLand, a sole trader established in Algeria.
- Controller
- SlidesLand
- Proprietor
- Abderrahmane Gaci
- Postal address
- Algeria
- Data protection contact
- support@slides.land
- Security reports
- support@slides.land
- Supervisory authority
- Autorité Nationale de Protection des Données à Caractère Personnel (ANPDP), Algeria
We are a small operation. There is no separately appointed Data Protection Officer, because the law does not require one at this scale: the proprietor named above is personally accountable for everything in this policy, and answers the address above.
This policy applies to https://slides.land and to the SlidesLand application and API. It is governed by Algerian Law No. 18-07 of 10 June 2018 on the protection of natural persons in the processing of personal data and (because the service is open to people in the EU) by the GDPR where it applies.
2. The short version#
- We do not sell your personal data. Not to anyone, in any form, for any price.
- We do not use your content or your platform data for advertising, ours or anyone else’s, and we run no advertising on the Service.
- We do not use your content to train AI models, and we instruct our AI providers not to train on it either.
- We do not track you across other websites. There are no advertising cookies and no pixels. Google Analytics, which counts which pages are used, runs only if you accept it on the cookie banner, with advertising features switched off.
- Data we read from the platforms you connect (TikTok, Instagram, Facebook, Threads, Bluesky) is used only to show you your own numbers inside SlidesLand, and is deleted when you disconnect the account. LinkedIn is used for posting only.
- You can export everything and delete everything, yourself, from inside the app.
3. What we collect, why, and on what basis#
Each row below is a real category of data the application stores, with the reason it exists and the lawful basis under Article 6 GDPR.
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| Email address | It is your login, it is how a password is reset, and it is how we reach you about security and billing. | Performance of a contract | While the account exists |
| Password | To authenticate you. Stored only as a scrypt hash with a per-user random salt: the password itself is never stored and cannot be recovered from what we hold, by us or by anybody who obtained the database. | Performance of a contract | While the account exists |
| Name (optional) | So the interface can greet you by name. You may leave it blank. | Performance of a contract | While the account exists |
| Profile picture (optional) | Shown in the interface. Only if you upload one. | Consent, withdrawable by removing it | Until you remove it |
| Two-factor secret and recovery codes | To verify a second factor at sign-in, if you switch it on. The secret is stored encrypted and recovery codes are stored hashed. | Performance of a contract; our legitimate interest in account security | Until you turn 2FA off |
| Account creation time, last sign-in time | To show you and us whether an account is in use, and to spot a dormant account being taken over. | Legitimate interests: security and service operation | While the account exists |
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| Images you upload | They are the point of the product. Stored in object storage or, on small deployments, in the database. | Performance of a contract | Until you delete them, or the account is deleted |
| Slides, slideshows, captions, formats, collections | Your work. | Performance of a contract | Until you delete them, or the account is deleted |
| Scheduled posts and their targets | So a post goes out when you asked it to. | Performance of a contract | Until you delete them, or the account is deleted |
| Prompts you send to AI features, and the text returned | To generate the draft you asked for and to show it to you again later. | Performance of a contract | Until you delete the slideshow it belongs to |
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| OAuth access and refresh tokens | To make the API calls you authorised. Encrypted at rest with a key derived from a server secret, so a stolen database does not hand over your social accounts. | Consent, given through the platform’s own authorisation screen | Until you disconnect, or the token expires |
| Platform account identifier, handle, display name, avatar URL | So the app can show which account is connected without spending an API call on every page load. | Consent | Until you disconnect |
| Counters for accounts you connected: followers, following, likes, posts, and (where the platform provides them to the owner) reach, impressions and profile views | To draw your analytics. Recorded as a time series because none of the platforms return history, so growth only exists if it is recorded. | Consent | Until you disconnect that platform, or delete the account |
| Per-post metrics and metadata for your own posts: views, likes, comments, shares, saves, caption, cover image URL, permalink, posted time, duration | To show which of your posts did well. | Consent | Until you disconnect that platform, or delete the account |
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| Activity log: the time, the route, the HTTP status, how long the request took, your IP address, your browser’s user-agent string, and a one-line summary | To answer "it broke on Tuesday, what happened", and to see a sign-in being guessed at. No request bodies, no captions, no images and no tokens are written to this log. | Legitimate interests: security, debugging, and service integrity | 90 days |
| Failed sign-in counters | To rate-limit guessing. The identifier is stored as a hash, not as the address, so the table does not become a list of other people’s email addresses. | Legitimate interests: security | The length of the lockout window |
| Email delivery records: recipient, subject, kind of message, time, and the delivery outcome reported by our email provider | To tell whether a password reset actually arrived before you spend an hour on a support ticket about it. | Legitimate interests: service operation | 180 days |
| Support tickets and their messages | To answer you, and to see whether the same thing is breaking for several people. | Performance of a contract; legitimate interests | 2 years after the ticket is closed |
| Captcha token, at sign-up and sign-in | Passed to Cloudflare Turnstile to check you are not a script, then discarded. See section 8. | Legitimate interests: preventing automated abuse | Not stored |
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| Polar customer and subscription identifiers (or Lemon Squeezy’s, for a subscription bought there), subscription status, plan, renewal date | To know what your account is entitled to. | Performance of a contract | While the account exists |
| Payment records: amount, currency, date, status, and the last four digits of a card where Polar or Lemon Squeezy supplies them | To show you what you were charged and to handle refunds. | Legal obligation: tax and accounting records | As long as the tax and accounting law that applies to us requires |
| Full card number, CVV, bank details | We never receive these. They go from your browser to Polar (or, for a subscription started before we moved to Polar, Lemon Squeezy), who are the merchant of record, and never touch our servers. | Not applicable | Never held |
| Data | Why we have it | Legal basis | Kept for |
|---|---|---|---|
| What you write about your business: name, description, audience, pricing, call to action, proof, context | So generated slideshows can describe and promote your business accurately. | Performance of a contract | Until you delete the business or your account |
| Documents you upload to a business | Only the text read from them is kept, for the analysis and for generation. The original file is not stored. | Performance of a contract | Until you remove the file, the business or your account |
| Pictures you upload to a business | Stored in your library like any other upload, so they can be placed on slides. | Performance of a contract | Until you delete them or your account |
| Text read from your public website | When you press Read website, the public pages of the address you gave (home, pricing, features, about) are read as text, for the analysis. | Performance of a contract | Until you read it again, change the address, or delete the business |
| The analysis | The brief your AI provider wrote from the above, kept so generation can reuse it without paying for it again. | Performance of a contract | Until you run it again or delete the business |
4. Where we rely on legitimate interests#
Legitimate interests is a basis that requires us to balance our interest against your rights, and to be able to show that we did. We rely on it in four places, and the balance in each is:
- Security logging
- Our interest is in detecting account takeover and abuse. The data is minimal and short-lived, no content is recorded, and a user would reasonably expect a service to keep a security log. Your interest is not overridden.
- Rate limiting
- Our interest is in preventing brute-force sign-in and automated sign-ups. Identifiers are hashed and kept only for the lockout window, so the record is worthless if leaked.
- Email delivery records
- Our interest is in knowing whether a reset email arrived. We store the recipient, the subject and the outcome, not the body of the message.
- Service and error metrics
- Our interest is in knowing that the application is working. The records are per-request and aggregated for reading; they are not used to build a profile of you.
You have the right to object to any processing based on legitimate interests. Write to support@slides.land and we will stop unless we can show compelling grounds that override your objection, which for the items above would be unusual.
5. Data from the platforms you connect#
This section exists because it is the part most people (and every platform reviewer) want spelled out. The full technical detail is in the Platform Data Policy; what follows is the privacy position.
What we ask for
When you connect an account, the platform shows you its own consent screen listing the permissions we request. We request only these:
| Platform | Permission | What it lets us do |
|---|---|---|
| TikTok | user.info.basic | Read the connected profile’s open id, display name and avatar. |
| TikTok | user.info.profile | Read the connected profile’s username and verified status. |
| TikTok | user.info.stats | Read the connected profile’s follower, following, likes and video counts. |
| TikTok | video.list | Read the list of the connected account’s own videos and their public counters. |
| TikTok | video.publish | Post a slideshow you made to your own TikTok profile as a photo post, when you post it or at the time you scheduled. |
| TikTok | video.upload | Send a slideshow to your TikTok inbox as a draft, which you finish and post in the TikTok app. |
| Meta | pages_show_list | List the Facebook Pages you administer, so you can choose which one to connect. |
| Meta | pages_read_engagement | Read engagement figures for the Page you connected. |
| Meta | pages_read_user_content | Read the connected Page’s own posts with their comment and like counts. |
| Meta | pages_manage_posts | Post a slideshow you made to the connected Page, only when you press Post. |
instagram_business_basic | Read the connected Instagram professional account’s profile and its own posts. | |
instagram_business_manage_insights | Read owner-only metrics for that account and its posts. | |
instagram_business_content_publish | Post a slideshow you made to that account, only when you press Post. | |
| Meta | read_insights | Read insight metrics for the Page you connected. |
| Meta | instagram_basic | Read the connected Instagram professional account’s profile and media. |
| Meta | instagram_manage_insights | Read insight metrics for that Instagram account and its media. |
| Meta | instagram_content_publish | Publish a slideshow you made to that Instagram account, only when you publish or schedule it. |
| Threads | threads_basic | Read the connected Threads profile and the list of its own posts. |
| Threads | threads_content_publish | Post a slideshow you made to the connected Threads profile, only when you press Post. |
| Threads | threads_manage_insights | Read the views, likes, replies, reposts and follower count of the connected Threads profile. |
openid, profile | Identify the connected member: id, name and picture. | |
w_member_social | Post a slideshow you made to your own LinkedIn feed, when you post it or at the time you scheduled. | |
| Bluesky | App password (not stored) | Post a slideshow you made, and read your public profile and your own posts’ counts. |
What we do with it
- It is shown back to you, in your own SlidesLand account, and to nobody else.
- Counters are stored as a dated series so the app can draw growth over time. The platforms return only today’s number, so this is the only way a chart can exist.
- It is never sold, licensed, brokered or shared with any third party for their own purposes.
- It is never used for advertising or ad targeting, ours or anyone else’s.
- It is never used to train machine-learning models.
- It is not combined with data from other users to build audience segments or any other derived product.
- It is not transferred to anyone except the infrastructure providers in the Subprocessors list, who process it only to host it on our behalf.
How long we keep it, and how it is deleted
You can revoke our access at any time, either from the Accounts page in SlidesLand or from within the platform directly (for Bluesky, by deleting the app password).
- The stored OAuth access and refresh tokens are deleted immediately.
- The platform account identifier, handle, display name and avatar URL are deleted immediately.
- The counters, per-post metrics, captions, cover URLs and permalinks we obtained from that platform are deleted immediately. The app warns you before you disconnect that this removes the analytics history for that platform, because it cannot be fetched again: the platforms do not return history.
- Backups holding that data age out within 35 days.
Deleting your SlidesLand account deletes all of it regardless of connection state, on the same timetable.
Where the platform’s own rules also apply
Your use of a Connected Account is also governed by that platform’s terms and privacy policy, which we cannot vary:
6. AI features and your data#
When you use a feature that drafts text, the instruction you gave and the relevant part of your slideshow are sent to a third-party AI provider over an encrypted connection, and the generated text is returned and stored with your slideshow.
- This happens only when you ask for it. Nothing is sent to a model in the background.
- We use providers on terms that prohibit training on data sent through the API, which is the default for the business tiers of the providers we use.
- We do not send your images to a language model, your email address, your payment details, or data from a Connected Account.
- When you run the analysis on the Business page, what you wrote about the business, the text of the documents you uploaded to it and the text read from its website are sent to your AI provider, once per run.
- The providers we use, and where they process, are in the Subprocessors list.
- If you supply your own provider key in Settings, the request goes to your own account with that provider and their terms apply to it directly.
No automated decision-making with legal or similarly significant effects is carried out under Article 22 GDPR. AI features produce drafts for you to accept or reject; nothing decides anything about you.
9. International transfers#
Some of our providers process data outside Algeria, principally in the United States and the EU. Where that happens, the transfer is covered by an appropriate contractual safeguard:
- the EU Standard Contractual Clauses in the provider’s data processing agreement; and, where the provider is certified,
- the EU–US Data Privacy Framework.
The Subprocessors list states the processing location and the safeguard for each provider. We carry out a transfer risk assessment before adding a provider that processes outside Algeria.
You may ask us for a copy of the safeguards relied on by writing to support@slides.land.
10. How long we keep things#
The tables in section 3 give the period for each category. The general rules behind them are:
- Content and account data live as long as the account does. Deleting an item deletes it.
- Security and activity logs are kept for 90 days, then deleted.
- Email delivery records are kept for 180 days.
- Support tickets are kept for 2 years after closure.
- Payment records are kept for as long as the tax and accounting law that applies to us requires. This is the one category we cannot delete on request, and a deletion request will leave it in place with everything else removed.
- Backups are kept on a rolling cycle and age out within 35 days. Data deleted from the live system disappears from backups within that window.
11. How your data is protected#
The measures below are implemented, not aspirational.
- Transport: every connection to the application and the API is over TLS. Plain HTTP is redirected.
- Passwords: stored as scrypt hashes with a per-user random salt and a deliberately expensive cost factor. Verification is constant-time. The password itself is never written anywhere.
- Platform tokens: encrypted at rest with a key derived from a server secret held outside the database, so a database dump alone does not yield a usable token.
- Two-factor authentication: available on every account, using time-based one-time codes, with single-use recovery codes stored hashed.
- Rate limiting: sign-in and sign-up attempts are counted per address and per account, and refused past a threshold. The counters store hashes, not addresses.
- Bot protection: Cloudflare Turnstile in front of sign-up and sign-in.
- Least privilege: the application uses a scoped database role; object storage buckets are private and served through signed URLs.
- Headers: responses set
X-Content-Type-Options,X-Frame-Options, a frame-ancestors content security policy, and a no-referrer referrer policy, so that capability URLs are not leaked to sites you click through to. - Tenancy: every query is scoped to the signed-in account, and that isolation is covered by automated tests that run on every change.
- Access: administrative pages are restricted to named operator addresses and every administrative action is logged with the operator who took it.
No system is perfectly secure, and we will not claim otherwise. If we suffer a personal data breach likely to result in a risk to your rights and freedoms, we will report it to the competent data protection authority where the law requires it (for users in the EU, within 72 hours of becoming aware of it, as the GDPR requires), and will tell you directly and without undue delay where the risk is high.
12. Your rights#
Under Algerian Law No. 18-07 and, where it applies to you, the GDPR, you have the following rights. All of them are free to exercise, and we will answer within one month.
- Access
- A copy of the personal data we hold about you. The Settings page exports it immediately, in a machine-readable form, without asking anybody.
- Rectification
- Correction of anything inaccurate. Most of it you can edit yourself in Settings.
- Erasure
- Deletion of your data. Delete your account in Settings and it happens; everything except the tax records in section 10 goes.
- Restriction
- To have processing paused while a dispute about accuracy or legitimate interests is resolved.
- Portability
- Your data in a structured, commonly used, machine-readable format, which is what the export produces.
- Objection
- To object to processing based on legitimate interests, on grounds relating to your situation. See section 4.
- Withdraw consent
- Where we rely on consent (a connected platform account, a profile picture), withdrawing it is a single action in the app, and does not affect processing carried out before you withdrew.
- Not be subject to automated decisions
- We make none with legal or similarly significant effects.
To exercise a right that the app does not do for you, write to support@slides.land. We may ask you to confirm your identity, which for an account holder normally means writing from the address on the account. We will not charge you unless a request is manifestly unfounded or excessive, and we would explain why before doing so.
If you are unhappy with how we handled it
Please tell us first: most complaints are a misunderstanding we can fix. You also have the right to complain to a supervisory authority at any time:
- in Algeria, the Autorité Nationale de Protection des Données à Caractère Personnel (ANPDP);
- if you are in the EU or the UK, the data protection authority of the country where you live, work, or where the issue arose.
13. Children#
SlidesLand is not for children. You must be 18 or over to hold an account, which is above the age at which a child can consent to information society services in any part of the UK or the EU.
We do not knowingly collect personal data from children. If you believe a child has created an account, tell us at support@slides.land and we will close it and delete the data.
14. If you are in California#
We do not target the United States, but the CCPA as amended by the CPRA may apply to some users. For the avoidance of doubt:
- We have not sold or shared personal information as those terms are defined by the CCPA, in the preceding 12 months or ever, and we do not intend to. There is therefore no "Do Not Sell or Share My Personal Information" link to provide, because there is nothing to opt out of.
- We do not use or disclose sensitive personal information for purposes other than those permitted without a right to limit.
- The categories we collect, the purposes, and the recipients are in sections 3 and 7 of this policy.
- You have the right to know, to delete, to correct, and not to be discriminated against for exercising a right. The export and delete tools in Settings satisfy the first three; the fourth we simply do not do.
Requests under the CCPA go to support@slides.land and are answered on the same timetable as everything else.
15. Changes to this policy#
We will update this policy when what we do changes. The "last updated" date at the top tells you when the text last changed substantively.
For a change that materially affects how your personal data is used, we will email the address on your account at least 30 days before it takes effect, so you have time to object, to withdraw a consent, or to delete the account.
We keep the previous versions and will send you one on request.
16. Contact#
- Controller
- SlidesLand
- Proprietor
- Abderrahmane Gaci
- Address
- Algeria
- Data protection
- support@slides.land
- Security
- support@slides.land
- Abuse and copyright
- support@slides.land
- General
- support@slides.land
We aim to acknowledge every message within 2 working days.