Duskly is a social scheduler. This page describes what we store when you use Duskly Cloud at duskly.site. If you self-host, this policy still describes the product; your own deployment holds the data.
What we store
- Account email — used to sign you in (one-time codes) and send team invites.
- Connected tokens — OAuth access and refresh tokens, API keys, app passwords, bot tokens, or webhook URLs you connect. They are encrypted at rest with a workspace-scoped key and used only to publish the posts you schedule.
- Posts — draft and scheduled copy, first comments, schedule times, and publish status.
- Media — images and clips you upload or generate, stored so we can attach them when a slot fires.
- Workspace metadata — plan, teammates, companies (client groups), and channel handles.
How we use it
We use this data to run the scheduler: authenticate you, keep channels connected, send posts when due, and bill Cloud plans. We do not sell your posts, media, or connected-network tokens. We do not use connected-network content to train models.
Google, Meta, LinkedIn, Slack, Reddit, and X
When you connect a network, that provider shares an access token (and sometimes a refresh token or profile name) so Duskly can publish on your behalf. You can revoke that access in the provider’s security settings and by removing the channel in Duskly. For LinkedIn, Duskly first requests openid, profile, and email, then continues into a second LinkedIn consent for w_member_social so it can identify the member and publish posts. LinkedIn Page uses a separate app and also requests w_organization_social, r_organization_social, and rw_organization_admin. We use LinkedIn tokens only to identify the connected member or organization and publish posts you schedule. LinkedIn’s privacy policy is at linkedin.com/legal/privacy-policy. The Slack bot posts to the public channel you picked before the bot is invited, which is why chat:write.public is requested. Google users can also revoke access at Google security settings. Google’s privacy policy is at policies.google.com/privacy.
Reviewer URLs
- Instagram public media:
GET https://api.duskly.site/v1/media/:id/public?exp&sig - Meta data-deletion callback:
https://api.duskly.site/v1/meta/data-deletion - Human data-deletion page:
https://duskly.site/data-deletion
How to delete your data
Sign in, open Accounts, and remove a channel to drop its tokens. Delete posts from the calendar. To delete an entire Cloud account, email hello@duskly.site from the same address you use to sign in. Meta also calls our data-deletion callback; see Data deletion.
Contact
Email hello@duskly.site. We do not list a street address.