Submit a loop

Privacy Policy

Last updated October 7th, 2026

This policy explains what personal data loopvember.vision collects, why we collect it, who can see it, how long we keep it, and what you can do about it. It covers the website, signing in with Discord, the optional contest, and the tool we use to find public posts that use the event hashtags.

Who we are and how to reach us

Loopvember is a yearly community challenge. Editors post short, seamless looping videos all through November. Loopvember is open to everyone, has no winner, and nobody owns it.

On top of Loopvember, amv.vision runs an optional contest and the website loopvember.vision. In this policy, 'we', 'us' and 'our' mean amv.vision. We decide how the data described here is used. The rules for the site and the contest are in our Terms and contest rules.

To ask a question, use your rights, or ask us to remove something, email us at contact (at) loopvember.vision. Everywhere else in this policy, 'email us' means this address.

The short version

  • You can watch loops without an account.
  • If you sign in with Discord, we keep your Discord user ID, username, display name and avatar. We do not get your email address or your password.
  • Your comments are public, with your Discord display name and avatar. Who you gave stars to is not public.
  • We look for public TikTok and Instagram posts that use the event hashtags, and we may store copies of them to show on the site.
  • We count visits with our own simple statistics, without cookies, using a code that changes every day.
  • Our own database and statistics do not store your IP address.
  • We do not sell your data, we do not show ads, and we do not use advertising or tracking cookies.
  • You can ask us at any time to see, fix or delete your data.

When you visit the site

As with any website, our host Cloudflare receives some technical data each time your browser asks for a page, picture or video. This includes your IP address and your browser details (the user agent). Our own database and site statistics do not store your IP address.

  • Request logs. Cloudflare keeps logs of requests to our site so we can run it and fix problems. A log entry can include the full web address that was asked for, including anything after the question mark in the address. It can also include the time, the result, and technical details that Cloudflare adds, which may include your IP address and browser details. These logs are kept for up to 7 days.
  • Abuse limits. We use your IP address to limit how often our statistics counter can be called. This limit lasts about 60 seconds. If someone types a wrong organiser code on the site, we store a count with a scrambled code made from their IP address, to stop guessing. We do not store the IP address itself. Old records are deleted after their one-hour window, the next time anyone enters an organiser code.
  • Site statistics. We count page visits. See Site statistics.
  • Browser storage. The site saves settings, such as dark or light mode, in your browser. See Cookies and browser storage.
  • Other services. Your browser also loads fonts and some pictures from other services, which see your IP address. See Who we share data with.

Why: to deliver the site, keep it safe and stop abuse. Our legal reason is our legitimate interest in running a safe, working site.

When you sign in with Discord

You do not need an account to watch. You need to sign in with Discord to give stars, comment, like comments, search for GIFs, save loops or submit a link.

  • What we get from Discord. We only ask Discord for basic profile access (the 'identify' permission). Discord then sends us your basic profile. This includes your user ID, username, display name and avatar, plus a few basic account details. We keep only your user ID, username, display name and avatar. We do not get your email address, your password, your servers or your messages.
  • Access key. Discord gives us a one-time key to read your profile. We use it once and then throw it away. We do not keep it.
  • How you stay signed in. We put your Discord user ID, display name, username and avatar into a signed cookie called loopsid in your browser. It lasts 30 days, or until you sign out in that browser. We do not keep a separate list of accounts on our server.
  • When your details reach our database. Your Discord details are saved in our database only when you do something, such as post a comment, give a star, save a loop or submit a link. See Stars, comments, likes, saved loops and submissions.
  • Copy in your browser. The page also keeps your user ID, display name, username and avatar in your browser's local storage, so it can show you as signed in. It is removed the next time the page loads after you sign out.

Why: to sign you in, show your name and avatar, and connect your actions to your account. For example, this lets us give each account 10 stars and stop you from starring your own entry. Our legal reason is that you asked us to provide these features.

If you remove our app in your Discord settings, this does not sign you out of our site. It also does not delete anything we hold, because we do not keep your Discord key. To delete your data, email us.

Stars, comments, likes, saved loops and submissions

