QalamNew: agency workspaces with separate client voice memorySee setup
← Back to Qalam

Privacy Policy

Last updated: June 2026

1. What We Collect

We collect your email address, name, and LinkedIn profile information (when you connect LinkedIn). We store drafts and posts you create inside Qalam.

2. How We Use Your Data

Your data is used to power your Qalam workspace: AI writing, voice training, post history, and scheduling. We do not sell your data to third parties.

3. Your Content Privacy

Your drafts are private. No one at Qalam reads your content. Your posts and ideas stay within your workspace unless you publish them.

4. LinkedIn Data

LinkedIn data (profile info, publishing permissions) is used only to enable posting on your behalf. We request the minimum required permissions. You can revoke access from your LinkedIn settings at any time.

5. Cookies

We use session cookies to keep you signed in. No advertising or tracking cookies are used.

6. Data Security

We use industry-standard encryption for data in transit and at rest. Access to your data is restricted to essential systems only.

7. Data Deletion

You may request deletion of your account and all associated data by emailing info@byqalam.com. We will process deletion requests within 7 business days.

8. Third-Party Data Processors

We use the following sub-processors to operate Qalam. Each receives only the data necessary for their function:

  • Supabase - database and authentication. Your account data, posts, and workspace settings are stored on Supabase-hosted infrastructure (AWS, EU or US region).
  • Groq / Google Gemini - AI content generation. When you generate a post, your topic, role, and writing preferences are sent to one of these providers to produce draft text. Prompts are not used to train their public models per their enterprise terms.
  • Resend - transactional email. Your email address is shared with Resend to deliver verification, notification, and password-reset emails.
  • Upstash Redis - rate limiting and caching. Your user ID is used as a rate-limit key; no personal content is stored in Redis.

9. Contact

For privacy questions, contact us at info@byqalam.com.