Privacy Policy
Last updated: November 4, 2026
This policy tells what information Sigme collects, how Sigme uses and shares it, how long Sigme keeps it, and what you can do about it. A link to this policy is at the foot of the pages of the Sigme site.
Who we are
Sigme is a tool for YouTube creators: it compares the public metrics of the channels in their niche and shows what works in it. The analytics of a connected channel is visible only to its owner.
Sigme is operated by ISENDORA INC., 3040 NE 190th St, Apt 303, Aventura, FL 33180, USA. In this policy, “we” and “us” mean ISENDORA INC. We decide how your personal information is used.
For any question or complaint about privacy, email us at support@sigme.io.
Sigme uses YouTube API Services
Sigme gets the data of YouTube channels and videos through YouTube API Services. When you use Sigme, you agree to the YouTube Terms of Service: https://www.youtube.com/t/terms. How Google handles your data is in the Google Privacy Policy: http://www.google.com/policies/privacy.
What we collect
Your account
- Your email, and your password if you set one. We keep only a hash of the password, never the password itself.
- If you sign in with Google: your Google account ID, the email of that Google account, and your name and profile picture from Google. Sigme uses your first name to greet you in emails and to name you on the pages that you share.
- The time when you agreed to this policy and to the Terms of Service.
- The time zone and the main language of your browser. Sigme stores both at each sign-in. The time zone sets when your weekly report comes and when your daily limits start again. The main language shows us which languages to add to Sigme. It also sets the language of the scripts of your ideas when you have no channel, or when Sigme does not know the language of your channel.
- The language of the interface. Today it is always English.
- Your role, and whether you have a free trial, a subscription or access given by our team.
Sessions and security
- For each session: when it started, when it ends, the IP address, the browser and the device. You see your sessions in Settings and can end them.
- The time that the first screen of Sigme took to show in your browser, and the time of a press that Sigme took to answer with the share of it that your browser spent on the layout of the page, each once a visit. Sigme keeps them as numbers about its own speed, with nothing that names you, and keeps on your session only the moments when it last took such times.
- Counts of requests, to stop abuse. Sigme counts requests per IP address, per session and per email, and keeps each count with a keyed hash in place of the IP address, the session or the email.
- The searches of a channel by its link: for each account and each day of the YouTube quota, how many searches you made and the IDs of the channels that they found. Sigme limits the searches of a day with them, and deletes them after that day.
- The check that you are not a robot on the screens of sign-up, sign-in and passwords, and before Sigme sends you a code. Cloudflare Turnstile does this check.
- The codes and one-time links that we send to your email.
Your channel
You can use Sigme with no channel, add a channel by its link, or connect a channel with Google.
- A channel added by its link. Sigme reads the public data of the channel through YouTube API Services, as it does for any channel.
- A channel connected with Google. Google asks you to give Sigme two permissions. The first,
youtube.readonly, lets Sigme see which YouTube channel is yours. The second,yt-analytics.readonly, is optional. It lets Sigme read the traffic sources of your channel: the channels whose videos bring you viewers. You can connect a channel with a different Google account than the one you sign in with. - The access tokens that Google gives Sigme for your channel. Sigme stores them encrypted.
Your profile and your activity
- Your niche, your second niche, the key tags and the market of your channel, and your answer whether your content is made for kids.
- What limits your filming, and the words that you enter about your channel.
- Your feed settings, the day of your weekly report and your email settings.
- What you do in Sigme: the signals that Sigme shows you and the signals on which you press Save, Ignore or Share.
- Your ideas, the pictures of your ideas and the ideas on which you press Pin.
Payments
Stripe processes all payments. Your full card number and its security code go to Stripe and never reach our servers. On its payment form, Stripe also collects your country, your postal code where the tax needs it, and the name and tax ID of your business if you buy as a business.
We keep your Stripe customer ID, your email at Stripe, and the status and dates of your free trial and your subscription. For the card that pays for it, we keep its brand, its last four digits and its expiry date.
The waitlist
When you join the waitlist on sigme.io, we keep your name, your email and your channel as you entered it, with the time you joined. Sigme confirms the email with a code that it sends to it, and finds your channel through YouTube API Services: it keeps only the ID of the channel, with the time when it last read the channel. When our team invites you, we keep the account of the invitation with your entry.
Visits to sigme.io
Sigme counts the visits to the pages of sigme.io with its own counter, with no cookie and with nothing stored on your device. To count you once a day, Sigme reads the IP address and the user agent of your browser to make a hash of them with a random value of that day. From the user agent it also reads the type of your device, and it does not count a robot. It keeps no IP address and no user agent. Until the day ends, it keeps that hash with the source of the visit, such as Google, YouTube or a direct visit, your country and the type of your device. Soon after the end of the day, Sigme writes the counts of the day and deletes the rest, together with the random value. The counts tell nothing about you. When you join the waitlist, the entry counts for the visitor of that day.
Support
When you email support@sigme.io, we keep your emails and our answers in our support mailbox. We keep them for as long as we need them to answer you and to keep a record of what we did. When you delete your account, they go as “How long we keep your information” tells.
Public YouTube data
To show what works in a niche, Sigme collects the public data of YouTube channels and videos through YouTube API Services. This data is the titles, descriptions, tags, categories and audio languages of videos, and the names, pictures, keywords, topics and country of channels. It also includes whether the content is made for kids, and statistics, such as views. Sigme also keeps the addresses of the thumbnails of videos and reads the thumbnails, but does not store the images. Your own channel can be among these channels, as can channels of creators who do not use Sigme. See “Creators whose public channels Sigme reads”.
When you press Convert, Sigme also makes the script of the source video of the idea. This data is the words spoken in the video, who speaks them, and what happens on its screen, in the language of your channel, of your browser, or in English when neither gives one. The Gemini API of Google writes the script from the public video. A script holds no data about you, and every person who opens an idea with that video and language sees the same script.
How we use your information
- To give you Sigme: your feed of signals, your ideas with the scripts of their source videos, your weekly report and Trending. Sigme compares the public metrics of channels to find them.
- To use the analytics of your connected channel for you only. It helps Sigme choose the signals of your own feed, and only you see it. Sigme never shows it to other users and never combines it with the data that other users give through their channels.
- To email you: codes, password reset links, notices about the security of your account, emails about your trial and your subscription, and your weekly report. You can turn off the weekly report email in Settings or with the link in the email.
- To keep the waitlist: to confirm your email, to know your channel and to invite you to Sigme.
- To count the visits to sigme.io: how many people visit it each day, where they come from, and how many of them join the waitlist.
- To process your payments and to decide what you can access.
- To keep Sigme secure and to stop abuse.
- To keep Sigme fast: the time of the first screen and the time of a press tell us when Sigme shows or answers slowly.
- To find and fix errors.
- To check the quality of the texts of Sigme.
- To answer you when you email support.
We do not sell your personal information. We do not use it for advertising, and we do not track you on other sites.
Sigme’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy (https://developers.google.com/terms/api-services-user-data-policy), including the Limited Use requirements.
Model providers
Sigme sends data to OpenAI for these tasks:
- to make the texts of signals, ideas and weekly reports
- to sort videos by topic and compare them by meaning
- to read thumbnails
- to check new channels
- to judge whether a signal of another niche fits your channel
- to draw the pictures of ideas.
This data is YouTube titles, descriptions, tags, categories and thumbnails, and the names, keywords and topics of channels. It is also your profile and the words that you enter about your channel. Your profile here is your niches, your key tags, your market, your formats, whether your content is made for kids and what limits your filming. OpenAI does not use these requests to train its models. It keeps them for up to 30 days only to check for abuse, unless the law requires longer. Sigme sends some requests in batches: the files of a batch stay at OpenAI until Sigme deletes them when the batch ends, and for no more than 14 days. Sigme turns off any other storage of the requests at OpenAI (https://developers.openai.com/api/docs/guides/your-data).
Sigme sends to Google’s Gemini API only the requests that make the script of the source video of an idea. This data is the link of the public YouTube video and the language of the script. It is also the names of the people in the script and their first lines, which the Gemini API wrote from that video, so that each person gets one name. These requests hold no words that you entered and nothing else about you. Google keeps these requests and their answers for 55 days to check for abuse, and uses them to train no models other than those of that check (https://ai.google.dev/gemini-api/docs/usage-policies).
Who we share your information with
Our service providers
These companies process data for us, only to run Sigme:
| Provider | What it does for Sigme | What it gets |
|---|---|---|
| Cloudflare | hosts the site and the app, protects them, runs the check that you are not a robot, and stores the pictures of ideas, our encrypted backups and our list of deletions | your requests to Sigme with their IP address, the IP address, the TLS fingerprint and the user agent of your browser at the check that you are not a robot, the pictures of ideas, encrypted backups, and the IDs of what we deleted, for the life of our backups and one more day |
| DigitalOcean | runs our servers and databases in the European Union | all the data that Sigme stores |
| runs sign-in with Google, YouTube API Services, the Gemini API and our support mailbox | what you allow at sign-in and at the connection of your channel, the requests of the Gemini API, your emails to support | |
| OpenAI | runs the models of Sigme | the data of “Model providers” |
| Stripe | processes payments, calculates the tax, and checks a card against fraud and a second free trial | your email, the language of your account, the ID of your account in Sigme, and the data of the payment form |
| Resend | sends the emails of Sigme | your email and the content of each email |
| Sentry | collects the reports of errors, the traces, the logs and the numbers of the work of Sigme | these, with passwords, tokens, keys, emails, user IDs, YouTube texts, scripts and the words that you enter removed |
| Langfuse | keeps the instructions for the models and the records of the model calls | records of model calls, where YouTube texts, scripts and the words that you enter are replaced by their length |
| Telegram | carries alerts to our team | internal IDs and YouTube channel IDs only, no name and no email |
Cloudflare also uses what it gets at the check that you are not a robot to improve that check, under its own policy: https://www.cloudflare.com/turnstile-privacy-policy/.
Our team
Our team sees the account information that it needs to support you: your email, your name, your role, the status of your trial or subscription and your payments in Stripe. To check the quality of the texts of Sigme, our team can also run the tasks of Sigme on your profile and on the words that you enter about your channel. Our team then reads the result. Our team does not see the analytics of your connected channel.
Pages that you share
When you press Share on a signal or an idea, Sigme makes a link to a page with it. Anyone who has the link can open the page after they agree to our Terms of Service, the YouTube Terms of Service and this policy. The page shows the signal or the idea as you see it, with every block, including the parts that Sigme made from your profile and your settings. It names you by your connected channel, with its name and picture, or by your first name from Google. It shows none of the analytics of your channel.
A link works while you have the signal or the idea in Sigme. You cannot turn off a link that you shared. When you delete your account, all your links stop working.
When the law requires it, or the business changes
We share information when the law requires it, or to protect the rights and the safety of our users and of Sigme. If ISENDORA INC. merges with or sells Sigme to another company, your information goes to that company under this policy.
Content of others on Sigme
Sigme shows no advertisements.
The thumbnails of videos and the pictures of channels on Sigme load from the servers of YouTube, and the links of videos and channels open YouTube. When your browser loads them, YouTube gets the request, as with any picture from its servers. The payment form is a form of Stripe inside Sigme. The check that you are not a robot is a frame of Cloudflare inside the screens of sign-up, sign-in and passwords. The sign-in with Google happens on a page of Google.
Cookies and storage on your device
Sigme stores this information in your browser:
| What | Why | How long |
|---|---|---|
| The session cookies | keep you signed in on the address of the app, app.sigme.io, or of its test release, app-test.sigme.io, and on no other address. One of them keeps a short copy of your session, so that pages open fast | 30 days. Each visit makes them live longer. The copy lives a short time |
| The cookie of a sign-in with Google | ties the answer of Google to the sign-in that you started on this device | 5 minutes |
| The cookie of your agreement on a shared page | lets you see shared pages when you have no account | 30 days |
| The action that you chose on a shared page, with your account when you have one | takes you back to that action after you sign up, sign in or pay | until the action is done or you sign out. After one day it no longer runs, and it leaves your browser the next time you open Sigme |
| The shared page that you left for the sign-up, the sign-in or the payment screen | takes you back to that page after you sign up, sign in, pay or close the payment screen | until you return to it or sign out. After one day it no longer opens that page, and it leaves your browser the next time you open Sigme |
| The data of the app | copies of the data that you already opened, so that screens open fast and work with no connection | at most one day, and it is deleted when your session ends |
| The files of the app | Sigme opens with no connection | until a new version of the app replaces them |
| The actions that you take with no connection | they go to Sigme when the connection comes back | until they go |
| Marks of the device | for example, that the payment screen was already shown on this device | while you use Sigme in this browser |
Cloudflare can set cookies that protect Sigme from attacks (https://developers.cloudflare.com/fundamentals/reference/policies-compliances/cloudflare-cookies/). Stripe sets its own cookies on its payment form to prevent fraud (https://stripe.com/legal/cookies-policy).
Sigme uses no advertising cookies and no analytics cookies. The count of the visits to sigme.io stores nothing on your device. If you delete the cookies of Sigme in your browser, you are signed out.
Sigme does not track you across other sites. A Do Not Track signal of your browser changes nothing in how Sigme works.
How to revoke the access of Sigme
You can stop the access of Sigme to your YouTube channel at any time, in two ways:
- Disconnect your channel in Settings. Sigme then revokes its access at Google and deletes the access tokens and the analytics of your channel within 7 days.
- Revoke the access on the Google security settings page: https://security.google.com/settings/security/permissions. Sigme finds the revocation at its next check of the access, and deletes the same data within 30 days of the revocation.
Your account stays. You can still use Sigme with a channel added by its link or with no channel.
How long we keep your information
- Your account and your activity: while you have the account. When your trial or subscription ends, your data stays, and it comes back to you when you pay again.
- When you delete your account: you delete it in Settings, or ask us at support@sigme.io from the email of your account. We then email you at the email of your account, and we delete the account after your answer from it. Your sessions end as soon as the deletion starts: at once in Settings, on the day of your answer for a request by email. Within 7 days, we cancel your subscription, delete your customer record at Stripe and delete your data. Your data includes the data of your channel that Sigme got with your permission and your emails to support. If a service that the deletion needs does not answer, we finish the deletion as soon as it answers again. After the deletion, no database of Sigme keeps your email. Google keeps an email that we erased from our support mailbox for 25 more days, and only our administrator can restore it. The log of sent emails at Resend keeps each email for 30 days after it was sent. Stripe keeps the payment records that the law requires it to keep. Deleting your data in Sigme does not change anything on YouTube: to delete data on YouTube, use YouTube itself.
- An account with an email that was never confirmed: we delete it 3 days after the sign-up.
- A visit to sigme.io: its hash, the source of the visit, your country and the type of your device until soon after the end of the day of the visit. Then only the counts of the day stay.
- Your entry on the waitlist: for one year from the day you joined, also after we invite you. Sigme refreshes the ID of your channel within 30 days, or deletes it. To delete your entry earlier, email us at support@sigme.io. When you delete an account with the email of your entry, or the account of its invitation, the entry goes with it.
- The analytics of your connected channel: while the channel is connected. For a revocation, see “How to revoke the access of Sigme”.
- Public YouTube data: Sigme refreshes or deletes titles, descriptions, channel names and other YouTube texts within 30 days. Statistics and the metrics that Sigme calculates from them stay for up to 36 months. When a video or a channel leaves YouTube, Sigme deletes its data.
- Scripts: Sigme deletes a script on day 29 after it made it, and makes it again when an idea opens it later. When Sigme deletes the data of its video, the script goes with it. The deletion of your account deletes no script, because a script holds no data about you.
- Our backups: they are encrypted and live 7 days. The periods above for the deletion of your account and for the access to your channel include them. After any other deletion, a backup keeps the data for up to 7 more days. After we restore a backup to recover from a failure, the backups of the restored database can keep deleted data for up to 7 more days.
Your rights
You can ask us to show, correct, export or delete your personal information, to stop or limit a use of it, or to object to a use of it. In Settings you can change your profile and your settings, disconnect your channel and delete your account. For the rest, email us at support@sigme.io. We answer within one month. When you ask us to delete your account, we delete it as “How long we keep your information” tells. If you live in the European Union or the United Kingdom, you can also complain to the data protection authority of your country.
If you live in California, you have the right to know, to delete and to correct your personal information, and the right to equal service when you use these rights. We do not sell or share your personal information for advertising.
The legal basis of the use
Where the law of the European Union or the United Kingdom applies, we use your information:
- to perform our contract with you, or to take the steps that you ask for before one: your account, Sigme itself, your payments and the emails about them, and your entry on the waitlist
- for our legitimate interests: the security of Sigme, the prevention of abuse, the repair of errors, the choice of the languages that Sigme adds, the count of the visits to sigme.io, and the comparison of public YouTube channels
- to meet our legal duties, for example for taxes
- with your consent where we ask for it, for example when you connect your channel with Google.
Creators whose public channels Sigme reads
Sigme reads the public data of YouTube channels to compare the channels of a niche, also the channels of creators who do not use Sigme. This data is the name, the picture, the keywords, the topics and the country of the channel, and its videos with their titles, descriptions, tags, categories, audio languages, thumbnail addresses and statistics, and whether they are made for kids. Sigme gets this data only through YouTube API Services. When a video of such a channel is the source of an idea, the Gemini API writes its script, as “Public YouTube data” tells. Sigme keeps this data as “How long we keep your information” tells. Our legal basis is our legitimate interest in showing creators what works in their niche. If you own a channel and object to this, email us at support@sigme.io with the link to your channel. We answer within one month.
Where your information goes
We are based in the United States. Our servers and databases are in the European Union. Some of our service providers process data in the United States and in other countries. Where the law requires it, we protect such transfers with the safeguards that the law provides, such as the Standard Contractual Clauses of the European Commission.
Children
Sigme is not for children under 13. If you are under 18, or under the age of majority where you live, you can use Sigme only with the permission of your parent or legal guardian. We do not knowingly collect information from children under 13. If you learn that a child under 13 uses Sigme, email us at support@sigme.io, and we delete the account.
Security
Sigme uses encrypted connections (HTTPS), and keeps the access tokens of channels and our backups encrypted. Only the people of our team who need access to run Sigme have it.
Changes to this policy
When we change this policy, we change the date at its top. Before Sigme uses YouTube data in a way that the policy you accepted does not cover, Sigme asks you to accept the new policy.
Contact
ISENDORA INC., 3040 NE 190th St, Apt 303, Aventura, FL 33180, USA