When you are signed in and use these features, we save the following in our database at Cloudflare.

  • Comments. We save your text (up to 400 characters), any GIF you picked, the loop it is on and the comment it replies to. We also save the time, the number of likes, and your Discord user ID, display name and avatar. Anyone can see your display name, avatar, comment, GIF, time and likes, even without signing in. Recent comments may also appear in a list of the latest comments on the site. If you use a custom Discord avatar, your Discord user ID is also public, because it is part of the avatar's web address. We save your name and avatar when you post. We do not update them if you change them on Discord later.
  • Editing and deleting comments. When you edit a comment, the new text replaces the old text, and we do not keep the old version. When you or an organiser delete a comment, it is hidden everywhere on the site. The record stays in our database, marked as removed. If you want it fully erased, email us.
  • Likes. We save which comment you liked, your account ID and the time. Only the number of likes is public. If you unlike, the record is deleted.
  • Stars. We save your account ID, the loop, how many stars you gave (0 to 3) and the time. Your browser also keeps a copy of your own picks until you sign out. Other visitors cannot see who you gave stars to. Star totals for each loop are hidden from the public until results are published. Organisers can see the totals at any time. Organisers may look at star records to check for suspicious voting before results are final.
  • Saved loops. We save the loop, your account ID and the time. Only you can see your saved list on the site. If you unsave a loop, or the loop is taken down, the record is deleted.
  • Submissions. When you submit a TikTok or Instagram link, we save the link, the creator handle you type, and whether you ticked 'I made this loop'. We also save your Discord user ID and display name, the post date, its review status, and the times. For TikTok links, we read the post date from the link itself. Your browser also keeps the links you submitted from it. Once a loop is approved, the public sees its link, creator handle, caption, post date and status. Only organisers see who submitted it and whether 'I made this loop' was ticked.
  • Limits. To stop spam, we keep a counter for your account that limits how many stars, saves and likes you can make in an hour. The counter is reused each hour and is not deleted on a fixed schedule.

Why: to provide the features you use and to run the contest. For example, we use this data to show discussion, count stars and credit creators. It also lets us stop people from starring their own entries, and contact you on Discord if your entry wins. Our legal reason is that you asked us to provide these features. Checking for vote abuse and stopping spam are in our legitimate interest in a fair contest and a working site.

Contest results and winners

  • When results are published, two numbers for each loop become public: its star total and how many accounts gave it stars. Who gave the stars stays private.
  • We show the finalists and winners with their loops, creator handles and results on the site. We may also share them on amv.vision's social media accounts.
  • We contact winners through the social accounts on their entry, or on Discord if they submitted through the site. The site does not ask for your email or postal address.
  • If a prize is offered and we need more details, such as a delivery address or a parent or guardian's permission, we will ask the winner directly. We will use those details only for the prize.
  • If you do not want your handle shown with the results, email us before results are published.

Why: to run the contest you entered and announce its results. Our legal reason is that you asked to take part. Publishing results is also in our legitimate interest in running an open, fair contest.

Public posts found on TikTok and Instagram

This part is also for creators who have never visited our site. If you post a loop with an event hashtag, we may find it and show it.

  • How we find posts. We run a tool on a rented server. It looks at public TikTok and Instagram hashtag pages and posts for the event hashtags that organisers choose, such as #loopvember and #loopvember26. It reads these pages directly, sometimes while signed in to an organiser's own account, or through a scraping service called Apify. Organisers can also add post links by hand, and anyone signed in can submit a link.
  • What we collect. For each post we keep: the link, the platform, the creator handle, the caption, the post time, the hashtag that matched, a thumbnail picture and the video file. We do not keep likes, views, follower counts or other profile details. When we use Apify, its results also include other public details, such as like and view counts and the creator's public profile details. Our tool does not keep these, but Apify stores the raw results in our Apify account for a limited time, under its own rules.
  • Copies. When the tool finds a post, it saves a small preview copy of the video and a poster picture in our Cloudflare storage. After an organiser approves a post, we may also save a better quality copy.
  • Review. Posts the tool finds go into a private list that only organisers can see. An organiser decides to keep or discard each one. If we discard a post, we either delete it, or keep only its link, handle and caption so the tool does not pick it up again. In that case its thumbnail and video are removed from the list, and the stored files may also be deleted.
  • Showing posts. If we keep a post, we show it on the site with the creator handle, caption, post date and a link to the original. Our stored copies let the loop play smoothly. Our server checks that these files are requested from our own site pages. If we have no copy, your browser plays the post from TikTok or Instagram instead.
  • Captions and pictures. Our server may read a post's caption from TikTok's public embed service. It may also fetch an Instagram post's cover picture. For a few older entries, it may read public post details from X. The site checks captions for #amvvision to mark loops that are part of the contest. Posts without #amvvision can still be shown as part of Loopvember.
  • Logs. The tool writes simple logs on its server, which include post links and creator handles. These logs have no fixed deletion time.

