Krevaya is a product of Gopherlume LLC (“Krevaya”, “we”, “us”), which is the data controller for the personal information described in this policy. Krevaya is an AI-assisted social publishing platform for creators and businesses. This policy explains what personal information we collect, how we use it, who we share it with, how we protect it, and the rights and choices you have. It applies to krevaya.com and all Krevaya services.
1. Personal information we collect
Information you provide.
- Account information — your email address, a secure hash of your password (we never store or see the plaintext), your display name, timezone, and subscription plan.
- Content — post drafts, edits, approvals and rejections, brand settings, personas and voice samples you provide, and media you upload for your creations.
- Sales inquiries — your Google-verified email, name, company, role, company size, country or region, and the needs you describe. We save these with your account and send a notification to our team so we can respond about Enterprise pricing.
- Payment information — processed entirely by our payment processor, Stripe. We never receive or store your card number; we retain only your subscription status, plan, and a Stripe customer reference.
Information from connected social accounts. When you connect a social account (Facebook Page, Instagram Business account, Threads, or LinkedIn), we receive and store the account identifiers, page or profile names, and the access tokens required to publish on your behalf. Access tokens are encrypted at rest with keys held in a dedicated key vault. We also retrieve performance insights (reach, impressions, engagement) for posts published through Krevaya so we can show you analytics. YouTube, Pinterest and Tumblr work differently and are described on their own in section 5, section 6 and section 7.
LinkedIn Pages. When your LinkedIn connection includes the Pages you administer, we read the list of those Pages (each Page's name) and post only content you approved, to the Page you choose. We do not read the Page's followers, messages or analytics. Disconnecting a Page deletes the stored token.
Information collected automatically. Standard request and error logs (IP address, user agent, timestamps) used for security, debugging, and abuse prevention, retained for up to 30 days. We also use Google Analytics (Google LLC) and our own self-hosted analytics to understand which pages and features people actually use; these record page views and interaction events, never the content of your drafts. We do not use third-party advertising cookies, ad-retargeting pixels, or cross-site ad tracking, and we never sell your personal information.
Non-personal data. We maintain a shared cache of publicly available trending topics (from sources such as Hacker News, Reddit, GitHub, and dev.to). It is common to all users and contains no personal information about you.
2. How we use your information
- To provide, operate, and secure the service.
- To authenticate you and maintain your session.
- To generate drafts, ideas, and analytics for you — including processing your prompts, niche, and writing samples with AI models as described in section 3.
- To publish content to your connected social accounts, only at your direction (per-post approval, or the auto-publish schedule you enable). Auto-publish never applies to Pinterest or Tumblr: you approve each of those posts yourself.
- To process subscription payments and manage your plan.
- To send transactional email (verification, password reset, invites). We do not send marketing email without your consent.
- To comply with law and enforce our Terms of Service.
We do not sell or rent your personal information, and we do not use your content to train AI models.
3. How we share your information
We share personal information only with the service providers required to operate Krevaya, each acting under contractual data-protection obligations:
- Social platforms — when you approve a post, we transmit it (text, hashtags, media) to the platform you chose: Meta Platforms, Inc. (Facebook, Instagram, Threads), LinkedIn Corporation, Google LLC (YouTube), Pinterest, Inc. or Tumblr, Inc. Your use of those platforms is governed by their own terms and privacy policies.
- Sign-in providers — if you choose "Continue with Google" or "Continue with Microsoft", we ask Google LLC or Microsoft Corporation to confirm who you are. We receive your email address, whether they have verified it, your display name, and an account identifier — never your password. See Google user data below for exactly what we request from Google and how we use it.
- Cloud infrastructure — Microsoft Azure hosts our application, database, and encrypted media storage. (This is separate from Microsoft sign-in above.)
- AI model providers — draft generation may be performed by vetted third-party AI infrastructure providers acting as our data processors. These calls contain only the material needed to write your draft (the topic, your niche and style preferences, and relevant prior post angles). They never include your passwords, social access tokens, payment details, or social platform data. Where generation runs on Krevaya-operated models, no third party is involved at all.
- Payments — Stripe, Inc. processes all payments and subscription billing.
- Legal requirements — we may disclose information if required by law, subpoena, or to protect the rights, safety, and security of Krevaya, our users, or the public.
A current list of our subprocessors is available on request from privacy@krevaya.com.
4. Google user data
This section describes, specifically, what Krevaya receives from Google when you choose "Continue with Google", and what we do with it. Signing in with Google is optional — Microsoft sign-in is offered alongside it.
What we request. Krevaya requests only the openid, email and profile scopes. These are Google's basic, non-sensitive sign-in scopes. From them we receive your Google account identifier, your email address and whether Google has verified it, your display name, and your profile picture.
Why we request it. Solely to authenticate you and create or match your Krevaya account, so that you do not have to create and remember another password. Your email address is the identity your account is keyed to; your name and picture are shown back to you in the app.
What we never request or access. Signing in with Google does not request, and cannot access, Gmail, Google Drive, Google Calendar, Google Contacts, Google Photos, YouTube, or any other Google service or data. YouTube access is asked for separately, only if you choose to connect a YouTube channel, and is described in section 5. We never receive your Google password. We do not use Google user data to train machine-learning models, we do not sell it, and we do not transfer it to third parties except the infrastructure providers named in section 3 who process it on our behalf.
Limited Use. Krevaya's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Revoking access. You can disconnect Krevaya from your Google account at any time at myaccount.google.com/permissions. To delete the data we hold, see section 11 and our data deletion instructions.
5. YouTube and Google data
Connecting a YouTube channel is optional and separate from signing in with Google. When you connect one, Krevaya uses YouTube API Services for two things only:
- to read the connected channel's name and picture, so you can see which channel a video will go to before you publish it; and
- to upload the videos you approved, with the title, description, tags, visibility and made-for-kids answer you chose on that video's card.
Beyond checking that a video it uploaded has finished processing, Krevaya does not read your YouTube videos, comments or subscribers. By connecting YouTube you also agree to the YouTube Terms of Service, and Google's own handling of your data is described in the Google Privacy Policy.
Limited Use. Krevaya's use of information received from Google APIs, including YouTube API Services, adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell it, use it for advertising, or use it to train machine-learning models.
Storage and revoking access. Krevaya stores the OAuth token encrypted at rest, together with the channel's id, name and picture. When you click Disconnect on the Channels page, Krevaya revokes its access at Google and deletes the stored token. If another Krevaya account is still connected to the same channel, Krevaya deletes your stored token but does not revoke, because Google's revoke would also disconnect that account. You can also revoke Krevaya's access at any time at security.google.com/settings/security/permissions. Videos already published stay on YouTube until you remove them there.
6. Pinterest data
Connecting a Pinterest account is optional. When you connect one, Krevaya receives your Pinterest username and profile picture. Each time you open a Pin draft, Krevaya reads your account name and your list of boards from Pinterest so you can choose where the Pin goes. The list is read from Pinterest when you need it rather than stored; only the name of the board you chose is kept, on that draft. Krevaya creates only the Pins you approved, with the board, title, link, alt text and description you chose, and never pins on its own. It does not read your saved Pins or messages.
Pinterest's consent screen asks you to let Krevaya read your account, read and write your boards, and read and write your Pins, because Pinterest requires all of these for an app to create a Pin. Krevaya uses them only as described above: it never creates, edits or deletes your boards, and never reads, edits or deletes your Pins.
Krevaya stores the access and refresh tokens encrypted at rest, together with your Pinterest account id, username and picture, and renews the tokens automatically so the connection does not lapse. It deletes all of this when you click Disconnect. Pinterest does not give apps a way to revoke their own access, so you can also remove Krevaya under Pinterest Settings → Security → Connected apps. Pins already published stay on Pinterest. Pinterest's own handling of your data is described in the Pinterest Privacy Policy.
7. Tumblr data
Connecting a Tumblr account is optional. When you connect one, Tumblr's own sign-in page asks you to let Krevaya read your account's basic information and write posts. Krevaya then receives your Tumblr username and the names and titles of the blogs you can post to, so you can choose which blog a post goes to. Krevaya keeps that copy for at most three days: after that it reads the list from Tumblr again the next time you choose a blog, and otherwise keeps only the name of the blog the connection is for. The name of the blog you chose for a post stays on that post.
Krevaya publishes only the posts you approved, one at a time, with the text, pictures or video, title and link you chose, to the blog you picked. It never publishes a Tumblr post on its own, never likes, follows, reblogs or replies for you, and does not read your dashboard, your posts, your followers or your messages.
Krevaya stores the access and refresh tokens encrypted at rest and renews them when it next needs them. It deletes the tokens and the details above when you click Disconnect, and you can also remove Krevaya's access under Tumblr Settings → Apps. Posts already published stay on Tumblr. Tumblr's own handling of your data is described in the Tumblr Privacy Policy.
8. International data transfers
Our primary infrastructure is located in Microsoft Azure data centers in the United States. Where personal information originating in the EEA, UK, or Switzerland is transferred internationally — including to AI processing subprocessors — we rely on appropriate safeguards such as Standard Contractual Clauses and process only the minimum content necessary to provide the feature.
9. How we protect your information
- All connections to the service are encrypted with TLS.
- Social access tokens are encrypted at the application layer before they touch the database; the encryption keys live in a dedicated cloud key vault, are fetched only at process startup, and are never written to disk or logs.
- Passwords are stored as salted bcrypt hashes.
- Production access is limited, credentialed, and logged; secrets are never stored in source control.
- No system is perfectly secure. If you believe you have found a vulnerability, please report it to security@krevaya.com — we investigate every report.
10. Data retention
- Active accounts — profile, content, and analytics data are retained for as long as your account is active.
- Deleted accounts — purged within 30 days of a deletion request (see Data Deletion), except where law requires longer retention.
- Operational logs — rolled off after at most 30 days.
- Questions asked of Ask Krevaya (the in-app assistant), with how it answered, are kept for 180 days so we can improve its answers, then deleted. This changes on December 1, 2026 (see section 13).
- Encrypted backups — expire within 35 days of deletion.
- Billing records — retained as required by tax and accounting law.
11. Your rights and choices
Depending on where you live — including under the GDPR (EU), UK GDPR, and CCPA/CPRA (California) — you may have the right to:
- access the personal information we hold about you,
- correct inaccurate information,
- delete your account and associated data (self-service from your dashboard, or via the Data Deletion page),
- receive a portable export of your data,
- object to or restrict certain processing,
- not be subject to solely automated decisions with legal or similarly significant effects — Krevaya makes none,
- (California) know what categories of personal information we collect and disclose. We do not sell or share personal information as those terms are defined by the CCPA/CPRA.
To exercise any of these rights, email privacy@krevaya.com. We verify each request and respond within 30 days. You will never be discriminated against for exercising your privacy rights.
12. Children's privacy
Krevaya is not directed to children under 13 (or under 16 where a higher threshold applies). We do not knowingly collect personal information from children; if we learn that we have, we delete it promptly. Report concerns to privacy@krevaya.com.
13. Changes to this policy
We will post material changes on this page at least 30 days before they take effect and notify registered users by email when a change meaningfully affects how their data is used. The effective date above always reflects the current version.
Upcoming change, effective December 1, 2026. Your Krevaya AI conversations with Krevaya AI (your questions and its answers) will be kept until you delete them or your account, so you can come back to them, and they will count toward your plan's storage. The details of how each answer was produced (the model used, its cost and timing, and spelling corrections) will still be deleted after 180 days, and so will questions asked outside a saved conversation.
14. Contact us
Gopherlume LLC (operating Krevaya)
330 2nd Ave S, Ste 200, Minneapolis, MN 55401, USA
Privacy requests: privacy@krevaya.com
Security reports: security@krevaya.com
Everything else: support@krevaya.com