edvly
How it worksPricingHelpSign inStart creating ↗
EDVLY

Privacy Policy

Updated October 21, 2026

Edvly is a marketing chat that helps you research public TikTok references, analyze their hooks and create original slideshow images. This policy explains the information processed when you use Edvly and how to contact us with a privacy request.

Information we process

  • Account details: your email address and optional name. If you sign in with a password, Edvly stores a password hash rather than your readable password. If you use Google sign-in, Google provides basic account details and an account identifier to complete sign-in.
  • Marketing conversations and creations: your messages, saved app information, website and TikTok links, search terms, public reference metadata, storyboards, captions, generated images and credit usage, provider-cost records and billing-period allowances. Conversations and creations are saved to your account so you can revisit them.
  • Billing records: subscription and payment status and Stripe customer or subscription identifiers. Payments are processed by Stripe; Edvly does not receive your full card number through its application.
  • Technical information: session and request information needed to sign you in, keep the service secure, and operate the website. We use a first-party random browser identifier to estimate unique visitors by day; the identifier is hashed before it is stored with a visit date. Hosting and security providers may process network details such as your IP address and browser request metadata.

How we use information

We use this information to operate your account, search public sources for the companies and topics you submit, create and save marketing answers and images, track credits and manage subscriptions, prevent abuse, troubleshoot the service, and respond to requests.

Service providers and public sources

To provide Edvly, information is processed by providers that host the service and database (Cloudflare), provide Google sign-in (Google), handle payments (Stripe), and retrieve public web and social information (Monid and its data-source providers). When you request an analysis, relevant company links and search terms may be sent to data providers to find public results. Those providers process the request to return the requested results.

Edvly uses publicly accessible sources. We do not ask for your social-media passwords. Public posts and reviews remain subject to the rules and privacy practices of the platforms where they appear. Service providers may process information in countries other than yours.

Relevant conversation context, app details and public reference media may be sent to Google Gemini for writing and analysis. Image prompts are sent through Monid to the selected image provider (currently GPT Image 2.5 Flare). Generated images are stored in private account-scoped storage on Cloudflare. These providers receive the inputs needed to complete your requested action. Provider credentials stay on the server.

DataFast measures site visits and attributes completed purchases to traffic sources. A random DataFast visitor/session identifier may be attached to Stripe checkout metadata. Your marketing conversations and image prompts are not added to payment metadata.

Security and prevention of trial abuse

Cloudflare Turnstile checks sign-in and registration requests to help prevent automated abuse. Its verification may process browser and network information under Cloudflare’s privacy terms. Edvly uses a signed, first-party security cookie lasting up to 180 days. We store keyed hashes of the network address, security-cookie identifier and normalized email to limit repeated registrations and free-trial claims. Network limits use recent 24-hour and 30-day activity, and browser limits use a 180-day window. Abuse-prevention records expire after 365 days and are removed by bounded maintenance. We do not request precise location or create a browser fingerprint for these controls. Shared networks can affect these limits; contact support if a legitimate registration is blocked.

Cookies and storage

Edvly uses an essential session cookie to keep you signed in and a first-party visitor cookie to measure approximate unique visits. The visitor cookie lasts up to one year; a separate daily marker reduces repeat counting. Account and report information is stored while needed to provide the service and maintain your account. Some billing or security records may be kept for longer when required to manage payments, prevent abuse, or meet legal obligations.

Your choices and requests

You can export your saved app details and conversations from Settings and download your images in chat. You can contact us to request correction or deletion of information associated with your account. We will handle requests under the laws that apply. To stop using Edvly, you can also sign out and contact us about closing your account and removing saved reports.

Retired discovery and mailbox features

The previous prospecting and outreach product is retired. Its searches, sending agents, follow-ups and mailbox synchronization are disabled. Historical product briefs, public-source records, outreach, replies, opt-out records and encrypted connection tokens may remain associated with your account for recovery or deletion requests. They are not used by the new marketing chat.

You can revoke an earlier Gmail or Microsoft connection in that provider’s account permissions. Contact us to request deletion of saved connection tokens or historical records. Google sign-in remains separate from mailbox access.

Edvly’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use email data for advertising or to train generalized AI models.

Contact

For privacy questions, urgent matters, or requests, email edvly.info@gmail.com.

Changes to this policy

We may update this policy as Edvly changes. The updated date above indicates when the current version was published.

← Back to Edvly
edvlyYour next great post starts here.
HelpPrivacyTerms