Why: to find, show and credit loops made for Loopvember, and to run the contest. Our legal reason is our legitimate interest in running a public community challenge built around a public hashtag.

Want your post removed? Email us with the link to your post. We may ask you to show that the post is yours. We will take it down from the site and delete our stored copies. You do not need to give a reason. Copies already saved in someone's browser or in network caches can stay there for some time after we delete them.

GIF search through KLIPY

  • When you are signed in and open the GIF picker in a comment box, your browser contacts KLIPY (api.klipy.com) directly. KLIPY then shows trending GIFs and search results.
  • KLIPY receives your search words, a page number, a content filter setting (PG-13) and a random ID. KLIPY also sees your IP address and browser details.
  • The random ID is made in your browser and saved there (loopnovember.klipy.v1). It is reused until you clear site data. It does not contain your name or your Discord details.
  • We do not save your searches. We only save the GIF you choose, as part of your comment.
  • Everyone who views a comment with a GIF loads that GIF from KLIPY (static.klipy.com).

Why: to give you GIF search in comments. Our legal reason is that you chose to use it.

KLIPY uses this data under its own privacy policy. That policy says KLIPY may use information such as your search words, the GIFs you view and your rough location from your IP address, including for advertising. If you do not want to share this data with KLIPY, do not open the GIF picker.

Site statistics

We count visits so we know how people find the site and which parts they use. We do this with Cloudflare Workers Analytics Engine, which stores the numbers for our own use. We do not use Google Analytics or any advertising or tracking network, and we set no cookies for this.

  • Page visits. When a page loads, we record the page address and where you came from. For example: direct, TikTok, Instagram, Discord, YouTube, Google, X, or the name of another website. We also record any campaign tag in the link, your device type (phone, tablet or desktop) and a daily visitor code. We record a two-letter location code from Cloudflare that shows roughly where the visit comes from. Known bots are not counted.
  • What you open. The page also counts which parts of the site you open, such as the grid, reel, ranking, stars, judges, comments, saved, about and search views. It counts which loops you open, at most once per loop every 30 minutes. It sends these counts at most every 20 seconds, and when you leave the page. They do not include your name or account. Our server adds the same location code, device type and visitor code.
  • The daily visitor code. To count visitors without cookies, our server mixes the date, your IP address and your browser details with a secret key, and keeps a short code. The code changes every day. We do not save your IP address or full browser details in the statistics. The code is not fully anonymous. Someone with our secret key who already knew your IP address and browser details could make the same code for that day.
  • Who sees it. Only organisers, and only as totals: visits and visitors per day, sources, campaigns, locations, devices, and the most opened views and loops.
  • How long. Cloudflare keeps this data for about three months. Our dashboard shows the last 30 days.

Why: to understand and improve the site. Our legal reason is our legitimate interest in knowing how the site is used. You can object at any time by emailing us.

Organiser and judge information

  • Organiser accounts. If an organiser links organiser access to their Discord account, we save their Discord user ID, display name and the time. This stays until an organiser removes it.
  • Organiser notes. Organisers keep private notes, labels and calendar events to run the event. These may mention entries or creators. Only organisers can see them.
  • Tool records. We keep records of each run of the finding tool and each video download job. They include post links (which contain creator handles), settings and progress notes. Only organisers can see them.
  • Judges. The judges page shows judges' names, short descriptions, and pictures or video backgrounds that organisers add.

Why: to run and organise the event. Our legal reason is our legitimate interest in organising Loopvember and the contest.

Our legal reasons, in plain words

