Privacy Policy
About this update. This version corrects the current uses of our AI providers in section 3. It removes optional OpenAI chat and speech and selectable Alibaba Qwen chat from the current list. The rest of our privacy practices are unchanged.
This Privacy Policy explains what personal data Desklight Inc. ("Desklight", "we", "us") collects when you use the Desklight platform (the "Service"), how we use it, who we share it with, and your rights. We aim to be plain about it.
Effective date. This version takes effect on November 2, 2026, or 30 days after we publish it and notify existing users by email, whichever is later. Until then, the previous version continues to apply.
1. Data we collect
1.1 Account data
When you sign up we collect your email address, name (if provided), and a hashed password. If you sign in via a third-party identity provider, we receive whatever profile fields you authorize (typically email and name).
1.2 Workspace data
Inside the Service you create brands, posts, calendar entries, knowledge base entries, and team members. We store this data so the Service works. We also store any files, documents, photos, or brand assets you upload or generate.
1.3 Generated content
When you ask Allie or any AI agent to generate text, images, video, or audio, we store the prompt, the output, and minimal metadata (model used, generation time) for delivery and revision history.
1.4 Connected services
If you connect a third-party service, we store the connection metadata and an OAuth token issued to us. Each connection uses that provider's own OAuth and API directly; no intermediary connector service holds your tokens. We use those tokens only for features you invoke, posts you approve or schedule, and optional publishing automations you explicitly enable. Tokens can be revoked at any time from Connectors in the app or from the third-party provider's settings.
The connections we offer are social publishing platforms: Facebook, Instagram, Threads, LinkedIn, X, TikTok, YouTube, and Pinterest. See section 1.5 below.
1.5 Social publishing platforms (Meta, LinkedIn, X, TikTok, YouTube, Pinterest)
When you connect a social account, we receive a limited, scoped set of data from that platform. We use it to identify and display the destination you select, show connected-account activity you request, publish posts you choose, run optional publishing automations you explicitly enable for supported platforms, and show the result of a publish. TikTok, YouTube, and Pinterest require you to use Publish now for each post; approval or a scheduled date alone does not send them. Facebook Page activity and Threads post history are retrieved only when you open that connection's details; Desklight does not persist those activity responses in its database. When you open a post in the Calendar that Desklight published, Desklight reads that post's performance metrics (such as views, reach, reactions, comments, shares, and saves) from the platform it was published to, on request, to show them to you. These metrics are not stored in Desklight's database.
| Platform | What we receive | What we do with it |
|---|---|---|
| Facebook (Meta) | OAuth access token; businesses and Pages you can access; Page IDs, names, profile metadata, and Page access token; recent Page post text, media, timestamps, and permalinks; and up to five recent comments per displayed post, including commenter ID, name, text, and timestamp; and views, viewers, reactions, comments, shares, and clicks for Page posts Desklight published | Let you select the correct Page; show recent Page activity and comments on demand; create, edit, or delete a Page post when you request it; and show the results of posts Desklight published when you open them. |
| Instagram (Meta) | OAuth access token, IG Business account ID, linked Facebook Page ID, IG media IDs after publish, and views, reach, likes, comments, shares, saves, and interactions for media Desklight published | Publish images, videos, and captions to the IG Business account. Read back the resulting media ID + permalink, and show the results of posts Desklight published when you open them. |
| Threads (Meta) | OAuth access token; your Threads user ID and username; and your recent Threads post IDs, text, media type, media or thumbnail URL, timestamp, and permalink; and views, likes, replies, reposts, quotes, and shares for posts Desklight published | Show your connected profile and recent posts on demand, publish text and media posts to your profile, return the resulting post ID and permalink, and show the results of posts Desklight published to the person who connected Threads when they open them. |
| OAuth access token and your LinkedIn member URN | Publish posts to your personal feed. | |
| X | OAuth access token, your X user ID and handle | Publish posts. |
| TikTok | OAuth access token, your TikTok user ID, display name and profile photo, and for each post the settings you chose and when you confirmed them | Publish the posts you choose, show which account a post goes to, and show a post's views, likes, comments and shares when you ask (read live, not stored). |
| YouTube | OAuth access and refresh tokens; channel ID, title, description, and thumbnail (read live, not saved); video ID and link after each upload, plus requested and recorded visibility; view, like, and comment counts for videos Desklight uploaded (read live, not saved) | Upload videos you choose through Publish now, using the title, description, tags, and upload choices you enter, then show you the resulting video link and its view, like, and comment counts. |
| OAuth access and refresh tokens, encrypted; the ID of the board you select (its name and Pin count are read live from Pinterest, not saved); the ID and link of each Pin Desklight creates; impressions, saves, clicks, reactions, and comments for those Pins (read live, not saved) | List your boards so you can choose one, create image Pins on that board when you use Publish now, and show those Pins' results when you open them. Keep the board ID you chose and the ID and link of each Pin Desklight creates. Disconnecting Pinterest deletes these, leaving only a record that each post was published and when. |
We do not read your inbox, scrape your followers, republish connected-account data as new content, publish outside a post or automation you approve or enable, or use connected-platform data for advertising or training. Our use of information received from Meta APIs adheres to the Meta Platform Terms, including the Limited Use requirements. Desklight's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google's own handling of your data is governed by the Google Privacy Policy. Data obtained from Google APIs is never used to create, train, or improve any machine-learning or artificial-intelligence model.
YouTube API Services. Desklight uses YouTube API Services to upload the videos you choose through Publish now to the YouTube channel you connect. By using that feature you agree to be bound by the YouTube Terms of Service. When you connect YouTube, we store the OAuth access and refresh tokens Google issues to us, encrypted. The connector card and publish dialog read your channel live from YouTube to show its name and picture. The channel ID, title, description, and thumbnail are read from YouTube, not saved by these features. When you open a post Desklight uploaded, Desklight reads that video's view, like, and comment counts from YouTube to show them to you; these counts are not saved. After each upload we keep the video ID and link, along with your requested visibility and the recorded visibility, so we can show the result and prevent duplicate uploads. These upload records remain when you disconnect. We use this data only to publish the videos you choose through Publish now and to show you where they went. We do not share it with third parties except the subprocessors in section 3 that host the Service, we do not let third parties serve content or advertisements through this feature, and we do not use it for advertising or model training. Google's own handling of your data is governed by the Google Privacy Policy. You can revoke Desklight's access to your YouTube and Google account data at any time via the Google security settings page. Disconnecting YouTube in Connectors deletes our stored tokens and saved publishing destinations, then requests revocation of the Google grant. If Google does not confirm revocation, Desklight tells you to remove access through the Google security settings page. We also delete stored tokens and saved publishing destinations when the YouTube grant can no longer be refreshed. Deleting data in Desklight does not delete anything on YouTube; to remove a video, delete it on YouTube. Questions or complaints about how we handle this data go to privacy@desklight.ai.
You can revoke a single platform connection at any time from Connectors → Disconnect inside Desklight, or from the platform's own app-permissions settings. Disconnecting deletes the stored OAuth token and clears provider-account and target metadata immediately. For Pinterest, disconnecting also removes Pin IDs and links from your publishing records. A minimal record that the integration is disconnected may remain for security and operational history.
When Meta or Threads sends Desklight a valid signed data-deletion callback, we immediately revoke that connection and delete its token, selected publishing destinations, platform post identifiers and links, publishing-attempt receipts, and short-lived cached publishing responses. For retry safety and operational proof, we retain a minimized receipt containing a one-way HMAC of the platform identity and the internal workspace IDs affected. Terminal receipts are deleted after 90 days; the raw app-scoped platform user ID is not stored in the receipt.
To delete all data Desklight has received from connected platforms (along with the rest of your workspace), follow the steps in our Data Deletion page.
1.6 Billing data
Payments are processed by Stripe, Inc. We never see or store your full card number. We retain Stripe customer IDs, subscription IDs, plan tier, and high-level billing status (current/past due/canceled) for billing purposes.
1.7 Usage data
We collect basic logs about how the Service is used: timestamps, IP addresses, requested URLs, error events, and feature interactions. Logs are used to operate, secure, and improve the Service.
1.8 Cookies and analytics
We use a small number of essential cookies and browser storage to keep you signed in, keep the service secure, remember your UI preferences and remember your cookie choice. With your permission, we also use Google Analytics (provided by Google LLC) to understand visits to desklight.ai and the Desklight app, such as which pages are viewed, which campaigns brought you to us, and the steps toward creating an account. Google Analytics cookies are set only after you choose "Accept analytics". You can change your choice at any time from "Cookie preferences" at the bottom of every page. We don't use Google Analytics for advertising: ad personalization and Google signals are off and advertising storage is always denied. We don't send your name or email address to Google Analytics. Analytics cookies last up to 180 days, and analytics data is kept for 14 months. We don't use third-party advertising or cross-site tracking cookies.
2. How we use data
| Purpose | Legal basis (GDPR) |
|---|---|
| Operate and provide the Service | Contract |
| Process payments and manage subscriptions | Contract |
| Send transactional email (assignments, approvals, billing, role changes, password resets) | Contract / Legitimate interest |
| Detect and prevent abuse, fraud, or security incidents | Legitimate interest |
| Improve features and fix bugs | Legitimate interest |
| Comply with law (tax, accounting, lawful requests) | Legal obligation |
| Marketing email (only if you opt in or are an existing customer) | Consent / Legitimate interest |
We do not sell or rent your personal data. We do not use your User Content to train AI models — yours or anyone else's.
3. Subprocessors
To deliver the Service we use the third-party providers below. AI and search providers receive the prompts and content needed for the feature you use; the others host, store, bill for, or deliver the Service. The current list:
| Subprocessor | Purpose | Based in |
|---|---|---|
| Anthropic, PBC | Claude models: Allie's chat and reasoning, copy drafting, brand-voice extraction | United States |
| OpenAI, L.L.C. | Image generation and text embeddings for search and memory | United States |
| Google LLC (Gemini API) | Image generation, image analysis, music generation | United States |
| Replicate, Inc. | Hosted image, video, music, speech, and background-removal models (some are run by the model's developer through Replicate) | United States |
| Eleven Labs Inc. (ElevenLabs) | Voiceover and music generation | United States |
| Hume AI | Voiceover generation | United States |
| Serper (serper.dev) | Web searches Allie runs to look up public facts for a post; only the search query is sent | Not stated by the provider |
| Brandfetch Sàrl | Public logos and brand assets for the website domain you give us | Switzerland |
| Stripe, Inc. | Payment processing | United States |
| Supabase, Inc. | Database, file storage, authentication | United States |
| Resend Inc. | Transactional email delivery | United States |
| AgentMail, Inc. | Email handling for AI agents | United States |
| Railway Corp. | Application hosting | United States |
| Netlify, Inc. | Website and web app hosting | United States |
| Functional Software, Inc. (Sentry) | Error monitoring, when enabled | United States |
| Google Analytics (Google LLC) | Measures visits and steps toward creating an account, only after you accept analytics cookies | United States |
"Based in" is where the provider is established. Providers may process data in other countries; see section 6. Each subprocessor has its own privacy and data-retention practices. Its public policies and the service terms applicable to Desklight also govern its processing.
To suggest timely topics, we also pull public news headlines from NewsAPI (newsapi.org) and public RSS feeds. We send those sources fixed search terms only, never your personal data.
4. Data retention and deletion
We retain workspace data while that workspace is active. A workspace administrator can delete one workspace through Settings → Danger zone → Delete workspace. If a login belongs to multiple workspaces, that action affects only the named workspace. To request deletion of your login profile and data across every workspace, or if you cannot sign in, follow the verified-request path in our Data Deletion instructions.
When you click Delete, your workspace is locked and enters a 28-day recovery window. During that window you can sign back in and click Restore, or email privacy@desklight.ai to waive recovery and request immediate erasure. If you do not restore, the remaining two days are an operations buffer: final database and object-storage erasure is operator-verified and processed no later than 30 days after the request; it is not represented as an unattended automatic purge.
The deletion includes any data Desklight received from connected social platforms (Facebook, Instagram, Threads, LinkedIn, X, TikTok, YouTube, Pinterest), including OAuth tokens, Page IDs, board/Pin IDs, media IDs, and connection metadata. Certain billing and transaction records may be retained after workspace erasure only where required or permitted by applicable tax, accounting, fraud-prevention, or dispute-resolution obligations.
We retain a minimal record of deletion requests and their completion to demonstrate compliance, for up to three years. This record identifies the request and its outcome; it does not retain the workspace content that was erased.
5. Sharing data
We share personal data only with:
- Subprocessors listed above, strictly to deliver the Service;
- Your authorized teammates inside your workspace;
- Authorities, when legally required, with a valid subpoena, court order, or other lawful process — and we will notify you unless prohibited.
6. International transfers
Our subprocessors may process data in countries other than the one where you live, as described in their applicable terms and privacy materials. Where data-protection law requires a transfer safeguard, Desklight uses the legally applicable mechanism documented for that service and deployment.
7. Your rights
Depending on where you live, you have the right to:
- Access the personal data we hold about you;
- Correct inaccurate data;
- Delete your data ("right to erasure");
- Export your data in a machine-readable format ("data portability");
- Object to or restrict certain processing;
- Withdraw consent at any time, where processing is based on consent;
- Lodge a complaint with your local data protection authority.
To exercise any of these rights, email privacy@desklight.ai. We will respond within the period required by applicable law.
8. Security
We take reasonable measures to protect your data, including TLS in transit, application-layer AES-256-GCM encryption for stored OAuth credentials, tenant-scoped access controls, and server-only service credentials. No system is perfectly secure; if we discover a breach affecting your personal data, we will notify you and the appropriate authorities as required by law.
9. Children
The Service is not directed to children under 16. We do not knowingly collect personal data from children. If you believe a child has provided us personal data, contact privacy@desklight.ai and we will delete it.
10. Canada (PIPEDA)
Desklight Inc. handles personal information in accordance with the Personal Information Protection and Electronic Documents Act (PIPEDA) and applicable Canadian provincial privacy laws. Our Privacy Officer, Jesse Dubberke, is accountable for our compliance with this policy and can be reached at privacy@desklight.ai or by mail at Desklight Inc., Attn: Privacy Officer, 8 Highlandview Rd, Moncton NB E1A 2K8, Canada.
You may ask for access to the personal information we hold about you, and ask us to correct it if it is inaccurate or incomplete. Send the request to privacy@desklight.ai. If you have an account, send it from the email address on that account so we can confirm it's you. We may need to verify your identity before we respond, and we will respond within the time PIPEDA requires, which is generally 30 days. If we cannot grant a request, we will tell you why.
Desklight Inc. is based in New Brunswick, Canada. Our subprocessors, including U.S.-based providers, may store and process personal information in other countries. While it is in another jurisdiction, it may be accessible to the courts, law-enforcement, and national-security authorities of that jurisdiction.
If you are not satisfied with our response, you may contact the Office of the Privacy Commissioner of Canada.
11. California residents (CCPA / CPRA)
California residents have additional rights, including the right to know what personal data we collect, the right to delete it, the right to correct it, the right to opt out of "sale" or "sharing" (we do neither), and the right to non-discrimination for exercising these rights. To exercise your rights, email privacy@desklight.ai. The categories of personal information we collect, our sources, business purposes, and disclosures are described above.
12. Changes to this policy
We may update this Privacy Policy from time to time. If a change is material, we will notify you by email or in the Service at least fourteen (14) days before it takes effect.
13. Contact
Desklight Inc.
Attn: Privacy Officer (Jesse Dubberke)
8 Highlandview Rd
Moncton NB E1A 2K8
Canada
Privacy questions or requests: privacy@desklight.ai.
General support: support@desklight.ai.