Elynd
Privacy Policy
Effective date: June 15, 2026
Last updated: September 20, 2026
This Policy applies to the beta version of Elynd. We may update it as the Service evolves, but the core principles stay the same: we use data to run the product, we do not sell it, and we never publish anything without your command.
General provisions
This Policy describes what data the Elynd service (the "Service", "we") collects, how we use it, who we share it with and what rights you have.
The data operator is the Elynd Service Administration, operating in the Republic of Kazakhstan.
Elynd is an AI tool for planning, preparing and publishing LinkedIn posts. To work, the Service processes your professional content: your strategy, topics, materials, writing samples, drafts and LinkedIn connection data.
1. What data we collect
Account data
- name;
- email address;
- password, stored only as a cryptographic hash;
- if you sign in with Google: your Google account ID, verified email, name and profile information available through Google Sign-In.
LinkedIn data
- the OAuth authorization token used to connect LinkedIn and publish at your command;
- profile information available through LinkedIn after you grant permission;
- past posts that you add yourself as writing samples.
Content you create in the Service
- strategy settings: niche, audience, content directions, tone and language;
- content plans, topics, drafts and posts published through the Service;
- materials: ideas, sources and your source notes;
- images you upload to posts.
Technical data and analytics
We collect anonymized usage events: which actions are performed in the interface, whether operations succeed or fail, generation time and similar technical metrics. These events do not contain your name, email, content text, links or writing samples. The event identifier is a technical UUID and is not intended to identify you directly.
Google Sign-In
If you sign in with Google, Elynd requests only the basic Google OAuth scopes: openid, email and profile. This data is used only to sign you up, sign you in, verify your email and link your Google account to your Elynd account.
Elynd does not access Gmail, Google Drive, Google Calendar, Google Contacts or data from any other Google services. Once sign-in is complete, we do not store Google access tokens or refresh tokens; your account keeps only your Google account ID, email and the name or profile data needed for your account to work.
Google user data is not sold, not used for advertising and not used to train AI models.
2. How we use data
We use your data only to operate, support and improve the Service:
- authenticating you and supporting your account;
- signing you up, signing you in and linking your Google account to your Elynd account when you use Google Sign-In;
- generating plans, topics and post texts based on your strategy, materials and writing samples;
- saving drafts, plans, materials and settings between sessions;
- publishing posts to LinkedIn only after your explicit command;
- anonymized analytics to understand which parts of the product work and which need improvement;
- contacting you about the beta, support and feedback.
We do not sell your data or use it for advertising.
3. Who we share data with
The Service runs on infrastructure from third-party providers. Each provider receives only the data it needs to perform its function.
| Provider | Purpose | Data received |
|---|---|---|
| OpenAI | AI generation of plans and posts | The texts and instructions sent for generation: strategy, writing samples, topics, materials and draft parameters. |
| Vercel | Hosting the web interface | Technical data about requests to the web interface. |
| Railway | Hosting the backend and database | Account and content data needed for the Service to work. |
| Cloudflare R2 | Storage for uploaded images | Images you attach to posts. The storage is private; images are accessed through the Service. |
| Resend | Sending service emails: email verification and password reset | The recipient's email address and a link with a one-time token in the body of the email. |
| PostHog | Product analytics | Anonymized usage events without your name, email, content text, links or writing samples. |
| Sentry | Technical error monitoring | Technical information about errors: error type and location, browser, device and browser language. Content text, request bodies, email addresses, tokens and cookies are removed or masked before sending. |
| Authentication via Google Sign-In | Google account ID, email address, name and profile information available within the openid, email and profile scopes. | |
| Account connection and publishing | Authorization data and the content you publish under your name at your own command. |
4. AI generation and OpenAI
To generate plans, topics and texts, the Service sends to the OpenAI API only the content needed for that specific generation: strategy settings, writing samples, topics, materials, instructions and the current draft text.
Under OpenAI's rules for its API and business products, API data is not used to train OpenAI models by default unless the organization has explicitly opted in to share data for model improvement. This data sharing is not enabled for Elynd's production project.
You can read more in OpenAI's official materials: how your data is used and enterprise privacy.
5. Where data is stored and processed
The infrastructure of our providers, including OpenAI, Vercel, Railway and Cloudflare, may be located outside the Republic of Kazakhstan, including in the United States and other countries. By using the Service, you consent to this cross-border processing of your data. We choose providers that offer industry-standard data protection measures.
6. Retention and deletion
Account and content data is kept while your account is active and as long as it is needed for the Service to work.
In the beta, deleting an account uses soft delete: the account is disabled immediately and the data is marked for deletion. Data is fully purged within 30 days after the account is deleted or after a separate request for a full purge.
Anonymized analytics events may be kept in aggregated form and are not linked to your identity, name, email or content text.
7. Your rights
You can:
- request access to the data we hold about you;
- correct inaccurate data;
- delete your account and related data;
- revoke the LinkedIn connection in the Service settings or on LinkedIn;
- withdraw your consent to data processing where that processing is based on consent.
To exercise any of these rights, write to us at hello@elynd.ai. We will respond within a reasonable time.
8. Security
We use technical safeguards: passwords are stored as hashes, API access is protected with OAuth/JWT tokens, image storage is private and accessible through the Service, and analytics is designed not to contain personal data or content text.
No system is 100% secure, but we strive to handle your data responsibly and to limit access to it to those who need it to operate the Service.
9. Age requirement
The Service is not intended for anyone under 18. We do not knowingly collect data from users under this age.
10. Changes to this Policy
We may update this Policy as the Service evolves. We will notify registered users of material changes. The date of the last update is shown at the top of this document.
11. Contact
For any questions about your data or this Policy, write to hello@elynd.ai.