Privacy laws ask us to name a legal reason for each use of your data. We use these:

  • You asked for it. We need the data to give you what you chose to use: signing in, comments, likes, stars, saved loops, submissions, GIF search, taking part in the contest, and receiving a prize.
  • Legitimate interests. We use data to keep the site safe and working, and to stop abuse and fake votes. We also use it to find and show public posts with the event hashtags, credit creators, publish results, organise the event and count visits. We only do this when it does not unfairly affect your rights.
  • Legal duties. We may use or keep data when the law requires it. For example, we may need to answer a valid legal request or a copyright notice.

Your right to object. When we rely on legitimate interests, you can object at any time. Email us and tell us what you object to. We will stop, unless we have strong reasons to continue that outweigh your interests, or we need the data for a legal claim.

Automatic rules and human review

  • The site applies some fixed rules automatically: 10 stars per account, up to 3 stars per loop, and stars only while voting is open.
  • Stars can only go on approved loops from this year's event that are part of the contest.
  • There are limits on how many comments, stars, saves, likes and submissions you can make in a short time.
  • The site stops you from starring a loop you submitted as your own, or a loop whose creator handle matches your Discord username.
  • The site checks captions for #amvvision automatically. If it cannot read a caption, it does not leave the loop out, and an organiser decides. Organisers can also mark any loop as a contest entry or not by hand.
  • Reviews of suspicious voting, decisions about reuploads and other entries, and the choice of winners are made by people.

We do not use your data for profiling or advertising.

Cookies and browser storage

Cookies. Our site sets only these three cookies. They come from loopvember.vision itself, and all three are needed to run the site.

  • loopsid: keeps you signed in. It holds your Discord user ID, display name, username, avatar and an expiry time, with a signature so nobody can change it. Page scripts cannot read it. It lasts 30 days, or until you sign out in that browser.
  • loopstate: protects the Discord sign-in step against forged requests. It holds a random value, lasts 10 minutes, and is removed after you sign in.
  • looppass: used only while the site is in private preview, to let invited visitors in. It is the same for everyone and holds no personal data. It lasts up to 365 days.

We set no advertising, analytics or tracking cookies, and we do not track you across other websites. The site does not change how it works when your browser sends a Do Not Track signal, because we do not do this kind of tracking. Some services your browser loads, such as the TikTok, Instagram and YouTube players, may set their own cookies under their own policies. If our host Cloudflare uses its security checks on a visit, it may also set its own security cookie. We do not control those cookies.

Local storage. The site saves these items in your browser. They stay on your device, unless we say otherwise below.

  • Settings
    • loopnovember.theme: dark or light mode.
    • loopnovember.sound.v1: volume and mute.
    • loopnovember.autoscroll: auto scroll on or off.
    • loopnovember.savedlook.v1: the layout of your saved list.
    • loopnovember.appicon.v1: the home screen icon.
    • loopnovember.mode.v1: preview mode for organisers, users or guests.
    • loopnovember.giffav.v1: your favourite GIFs from the comment GIF picker, kept separately for each account on this device.
  • Your account on this device
    • loopnovember.account.v1: your Discord user ID, display name, username and avatar, so the page shows you as signed in. It is removed after you sign out.
    • loopnovember.me.v1: a random guest ID. The page may send it with some requests, but our server does not use or save it.
  • Your activity on this device
    • loopnovember.local.v3: links you submitted from this browser, your star picks and other page state. For organisers, it also holds their notes, labels and calendar events.
    • loopnovember.local.v3.dropped and loopnovember.local.v3.seeded2: loops hidden on this device, and a setup marker.
    • loopnovember.seen.v1: a visit count and the loops already shown, used to order the Discover view.
  • Speed and display
    • loopnovember.shots.v1: thumbnails, author names and titles from TikTok and YouTube, reused for 36 hours.
    • loopnovember.meta.v3: post details such as handle, name, caption, post time and length.
    • loopnovember.ratios.v1: video shapes.
    • loopnovember.vxfit.v1: picture crop settings.
  • GIF search
    • loopnovember.klipy.v1: the random ID sent to KLIPY.
  • Organiser tools
    • loopnovember.search.v1: a draft of the finding tool's search form.
    • loopnovember.adminkey.v1: an older copy of the organiser code. The site moves it to session storage and deletes this copy.

