Cookie Policy

Cookies are small text files stored on a browser or device when a website is visited.

Cookies may be used to:

• maintain a login session;
• remember preferences;
• secure accounts;
• prevent fraud;
• provide checkout functionality;
• measure website use; or
• enable other technical features.

MakerShake may also use similar technologies, including:

• local storage;
• session storage;
• browser databases;
• pixels;
• tags;
• SDKs;
• server-side events;
• consent signals;
• authentication tokens;
• security tokens;
• anti-abuse identifiers; and
• device or browser identifiers.

For simplicity, this policy generally refers to all of these technologies as "cookies."

Some providers described in this policy do not normally place cookies directly in your browser. They are included because their services may be triggered through website features and may process technical or personal data as explained in the Privacy Policy.

Under Section 25 of the German Telecommunications Digital Services Data Protection Act (Telekommunikation-Digitale-Dienste-Datenschutz-Gesetz – TDDDG), storing information on a user's device or accessing information already stored there generally requires consent.

Consent is not required where the storage or access is strictly necessary:

• to carry out the transmission of a communication over a public telecommunications network; or
• to provide a digital service expressly requested by the user.

Where consent is required, MakerShake obtains it before activating the relevant technology.

The subsequent processing of personal data is governed separately by the GDPR. Depending on the purpose, the legal basis may include:

• Article 6(1)(a) GDPR — consent;
• Article 6(1)(b) GDPR — performance of a contract or pre-contractual measures;
• Article 6(1)(c) GDPR — compliance with a legal obligation; or
• Article 6(1)(f) GDPR — legitimate interests.

MakerShake may use cookies and similar technologies to:

• operate and deliver the website;
• register and authenticate users;
• maintain secure login sessions;
• provide account and dashboard features;
• create, edit, and publish project profiles;
• store images and profile settings;
• remember cookie preferences;
• protect accounts and infrastructure;
• prevent spam, fraud, bots, and abuse;
• enforce rate limits;
• provide checkout and subscription functionality;
• manage paid plans and project limits;
• diagnose technical problems;
• measure profile views and outbound clicks;
• provide comments, upvotes, saves, follows, notifications, and maker messaging;
• remember your light or dark mode selection;
• play project videos you choose to start;
• understand website usage after consent; and
• improve MakerShake.

We do not use advertising cookies to sell personal data.

We do not currently intend to use third-party behavioral advertising on MakerShake.

MakerShake may use the following categories of cookies and similar technologies:

1. strictly necessary technologies;
2. consent and preference technologies;
3. security and anti-abuse technologies;
4. functionality technologies;
5. analytics technologies; and
6. payment and checkout technologies.

Optional technologies are not activated until consent has been obtained where consent is required.

Strictly necessary technologies are required for MakerShake to function or to provide a feature expressly requested by the user.

They may be used for:

• account registration;
• authentication;
• login sessions;
• passwordless or email-based login;
• protection against cross-site request forgery;
• secure account access;
• profile creation and editing;
• image uploads;
• saving account and plan settings;
• cookie-preference storage;
• server-side functions;
• rate limiting;
• bot and abuse prevention;
• service stability;
• checkout;
• subscription administration;
• cancellation processes; and
• fraud prevention.

Without these technologies, some requested MakerShake features may not work.

Access to or storage of device information is based on the strictly necessary exception under Section 25(2) TDDDG where applicable.

Related personal-data processing may be based on:

• Article 6(1)(b) GDPR where necessary to provide a requested service; and
• Article 6(1)(f) GDPR where necessary for security, stability, fraud prevention, or reliable operation.

MakerShake uses a consent mechanism to record and respect your cookie choices.

Consent technologies may store:

• whether you accepted or rejected optional technologies;
• which categories you selected;
• the date and time of your choice;
• the policy or consent version displayed;
• whether analytics may be activated;
• whether optional third-party features may be activated; and
• when consent was withdrawn or changed.

This information is necessary to remember and document your choice.

Device storage may be strictly necessary to remember the privacy selection you requested.

The related personal-data processing may be based on:

• Article 6(1)(c) GDPR where required to demonstrate legal compliance; and
• Article 6(1)(f) GDPR for effective and user-friendly consent management.

MakerShake may use cookies, tokens, request data, and similar technologies to:

• detect automated attacks;
• protect login flows;
• prevent account takeover;
• prevent fake or automated account creation;
• reduce spam;
• prevent contact-form abuse;
• enforce rate limits;
• limit how many projects one account can submit per day;
• screen submitted and published project websites for malware, phishing, and deception;
• detect suspicious traffic;
• identify artificial profile views or clicks;
• prevent unauthorized profile claims;
• protect payment processes;
• secure server functions; and
• maintain infrastructure reliability.

Technical information processed for these purposes may include:

• IP address;
• request time;
• browser and device information;
• user agent;
• session information;
• authentication status;
• security events;
• request frequency;
• challenge results; and
• technical identifiers.

The legal basis for personal-data processing is generally Article 6(1)(f) GDPR.

Our legitimate interests are the security and integrity of MakerShake, protection of users and third parties, prevention of fraud and abuse, and reliable service operation.

Automated safety screening does not use cookies

The automated safety screening of submitted and published project websites runs entirely on our servers. It does not store or read any information on your device, does not set cookies, and does not use browser storage, fingerprinting, or tracking pixels.

Screening sends the submitted website address to server-side providers such as a public DNS resolver, public threat feeds, and our AI provider for content classification. No cookie or device identifier is transmitted with those requests. Where an event is recorded without an account, an IP address is stored only as an irreversible hash.

The website being screened may set cookies inside our automated fetching environment. Those cookies belong to that website and never reach your browser.

MakerShake is developed and operated using Lovable.

Lovable may support:

• application hosting and deployment;
• website and application delivery;
• account functionality;
• technical integrations;
• consent implementation;
• server-side features;
• AI Gateway access;
• operational monitoring;
• security; and
• other technical functionality.

Depending on the MakerShake configuration, Lovable-related technologies may be used for:

• session handling;
• authentication;
• application state;
• account and dashboard functionality;
• technical routing;
• consent preferences;
• error handling;
• feature delivery; and
• security.

Possible information processed may include:

• IP address;
• browser and device information;
• session information;
• account identifiers;
• application requests;
• consent choices;
• security information; and
• technical logs.

Lovable-related technologies necessary to provide MakerShake may be used without consent where the requirements of Section 25(2) TDDDG are met.

Related personal-data processing may be based on Article 6(1)(b) or Article 6(1)(f) GDPR.

Optional analytics or tracking technologies provided through Lovable are not activated without consent where consent is legally required.

MakerShake uses Lovable Cloud for backend functionality.

Lovable Cloud provides built-in functionality that may include:

• database storage;
• account authentication;
• file and image storage;
• server functions;
• application APIs;
• security controls;
• access management; and
• technical logs.

Lovable Cloud uses Supabase-based infrastructure for parts of this functionality.

Cookies or local-storage entries may be used to:

• keep a user signed in;
• store authentication or refresh tokens;
• maintain account sessions;
• protect server requests;
• remember application state; and
• provide requested dashboard features.

Depending on the authentication implementation, session information may be stored in cookies, local storage, or another secure browser-storage mechanism.

These technologies are generally necessary to provide account and dashboard functionality requested by the user.

The legal basis for related personal-data processing is generally Article 6(1)(b) GDPR. Article 6(1)(f) GDPR may apply to security and reliable operation.

Cloudflare infrastructure may be used through Lovable for:

• application delivery;
• routing;
• edge processing;
• performance;
• security;
• protection from attacks;
• bot detection; and
• prevention of abusive traffic.

Depending on the activated Cloudflare services and current security conditions, Cloudflare may use strictly necessary cookies or similar technologies to:

• distinguish legitimate visitors from automated traffic;
• conduct security challenges;
• manage traffic;
• apply firewall rules;
• protect forms and login processes; and
• deliver the service reliably.

Cloudflare may process:

• IP addresses;
• HTTP request information;
• browser and device information;
• security events;
• challenge information;
• routing data;
• firewall signals; and
• technical identifiers.

Cloudflare states that the cookies used for its customer security and traffic-management services are generally strictly necessary unless otherwise indicated.

The legal basis for the associated personal-data processing is Article 6(1)(f) GDPR.

Our legitimate interests are secure website delivery, protection from attacks, abuse prevention, and stable operation.

MakerShake may use functionality technologies to remember options selected by a user.

These may include:

• dashboard preferences;
• display preferences;
• profile-editing state;
• draft profile information;
• selected categories or tags;
• interface settings;
• previously selected project;
• upload status; and
• other feature preferences.

