Cinemagraphs.space
Privacy Policy
Last updated:
This policy explains how the operator of Cinemagraphs.space ("we", "us") processes information when you browse the website, create an account or publish work. For privacy questions or requests, email eleprimer@gmail.com.
Information we process
Accounts and profiles. We store your email address, username, display name, account creation time and account status. You can add an avatar, biography, location and website link. Passwords are stored as Argon2 hashes rather than readable passwords. Email verification and password recovery use tokens and expiry times.
Content and interactions. We store uploaded images and videos, processed video loops, thumbnails and previews, titles, descriptions, categories, related Coub links, publication times and visibility settings. We also store comments and replies, mentions, work and comment likes, saved works, follows, and notifications about interactions.
Usage and technical information. The site records work views, dates, navigation sources and share counts. A random browser-session identifier is used to avoid duplicate view counts; the server stores a hash of the view receipt. Signed-in views are also associated with the account and day. Creator insights show counts and trends, including the number of signed-in viewers, rather than a list of those viewers. Server access and error logs can contain IP addresses, request URLs, browser information, referrers, timestamps and errors. Download processing also uses temporary job records and hashed identifiers for rate limiting.
What is public and what stays private
Your username, display name, avatar and optional profile fields are public. Public works, their titles and descriptions, comments, likes, the public works you have liked, and follower/following lists and counts can be seen by other visitors. Public content may be indexed by search engines, embedded, downloaded or copied by others.
Your account email, password hash, verification and recovery tokens, saved-work collection and personal notifications are not displayed publicly. Drafts, scheduled works before publication and works marked private are excluded from public browsing; access is restricted to the owner and authorized administrators. Creator insights are restricted to the creator. Authorized administrators can access information needed to operate the service and moderate content. Please avoid putting private information in public profile fields, comments or uploads.
Why we use information
We use information to create and operate accounts, authenticate users, manage profiles, process and publish media, support comments and social features, deliver notifications, and provide creator statistics. We also use it to protect accounts, limit abuse, investigate errors, moderate content and keep an audit trail of administrative actions. Usage statistics help us understand and improve the service.
For email verification and password recovery, the application sends your recipient email address, message content and verification or recovery link to Brevo through its HTTPS email API. These are transactional messages. Privacy correspondence sent to the contact address is handled through Gmail.
Cookies and browser storage
Authentication and preferences. The site uses a signed session cookie for sign-in and form security. It is configured as Secure, HttpOnly and SameSite=Lax. Local and session storage remember settings such as theme, sound, sidebar state, navigation position, recent searches and dismissed interface messages, and synchronize sign-in changes between tabs.
Analytics. Separate browser storage supports work-view counting and navigation attribution. Google Analytics and Yandex Metrica can also use cookies and identifiers to measure visits and activity. These analytics functions are distinct from the storage needed for authentication and preferences.
You can clear or restrict cookies and browser storage through your browser, although this can sign you out or affect site features. The analytics initialization code checks whether the browser reports Do Not Track as "1": it skips Metrica's JavaScript initialization and disables Google Analytics measurement in that case. The Google tag can still be requested, and a separate Metrica image request is included when JavaScript is disabled. This is not a guarantee that all third-party requests stop. The site currently has no analytics consent panel or dedicated on-site analytics opt-out.
Analytics and embedded services
Google Analytics. Google Analytics 4 is enabled on selected public pages and eligible public work pages. The application sends a page address without its query string or fragment, a generic page title and an empty referrer field. Account pages and search-query pages are excluded from this integration. Advertising storage and advertising personalization are configured as denied, and Google Signals and automatic interaction detection are disabled. Requests to Google still disclose connection information such as your IP address and browser details and may involve analytics cookies. See Google's Privacy Policy.
Yandex Metrica. Metrica is included on pages using the shared analytics block, including account settings and this policy. Registration, sign-in, email-verification, password-recovery and administration pages suppress that block. Its configuration enables session replay (Webvisor), click maps, link tracking and visit/bounce measurement, and supplies the current page URL and referrer. It can process browser and device information, IP addresses, cookies and information about page interactions. Do not assume that account pages or every URL parameter are excluded. See Yandex's Privacy Policy.
Coub. Works can include related Coub content. The application requests Coub metadata and player information from its servers. Your browser can then load thumbnails, video, audio or embedded content from Coub and its media hosts, disclosing connection information and, where sent by the browser, referrer information. Coub's own privacy terms apply to its services.
Google Fonts. The shared template includes connection hints and a stylesheet link to Google Fonts. The current site security policy blocks the remote stylesheet and font loads, but connection hints may still contact Google's font hosts and disclose connection information.
YouTube. The tutorial page loads a thumbnail from YouTube's image service. Pressing play loads a player from youtube-nocookie.com. These requests disclose connection information to Google/YouTube; the player is not loaded before you press play.
Telegram, Tumblr and Bluesky publishing
Connected automation uses a self-hosted n8n service to send eligible public content to Telegram, Tumblr and Bluesky. Public-work Telegram posts share a preview image, work title and author display name; the automation also receives the original work URL. A separate new-account notification sends the public display name, username, profile link and avatar when available to a configured Telegram destination. Account emails, password hashes and recovery tokens are not part of these social payloads.
Tumblr publishing uploads eligible public MP4 videos, including multiple videos in a work, with the title, author credit linked to the public profile, a link to the original work and cinemagraph-related tags. These integrations check publication eligibility before delivery. Drafts and private works are not eligible for public-work posting.
Bluesky publishing uploads the first supported MP4 video from an eligible public work to Bluesky's video service. The post includes the work title, the author's actual site display name, a short caption, a link to the original work, descriptive alt text based on the title and description, and the video's aspect ratio. An author credit is not treated as a Bluesky account mention. Delivery records retain the remote post identifiers and link for verification and duplicate prevention, including after a work is deleted.
Making a work private or deleting it here does not automatically remove copies already sent to Telegram, Tumblr or Bluesky, downloaded by others, reblogged or cached. Contact us about removal from destinations we control; other services and recipients may retain their own copies. Pinterest is planned and is not currently connected.
Hosting, providers and international processing
The application, PostgreSQL database, uploaded media and n8n automation run on server infrastructure used by the operator. Hosting and infrastructure providers support that processing. Brevo, Google, Yandex, Coub, Telegram, Tumblr and Bluesky receive the information described above when their respective features run.
Information sent to external services is processed on their infrastructure and may be processed outside your country. We do not guarantee that information stays in one country. The hosting provider's identity, exact server and backup locations, and provider-specific retention and international transfer arrangements have not been confirmed for this policy. Contact us if you need those details.
Retention and deletion
Account and content records are stored to support the service. You can edit profile information, remove likes, saves and follows, and delete your own works and comments using the available controls. There is currently no self-service account deletion control: email eleprimer@gmail.com to request account deletion.
Work deletion removes its database record and associated interactions and attempts to delete media and generated previews that are not shared with another work. File cleanup can fail, and replacing or removing media does not establish that every older file has been erased. Deleting a comment with replies clears its text but keeps a placeholder and related thread record.
Security logs, moderation audit records, analytics records and automation delivery records can remain after content changes or deletion. Tumblr and Bluesky delivery records deliberately survive work deletion to prevent duplicate publishing and retain delivery receipts. Temporary generated GIF downloads have an automated cleanup process.
Server logs are rotated, but this does not define retention for all service records. Backup copies and deployment snapshots exist. No single fixed retention period or verified automatic deletion schedule has been established for all accounts, logs, analytics, automation history or backups. Deletion from the live service does not promise immediate erasure from backups or from external services. Contact us about the scope of a deletion request and any retained information.
Privacy requests and your rights
Email eleprimer@gmail.com to ask about your information, request access or a copy, correct it, request deletion, or raise concerns about processing. Include your username and describe the request; do not send your password or recovery token. We may need to verify that you control the account before disclosing or changing private information.
Depending on the law that applies to you, you may also have rights to restrict or object to processing, receive data in a portable format, or complain to a relevant data protection authority. The availability and scope of these rights depend on applicable law and the circumstances. Contact us to discuss your request.
Security
Measures in the current implementation include HTTPS, password hashing, secure session-cookie settings, form request verification, rate limits, server-side access controls and browser security headers. These measures reduce risk, but no website, transmission method or storage system can guarantee absolute security.
Policy updates
We may update this policy as the website and its services change. The current version will be published at cinemagraphs.space/privacy with an updated date. For questions about a change, contact eleprimer@gmail.com.