Session storage. These items are deleted when you close the tab.

  • loopnovember.draft.v1: an unsent comment, kept while you sign in with Discord and removed once it is put back.
  • loopnovember.adminkey.v1: the organiser code for the current tab, for organisers only.

Emoji picker. If you open the emoji picker, a library loaded from jsDelivr saves some data in your browser's database (IndexedDB). This is the emoji list, your preferred skin tone and your most used emoji.

All of this is needed for features you use. You can delete it at any time by clearing site data for loopvember.vision in your browser settings. This also signs you out on that device.

Who we share data with

We do not sell your data. We do not share it for advertising, we do not show ads, and we do not build profiles from your Discord data.

Services that work for us. These providers handle data to run the site for us.

  • Cloudflare hosts the site and runs our server code, database, file storage, statistics, request logs, abuse limits and caching. The site's database, files and statistics are stored with Cloudflare. The finding tool's logs, our emails and Apify's raw results are held by the providers below.
  • Discord handles sign-in.
  • Apify is a scraping service our finding tool may use to read public TikTok and Instagram posts. It keeps the raw results of each search in our Apify account for a limited time.
  • A server provider hosts the finding tool and its logs. It also holds video files for a short time while they are processed.
  • Our email provider holds the emails you send to our contact address.

Services your browser contacts directly. When your browser loads something from these services, they see your IP address, your browser details, and that you came from loopvember.vision. They use this under their own policies.

  • Google Fonts (fonts.googleapis.com and fonts.gstatic.com): fonts, on every page.
  • KLIPY: GIF search when you use it, and GIF pictures when you view a comment with a GIF. See GIF search through KLIPY.
  • Discord (cdn.discordapp.com): avatar pictures next to comments and your account.
  • jsDelivr: the emoji picker code and emoji list, only when you open the emoji picker.
  • TikTok and Instagram: their video players, thumbnails or cover pictures, only when we do not have our own copy of a loop.
  • TikTok's embed service (www.tiktok.com): when the page shows TikTok loops, your browser asks this service for each post's title, creator name and the address of its thumbnail picture. This happens even when we have our own copy of the loop. The page saves the answer in your browser and uses it again later.
  • YouTube (www.youtube.com, youtube-nocookie.com and i.ytimg.com): when a judge card uses a YouTube video or picture, and for a few older entries. For those entries, your browser may also ask YouTube's embed service for the title and thumbnail.
  • Other websites: if organisers use a picture or video from another website as a judge card background, your browser loads it from that website.

The links to the amv.vision profiles on TikTok, Instagram, X and YouTube at the bottom of the page send nothing until you click them.

Sources. The public posts we show come from TikTok and Instagram. Our server may also ask TikTok's public embed service for a post's caption, and ask Instagram for a post's cover picture. For a few older entries, it may ask X for post details. The page in your browser also asks TikTok's embed service for post titles, creator names and thumbnails, as described above.

Organisers. A small team of organisers can see the private data described in this policy, such as who submitted a loop and star totals during voting.

The public. Some things are public by design: comments with display names and avatars, approved loops with creator handles and captions, and results.

Everyone else. Apart from the above, we share data only if the law requires it, or if you ask us to.

Where your data is processed

Our providers run servers in many places. Your data may be processed and stored outside the place where you live, where data protection laws may be different. For the providers that work for us, these transfers are covered by approved safeguards where the law requires it. Examples are standard contract terms approved by data protection authorities, and certified transfer frameworks that our providers take part in. Each provider's privacy policy has the details.