Where the technology is necessary to provide a feature explicitly selected by the user, it may fall within the strictly necessary exception under Section 25(2) TDDDG.

Optional convenience or personalization technologies are used only with consent where required.

When you submit a URL to generate an project profile, MakerShake may process the submitted URL through server-side systems and connected service providers.

This operation does not ordinarily require a third-party provider to place a cookie in your browser.

However, MakerShake may use essential session or account technologies to:

• associate the request with your account;
• prevent abuse;
• save generated profile information;
• monitor the request status;
• avoid duplicate submissions; and
• return the generated content to your browser.

Related processing is described in the Privacy Policy.

MakerShake uses ScreenshotOne to create automated screenshots of submitted project websites.

ScreenshotOne does not ordinarily need to place a cookie directly in the browser of a person visiting MakerShake.

When a MakerShake user requests or triggers a screenshot, MakerShake sends information to ScreenshotOne server-to-server. This may include:

• the submitted website URL;
• screenshot configuration;
• viewport settings;
• rendering instructions; and
• technical request information.

ScreenshotOne then loads the submitted project website in an automated browser environment.

The target project website may set its own cookies or similar technologies in ScreenshotOne's automated browser while the screenshot is created. Those technologies are controlled by the target website, not by MakerShake visitors' browsers.

ScreenshotOne is included in this Cookie Policy for transparency, even though its main MakerShake function is server-side screenshot processing rather than browser tracking.

Further information about this processing is provided in the MakerShake Privacy Policy.

MakerShake uses OpenAI models through the Lovable AI Gateway for AI-assisted text generation.

These services may be used to:

• generate project descriptions;
• create taglines;
• generate SEO titles and descriptions;
• suggest categories and tags;
• summarize submitted website content; and
• provide other AI-assisted profile features.

OpenAI and the Lovable AI Gateway do not ordinarily need to set cookies directly in the browser of a visitor using MakerShake.

Requests are generally sent from MakerShake's technical infrastructure to the AI service.

MakerShake may nevertheless use strictly necessary session, security, or account technologies to:

• associate the request with an account;
• protect the API from abuse;
• monitor generation status;
• store generated results; and
• enforce usage or plan limits.

The transmission and processing of content through the AI Gateway and OpenAI are explained in the Privacy Policy.

OpenAI states that API data is not used to train or improve its general models by default unless the customer expressly opts in.

MakerShake uses Resend to send transactional and operational email.

This includes:

• login or authentication emails;
• account notifications;
• project-profile notifications;
• private contact-form messages;
• payment and subscription messages;
• moderation notices;
• support replies; and
• legal communications.

Resend does not ordinarily place cookies directly on the MakerShake website solely because it delivers an email.

Resend may process email-delivery information, such as:

• recipient email address;
• email content;
• delivery status;
• bounce information;
• spam complaints;
• IP and technical delivery data; and
• interaction data if email tracking is enabled.

MakerShake does not enable email-open or link-click tracking unless it is necessary, clearly disclosed, legally permitted, and based on consent where required.

Email processing is described more fully in the Privacy Policy.

Eligible MakerShake profiles may include a private contact form.

Strictly necessary technologies may be used to:

• protect the form from bots and spam;
• maintain the form session;
• enforce submission limits;
• prevent duplicate messages;
• associate the message with the relevant project profile;
• detect fraudulent or malicious activity; and
• confirm successful submission.

Messages may be delivered through Resend.

The form itself does not require analytics or advertising cookies.

Any optional analytics measurement associated with form use is activated only after consent where required.

MakerShake's community features rely on strictly necessary technologies only. No consent-based cookies are used for them.

Strictly necessary storage may be used to:

• keep you signed in so that comments, upvotes, saves, follows, and messages can be attributed to your account;
• remember upvote state in your browser's local storage under the key "makershake-upvotes" so an already-cast upvote is reflected immediately;
• remember when you last shared a project under the key "ms_shared_at" so share counts cannot be inflated by repeated clicks;
• keep bookmark and follow buttons in sync within the current page session;
• enforce rate limits and prevent duplicate or automated actions;
• load and display in-app notification counts; and
• maintain the realtime connection used to deliver new direct messages while a conversation is open.

Local storage entries used for these features remain in your browser until you clear your browser storage or sign out, where applicable. They are first-party and are not used for advertising or cross-site tracking.

Message content itself is stored on the server, not in cookies. How message, comment, save, and follow data is processed is described in the Privacy Policy.

Eligible makers may add one YouTube or Vimeo video URL to a project profile.

MakerShake does not load the external video player automatically. A static preview or poster frame is shown first, and the player is embedded only after you actively start the video.

YouTube videos are embedded through the privacy-enhanced youtube-nocookie.com domain. Vimeo videos are embedded through Vimeo's player domain.

Once you start a video, the video provider may:

• set cookies or use similar storage in your browser;
• receive your IP address;
• receive browser and device information;
• receive the address of the MakerShake page containing the video;
• measure playback events; and
• process information under its own responsibility.

Because the embed is loaded only in response to your action, the storage or access takes place on the basis of your selection. Related personal-data processing may be based on Article 6(1)(a) GDPR or, where the embed is necessary to provide the requested playback, Article 6(1)(b) or Article 6(1)(f) GDPR.

If you do not start a video, no YouTube or Vimeo player is loaded and no provider storage is created by that page.

YouTube is provided by Google. Vimeo is provided by Vimeo. Their own cookie and privacy information applies to the embedded player.

MakerShake stores a small number of first-party preferences in your browser so that the interface behaves the way you selected.

These may include:

• "maker-theme" — your light or dark mode choice, or the instruction to follow your system preference;
• "makershake.cookie-consent.v1" — your cookie selection and the time it was made;
• "makershake:site-settings" — cached public site settings used to render the interface;
• "makershake:pending-app" — a project submission draft or selected plan kept while you complete sign-up;
• "makershake-upvotes" — projects you have already upvoted in this browser;
• "ms_shared_at" — the time of your last share action; and
• "demo-plan" — the plan being previewed when an administrator inspects the dashboard in demo mode.

These entries are first-party, are not shared with advertising networks, and are not used for cross-site tracking.

They are used to provide a function you requested and generally fall within the strictly necessary exception under Section 25(2) TDDDG. You can delete them at any time through your browser settings.

Makers may publish funding-status signals such as "Bootstrapping," "Open to funding," or "Actively raising," and visitors may filter projects by them.

These features are processed server-side and do not require analytics or advertising cookies.

Strictly necessary account and security technologies may be used to attribute a change to your account, apply rate limits, and prevent abuse of investor-oriented discovery features.

Where an eligible maker sees aggregated interest or engagement figures, they are produced from measurement described in the following section.

MakerShake may measure:

• project-profile views;
• clicks on external project links;
• clicks on contact options;
• interactions with work, remix, or funding sections;
• upvotes, shares, saves, and follows; and
• aggregated directory activity.

This measurement may be used to:

• provide analytics to eligible makers, in the depth included in their plan;
• count project-profile engagement;
• filter bots and artificial activity;
• improve search and discovery;
• operate visibility rotation and priority indexing for paid plans;
• prevent click manipulation; and
• diagnose technical problems.

Where possible, essential security and fraud-prevention measurement is separated from optional analytics.

Strictly necessary server-side logging may occur without analytics cookies where required to operate and secure the service.

Where cookies, local identifiers, or comparable technologies are used for optional analytics, they are activated only after consent.

MakerShake uses or intends to use Google Analytics to understand how visitors use the website.

Google Analytics may process:

• cookie identifiers;
• online identifiers;
• browser information;
• device information;
• approximate location;
• page views;
• navigation events;
• referrer information;
• session information;
• interaction events; and
• technical usage data.

Google Analytics is an optional analytics service.

It is activated only after you have provided consent through the MakerShake consent interface, where consent is legally required.

The legal basis for storing or accessing information on your device is your consent under Section 25(1) TDDDG.

The legal basis for the subsequent processing of personal data is Article 6(1)(a) GDPR.

You may refuse or withdraw consent at any time.

Google Consent Mode

MakerShake may use Google Consent Mode to communicate your consent selection to Google tags.

The intended MakerShake configuration is Basic Consent Mode:

• Google Analytics tags remain blocked before a visitor makes a selection;
• no Google Analytics request is sent before analytics consent;
• Google Analytics is loaded only after analytics consent is granted; and
• rejecting analytics prevents Google Analytics from loading.

MakerShake does not intend to use Google Analytics advertising functions, remarketing, personalized advertising, Google Signals, or advertising-personalization features unless they are separately implemented, disclosed, and consented to.

Until Google Analytics is technically active, no Google Analytics cookie is placed merely because this section appears in the Cookie Policy.

MakerShake uses Stripe to provide:

• checkout;
• recurring subscriptions;
• additional project-slot payments;
• payment authentication;
• invoices;
• cancellations;
• refunds;
• payment security; and
• fraud prevention.

When Stripe checkout or Stripe payment components are opened, Stripe may use cookies, local storage, scripts, device signals, or similar technologies to:

• establish a checkout session;
• process a payment;
• authenticate a transaction;
• remember payment-flow state;
• detect and prevent fraud;
• assess payment risk;
• prevent unauthorized transactions;
• meet legal and regulatory obligations; and
• maintain payment security.

Possible information may include:

• IP address;
• browser and device information;
• checkout-session identifier;
• payment status;
• transaction information;
• fraud and risk signals;
• interaction data; and
• technical identifiers.

Technologies strictly necessary to process a payment explicitly requested by the user may be used under Section 25(2) TDDDG.

Associated personal-data processing may be based on:

• Article 6(1)(b) GDPR for payment and contract performance;
• Article 6(1)(c) GDPR for legal and regulatory obligations; and
• Article 6(1)(f) GDPR for payment security and fraud prevention.

Stripe may use additional optional technologies under its own responsibility. Where MakerShake controls activation of non-essential Stripe technologies, they will be used only after consent where legally required.

Stripe states that non-essential cookies are subject to consent or opt-out requirements depending on the relevant jurisdiction.

Until Stripe checkout is activated, no Stripe cookie is placed merely because Stripe is named in this Cookie Policy.

MakerShake may use Stripe-hosted pages or embedded Stripe functionality to allow paid users to:

• view a subscription;
• update payment information;
• download invoices;
• cancel a subscription;
• manage billing information; and
• purchase additional project slots.

Opening a Stripe-hosted portal means that you are interacting directly with Stripe's infrastructure.

Stripe may place necessary checkout, authentication, security, and fraud-prevention technologies in that context.

Stripe's own cookie and privacy information also applies to the Stripe-hosted page.

When a user uploads a screenshot, title image, logo, or other file, MakerShake may use essential browser-storage or session technology to:

• maintain upload progress;
• associate the upload with an account;
• prevent unauthorized uploads;
• validate the file;
• recover from upload errors; and
• display the uploaded file.

These technologies are used only to provide the requested upload functionality and maintain security.

The following providers are primarily used through server-to-server requests and do not ordinarily need to place cookies directly in a visitor's browser:

• ScreenshotOne;
• OpenAI;
• the Lovable AI Gateway; and
• Resend.

Their inclusion in this policy does not mean that each provider sets a browser cookie on MakerShake.

They are included because their services process information when a user activates a related feature.

Details of those processing activities are provided in the Privacy Policy.

The duration of a cookie or similar technology depends on its purpose and technical configuration.

Possible durations include:

Session technologies

These may be deleted when:

• you close the browser;
• the session ends;
• you log out; or
• a short technical period expires.

Authentication technologies

These may remain until:

• the session expires;
• the refresh period ends;
• you log out;
• your account is secured or reset; or
• the technology is manually deleted.

Security technologies

These may remain only for the duration of a challenge or for a limited period necessary to recognize a previously validated or suspicious request.

Consent technologies

These may be stored for a longer period so that MakerShake can remember and document your choice.

MakerShake intends to request renewed consent after an appropriate period or when the consent configuration materially changes.

Google Analytics technologies

These are retained according to the configured Google Analytics settings and your consent.

Interface and preference storage

Local-storage entries such as your theme choice, consent selection, upvote state, or submission draft remain until you clear your browser storage or the entry is replaced.

Video-player technologies

These are set by YouTube or Vimeo once you start a video and are retained according to that provider's own configuration.

Stripe technologies

These are retained according to Stripe's checkout, security, fraud-prevention, and legal requirements.

Specific cookie names and durations may change when providers update their services or MakerShake changes its configuration.

The current consent interface should display the cookies and technologies detected in the live MakerShake implementation.

The inventory below reflects MakerShake's current technical implementation.

Strictly necessary (always active)

• Lovable Cloud authentication and session storage (keeps you signed in);
• "makershake.cookie-consent.v1" — your cookie selection;
• "maker-theme" — light or dark mode;
• "makershake:site-settings" — cached public interface settings;
• "makershake:pending-app" — submission draft or selected plan during sign-up;
• "makershake-upvotes" — upvotes already cast in this browser;
• "ms_shared_at" — last share action, used against inflated share counts;
• "demo-plan" — plan preview in administrator demo mode;
• Cloudflare security and bot-protection technologies; and
• Lovable application-operation technologies.

Only after consent

• Google Analytics measurement technologies, where analytics consent is granted.

Only after you start a video

• YouTube (youtube-nocookie.com) player technologies; and
• Vimeo player technologies.

Only during payment

• Stripe checkout, portal, authentication, and fraud-prevention technologies, when you open a payment or billing flow.

The cookie or consent interface should identify, where technically available:

• cookie or storage name;
• provider;
• purpose;
• category;
• duration;
• whether it is a first-party or third-party technology; and
• whether consent is required.

Exact provider cookie names for authentication, Cloudflare, Google Analytics, and Stripe are set by those providers and may change when they update their services.

You may change your cookie settings or withdraw consent at any time through the MakerShake cookie settings.

A permanent "Cookie settings" or comparable link should remain accessible in the website footer.

Withdrawing consent:

• applies for the future;
• prevents optional technologies from being activated again;
• does not affect processing that occurred lawfully before withdrawal; and
• does not automatically delete information already received by a provider.

Where technically possible, MakerShake will also remove or expire optional first-party identifiers after consent is withdrawn.

The MakerShake consent interface should provide options to:

• accept all optional technologies;
• reject all optional technologies; and
• manage individual categories.

Rejecting optional technologies must be as easy as accepting them.

The website's essential features should remain available without analytics consent, except where a feature genuinely requires a specific technology to provide a service requested by the user.

Most browsers allow you to:

• view stored cookies;
• delete cookies;
• block cookies;
• restrict third-party cookies;
• clear local storage;
• delete site data; and
• control tracking protection.

These options are usually found under privacy, security, or website settings.

Blocking all cookies or browser storage may prevent or limit:

• registration;
• login;
• authentication;
• account dashboards;
• profile editing;
• image uploads;
• consent preferences;
• Stripe checkout;
• payment management;
• subscription cancellation;
• security checks; and
• other requested features.

MakerShake profiles contain links to independent third-party apps and websites.

When you leave MakerShake, the destination website may use its own:

• cookies;
• pixels;
• analytics tools;
• advertising technologies;
• login systems;
• payment technologies; and
• other tracking methods.

MakerShake does not control the cookies or tracking practices of listed third-party products.

You should review the destination website's own cookie and privacy information.

MakerShake does not automatically load non-essential embedded third-party content.

Project videos from YouTube and Vimeo are loaded only after you start playback, as described in the section on project video embeds.

If MakerShake later embeds content such as:

• social-media posts;
• interactive maps;
• external widgets; or
• third-party review tools,

that content may allow the external provider to set cookies or receive technical information.

Such content will be blocked until consent or an equivalent user action where consent is legally required.

Some browsers transmit "Do Not Track," Global Privacy Control, or similar privacy signals.

There is not yet one universally applicable technical standard for every such signal.

MakerShake may recognize supported consent and privacy signals where technically feasible and legally appropriate.

Your selections in the MakerShake consent interface remain the primary method for controlling optional technologies on MakerShake.

The technologies used by MakerShake may change as the service develops.

Providers may also change:

• cookie names;
• storage methods;
• retention periods;
• technical purposes;
• subprocessors; or
• browser behavior.

MakerShake will update this Cookie Policy, its Privacy Policy, and the consent interface where necessary.

A service provider will not be treated as active merely because it is named as planned processing. The live consent interface should reflect only technologies currently capable of operating on MakerShake.

This Cookie Policy focuses on storage and access technologies used on devices.

The MakerShake Privacy Policy provides additional information about:

• data categories;
• processing purposes;
• legal bases;
• recipients;
• international transfers;
• retention;
• user rights;
• URL scanning;
• AI generation;
• screenshot generation;
• email delivery;
• payments; and
• public profiles.

The two policies should be read together.

We may update this Cookie Policy if:

• new features are introduced;
• providers change;
• Stripe or Google Analytics is activated;
• authentication or storage methods change;
• legal requirements change;
• consent technology changes; or
• security practices are updated.

The current version will be published with a revised "Last updated" date.

Where required, users will be asked to make a new consent selection following a material change.

For questions about this Cookie Policy or the processing of personal data, contact:

DOMU.STUDIO

Dominic Müller

Mainzer Straße 19

50678 Cologne

Germany

Email: contact@domu.studio