Legal
Privacy Policy
Last updated 19 November 2026Terms of UseData deletion
1. What this policy covers
This policy explains how Digital Sixty (“we”, “us”) handles personal data in the Digital Sixty workspace at app.digitalsixty.com (the “workspace”). The workspace is where a brand and our account team manage the brand’s Facebook and Instagram presence: businesses, ad accounts, campaigns, Pages, customer comments and messages, and leads.
“We” means the operator of the workspace under the Digital Sixty brand, based in the United Kingdom. Our public website has its own policy at digitalsixty.com/privacy. Where a client has a written agreement with us, that agreement and any data-processing terms in it also apply.
2. Whose data we handle
- Workspace users: our staff and the people a client has asked us to invite. There is no public sign-up.
- People who interact with a connected Page or Instagram account: customers who comment, send a message or review the Page, and people who submit a lead form.
- Owners of public Pages that a user looks up, such as a competitor or a distributor. Only information that is already public on Facebook is shown.
3. Data about workspace users
- Name, work email address and role (administrator or member).
- A password, stored only as a salted scrypt hash. We cannot read it.
- Sign-in sessions, stored as a hash, which expire after 7 days.
- Which business, ad account and Page the user last worked on, so the workspace opens where they left off.
Failed sign-in attempts are counted for 15 minutes by email address and IP address to stop password guessing. That count is held in memory and is not written to our database.
4. Data we receive from Meta
A user connects their own Facebook account through Facebook Login for Business. Meta shows each permission, and the user chooses which businesses, Pages, Instagram accounts, ad accounts and catalogs to share. We receive only what those choices allow, and only the data a screen in the workspace uses:
- The connecting user: their app-scoped Facebook ID, name, and the permissions they granted or declined.
- Businesses: the businesses the user manages, the businesses created for a brand’s ad accounts, their system users, credit line details and the Pages and pixels shared with them.
- Advertising: ad accounts, campaigns, ad sets, ads, creatives, audiences, pixels, spending limits and performance figures (spend, impressions, clicks and breakdowns by country, age, gender and platform). These are aggregate figures, not data about identifiable people.
- Catalogs: product catalogs, products, feeds and product sets.
- Pages and Instagram: Page and Instagram account details, posts, media, insights, ratings and reviews.
- Comments and messages: comments, mentions and messages sent to the connected Pages and Instagram accounts, with the name and profile picture of the person who sent them.
- Leads: the answers a person gives in a Page’s Instant Form, typically name, email address, phone number and company.
- Public Pages: the public details and public posts of a Page a user looks up. These are shown on screen and are not stored.
5. How we use it
- To show the connected assets and act on them when a user asks: creating and editing campaigns, posts and catalogs, publishing to Instagram, replying to and moderating comments and messages, creating lead forms and retrieving leads.
- To open and run businesses and ad accounts on a client’s behalf.
- To report on ad, Page and Instagram performance, including an hourly refresh of ad results.
- To hide comments automatically when they match a keyword a user has set.
- To keep the workspace secure and working: we record which Meta endpoint was called, for which permission, and whether it succeeded. That record never contains the content of a comment, message or lead.
What we do not do
- We do not sell data received from Meta, and we do not share it with data brokers or advertising networks.
- We do not use it to build profiles of people, to target them elsewhere, or to make decisions about them.
- We do not use it to train AI models.
- We do not combine one client’s data with another’s, and we do not use it for any purpose other than providing the workspace to the business that connected it.
- The workspace never spends or publishes on its own: ads are created paused, and posts and replies go out only when a person sends them.
6. Our role and the brand’s role
For data about a brand’s customers and leads, the brand decides why and how that data is used, and we handle it on the brand’s behalf to provide the workspace and the services in its agreement. If you are a customer of a brand and want to use your rights over a comment, message or lead, contact that brand; you can also contact us and we will pass your request on and help the brand respond.
For data about workspace users, and for the security records in section 5, we decide how the data is used.
Depending on the law that applies, we rely on the agreement with the client, on the permissions the connecting user gave in Meta’s login, and on our legitimate interest in running and securing the workspace. We handle personal data in line with the UK General Data Protection Regulation and the Data Protection Act 2018 and, where they apply, the EU GDPR and other applicable laws.
7. Who we share it with
- Meta. Actions a user takes are sent to Meta through its APIs, and Meta sends us updates for connected Pages and Instagram accounts. Meta handles that data under its own terms and policies.
- Our hosting providers, who process data only to run the workspace for us: Vercel (application hosting) and Neon (database).
- The client’s own team and our account team, limited to the workspace accounts that have been invited.
- Authorities, only where the law requires it, or to investigate misuse of the workspace.
We do not share data received from Meta with anyone else.
8. Where data is processed
Our hosting and database providers may process data outside the United Kingdom, and outside the country of the people it is about. Where the law requires safeguards or consent for a cross-border transfer, we put them in place. Contact us for details.
9. Security
- Access tokens stay on our servers, are never sent to the browser, and are encrypted at rest with AES-256-GCM.
- The workspace never asks for or stores a Facebook password. Access to each business uses Meta’s system users.
- All traffic uses HTTPS. Requests from Meta are checked against Meta’s signature before they are accepted.
- Accounts are issued by invitation, each user sees only what their own Facebook connection can reach, and administrator tools are closed to other users.
No online system is completely secure. If we learn of a breach that affects your data, we will tell you and the relevant authorities as the law requires.
10. How long we keep it
| Data | Kept for |
|---|---|
| Comments, messages, posts, Page and Instagram insights shown on screen | Not stored. Read from Meta when the screen is opened. |
| Notifications from Meta about new comments, messages and leads | 90 days, or until the connection is removed. |
| Leads retrieved from lead forms | Until the connection is removed or the lead is deleted on request. |
| Ad performance refreshed each hour | The latest 7 days only, replaced at each refresh, until the connection is removed. |
| Access tokens, connected assets, system users, keyword rules | Until the connection is removed. |
| Images uploaded for a post, an Instagram publish or a message | 30 days. They sit at an unlisted web address so Meta can fetch them. |
| Record of calls made to Meta (no content) | 90 days. |
| Workspace account | Until an administrator removes it or you ask us to. |
| Confirmation of a completed deletion request | Kept, with the app-scoped Facebook ID only, as proof the request was carried out. |
11. Deleting your data
- In the workspace: Settings → Disconnect Meta and delete data. This revokes the app on Facebook and deletes, straight away, your tokens, connected assets, system user tokens, keyword rules, uploaded images, retrieved leads, stored notifications and synced ad results.
- From Facebook: remove Digital Sixty under Business integrations (or Apps and websites) and ask for your data to be deleted. Facebook notifies us and the same data is deleted automatically.
- By asking us: through digitalsixty.com/contact. We delete your data, including your workspace account, within 30 days.
The steps are set out on the Data deletion page.
12. Cookies
The workspace sets two cookies, both essential:
- d60_session keeps you signed in for up to 7 days. It cannot be read by scripts.
- rsp_meta_state exists for a few minutes while you connect Facebook, to make sure the answer from Meta belongs to your request.
The workspace uses no analytics, advertising or tracking cookies, loads no third-party scripts, and serves its own fonts.
13. Your rights
Depending on the law that applies, you may ask for a copy of your data, ask us to correct or delete it, withdraw a consent you gave, or object to or restrict certain uses. We may need to confirm your identity first. Send requests through digitalsixty.com/contact and mark your message as a privacy request. You may also complain to the Information Commissioner’s Office in the United Kingdom or to the data protection authority where you live.
14. Children
The workspace is a business tool. It is not offered to children, and workspace accounts are issued only to adults acting for a business.
15. Changes to this policy
We update this page when the workspace or our practices change. The date at the top shows the latest version. If a change affects how we use data received from Meta, we tell workspace users before it takes effect.
16. Contact
Privacy questions and requests: digitalsixty.com/contact. Please do not send passwords or payment details.