How long we keep data

  • Sign-in cookie (loopsid): 30 days, or until you sign out in that browser.
  • Sign-in safety cookie (loopstate): 10 minutes.
  • Preview cookie (looppass): up to 365 days, only while the private preview is on.
  • Request logs at Cloudflare: up to 7 days.
  • Abuse limit on the statistics counter: about 60 seconds.
  • Site statistics: about three months.
  • Short copies for speed: Cloudflare keeps short copies of public data, such as comment lists and the list of loops, for between 20 seconds and 10 minutes.
  • Comment summaries: to load pages faster, we keep the number of comments and the 4 newest comments on each loop, with their display names and avatars. When a comment is deleted or removed, we update this summary.
  • Comments, likes, stars, saved loops, submissions, found posts and stored videos: as long as we run Loopvember and keep its results and archive, or until you ask us to delete them. We do not delete these on a fixed schedule today.
  • Removed comments and taken-down loops: hidden from the site, but the records stay in our database until we erase them on request. For taken-down loops, we delete the video and picture files. Comments and stars on those loops stay in the database.
  • Wrong organiser code attempts: a count with a scrambled code, never the IP address itself. Old records are deleted after their one-hour window, the next time anyone enters an organiser code.
  • Account limit counters and the finding tool's logs: no fixed deletion time today.
  • Raw search results at Apify: kept in our Apify account for a limited time, under Apify's own rules. Our tool keeps only the details listed in Public posts found on TikTok and Instagram.
  • Browser storage: until you clear site data. Your account copy is also removed after you sign out.
  • Emails you send us: as long as we need them to answer you and keep a record of your request.

Browsers and networks keep video and picture files in their caches for a long time. After we delete a file, copies saved earlier may stay there for some time.

Your rights and how to use them

You have these rights over your personal data:

  • See the data we hold about you and get a copy.
  • Get it in a common format that you can move to another service.
  • Fix data that is wrong, for example an old name on past comments.
  • Delete your data.
  • Ask us to limit how we use your data.
  • Object to how we use your data. See Our legal reasons, in plain words.
  • Complain to the data protection authority where you live. We would like the chance to help first, so please email us.

How to ask. Email us. Tell us your Discord username, or the link to your post if we found it on TikTok or Instagram, so we can find your data. We may ask you to show that the account or post is yours. Asking is free. We will answer within one month. If a request is complex, we may need up to two more months, and we will tell you why.

What you can do yourself today:

  • Sign out. This ends your sign-in in that browser only. A sign-in on another device ends when its cookie runs out, within 30 days.
  • Edit or delete your own comments. Deleting hides a comment everywhere on the site. To erase it fully, email us.
  • Unlike a comment. This deletes the like.
  • Move or take back your stars while voting is open (planned for December 1st to December 7th, times in UTC). After voting closes, stars are locked.
  • See your own star picks and your own comments.
  • Save and unsave loops.
  • Clear your browser storage for loopvember.vision.

What needs an email:

  • deleting all your data
  • getting a copy of your data
  • removing or changing a link you submitted
  • updating your name or avatar on past comments
  • removing a post we found on TikTok or Instagram
  • reporting a comment or a loop (there is no report button on the site)

What deletion covers. When you ask us to delete your data, we delete your comments (including hidden ones), likes, stars, saved loops and account limit counters. We remove your Discord details from links you submitted, and we remove any organiser access. We also update the comment summaries, so your comments stop showing anywhere on the site. In some cases we may need to keep some data, for example to finish a review of suspicious voting or to keep published results correct. The law may also require us to keep some data. If so, we will tell you what we keep and why.

Removing our app in your Discord settings does not delete your data on our site. Please email us instead.

Children

  • To sign in with Discord, you must meet Discord's minimum age where you live. Discord asks for your age. We do not check ages ourselves.
  • If you are under the age of majority where you live, you need a parent or guardian's permission to enter the contest and to accept any prize.
  • Parents and guardians can email us to ask us to remove a child's data, including a post our finding tool picked up. We will delete it.

How we protect your data

  • The site is served over HTTPS, and our cookies are only sent over secure connections.
  • Your sign-in cookie is signed so it cannot be changed, and page scripts cannot read it. It is not encrypted, but it only holds your Discord user ID, names, avatar and an expiry time.
  • We never see your Discord password, and we do not keep your Discord access key.
  • Cloudflare encrypts our database and file storage when the data is stored.
  • Organiser pages and private data need an organiser code or a linked organiser account.
  • We limit how often actions can be repeated, to stop abuse.

No system is perfectly safe. Please sign out on shared devices. If a data breach affects your personal data, we will tell you, and the authorities, where the law requires it.

Changes to this policy

We may update this policy when the site, the contest or the law changes. When we do, we will change the 'Last updated' date at the top. If a change is important, we will also announce it on the site.

Other privacy policies

The services named in this policy have their own privacy policies. Here are some of them: