Dslop
RedesignCreate a flyerProduct photosPricingLog inTry for free

LEGAL

Privacy notice

What we process, why, on what basis, who receives it and how long it stays.

Read this page in German

1. Controller and contact

The controller for our own processing described here is Sydney Rüger, trading as Rüger Solutions, a sole proprietor operating Dslop, Bergheimer Weg 24, 70839 Gerlingen, Germany.

Privacy and general contact: contact@dslop.app. Support: support@dslop.app. Telephone: +49 157 51178898. Website: https://dslop.app.

This notice covers the website, accounts, design features and our communications. It also explains the intended payment route where purchases are actually offered. A privacy notice is not consent and does not replace a required data processing agreement.

2. Data and purposes

Website delivery and security

Access involves processing IP addresses, timestamps, requested addresses, technical browser/connection information and status/security information. We need this for delivery, secure operation, attack detection and restricting abusive access. Cloudflare provides hosting, network and security services.

The basis is Article 6(1)(f) GDPR. Our legitimate interests are a functioning, secure service, account protection and preventing unauthorised or cost-generating access. Where processing is directly necessary for the contractual service you request, Article 6(1)(b) applies.

Visitor counting without cookies

To understand how many people visit Dslop and where they drop off, our server counts page requests itself when a page is requested. We use no script and no cookie for this and read nothing from your device. We store only daily totals: the page, the referring page (domain only), the country (derived from the IP address) and the device type (phone, tablet or computer, from the browser string). To count each visitor once per day, we form a hash of the IP address and browser string with a secret key that changes daily and delete it after at most two days. We do not store the IP address itself for this, and nobody can be recognised across days. We also count individual steps as daily totals, for example whether text was recognised in the studio without an account or a sign-in code was requested.

The legal basis is Article 6(1)(f). Our legitimate interest is measuring the reach and user journey of our service in order to improve it.

Registration and login

We process email addresses, names where entered, account identifiers, invitation/approval details, account and permission status, and registration/login timestamps. Passwords are processed for authentication and stored as salted hashes, not readable password text. Session information links a login to an account. Abuse controls also process IP-related login or registration attempts and timestamps.

Creating and operating your own account relies on Article 6(1)(b). For a business customer's contact persons and additional necessary security measures, we rely on Article 6(1)(f), with legitimate interests in proper business communication and service protection. Where verified Cloudflare Access is used, its identity and access assertions are also processed.

Sign-in with an email code: You can sign in without a password. We send a six-digit code to your email address and store only a hash of it, for at most ten minutes and at most five attempts. The correct code also confirms your email address and creates your account on first sign-in.

Sign-in with Google: If you choose “Continue with Google”, we redirect you to Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). After you agree there, Google sends us your email address, whether Google has verified it, a Google account identifier, and your name and profile picture. We store only the email address and the identifier to match your Dslop account; we do not store the name or picture. We get no access to other data in your Google account. Google explains its processing in the Google Privacy Policy. The legal basis is Article 6(1)(b).

An email address and credentials are required for account-based functions; without them we cannot provide the account. Optional details are identified in the relevant form. An invitation does not oblige you to register.

Trying the studio without an account

In the studio you can upload a poster, have its text recognised and use copy suggestions before creating an account; creating an image needs an account. Your uploaded image and your entries stay in your browser (see section 8). For text recognition and copy suggestions we send them to OpenAI (see section 4) but do not store them on our servers. To limit abusive and costly use, we count requests per connection and store only a keyed hash of the IP address for at most two days. If you then create an account, we move your draft from the browser into your account and delete it from the browser.

The legal basis is Article 6(1)(b) (steps taken at your request before entering into a contract) and, for abuse limits, Article 6(1)(f); our legitimate interest is protection against costly misuse.

Projects, images, text and design jobs

We process submitted source images, logos, motif images, text, brand/design instructions and QR content or destinations. This includes confirmed or edited text, generated results, job/project identifiers, review notes, states, timestamps and necessary usage/cost information. Filenames and image metadata may also identify people. Inputs and outputs are stored for processing and project functions, not processed solely transiently in your browser.

Article 6(1)(b) applies where processing is necessary for your own ordered service. Where we process a business customer's personal content solely on its instructions, the required Article 28 agreement governs that processing; the customer remains responsible for its purposes and legal bases. Article 28 is not a separate legal basis for arbitrary use of content. Additional use for our own purposes requires a separate assessment and basis.

The Terms' content restrictions apply to this version. Do not upload identity documents, sensitive personal information, images of identifiable people or uncleared confidential records. Personal business information is accepted only through a processing route expressly approved for it. A public name, sole trader's address or personal business email can still be personal data.

Usage and accounting

We record job states, model/provider identifiers, available token or cost information and applicable credit entries. Purposes include executing and allocating jobs, calculating allowances, troubleshooting and preventing double charges. Bases are Article 6(1)(b) or (f), and, for mandatory records, Article 6(1)(c) together with the relevant tax or commercial-law obligations.

An internal dashboard accessible only to the operator evaluates registrations, successful password logins, starter-credit claims, generations, top-ups, refunds, balances and costs. It uses our own account and billing records, sets no additional analytics cookie and loads no external tracking service. Individual successful logins are recorded with an account identifier and timestamp and deleted after 180 days. Other records follow the applicable account, contract and retention rules. The purpose is operating the service sustainably and securely, including capacity and cost planning; Article 6(1)(f) is the basis where contract performance or a legal duty does not apply.

If you use the online withdrawal function, we record your name, confirmation email, details identifying the contract, the time and handling status of your declaration, and whether the receipt confirmation was sent. We process this to handle and evidence the withdrawal under Article 6(1)(b) and (c) GDPR. The declaration does not itself trigger an automatic refund; the affected purchase is reviewed separately.

3. Hosting and storage

The application uses Cloudflare Workers for execution and delivery, Cloudflare D1 for structured account, project, job and related data, and Cloudflare R2 for uploaded and generated image files. Private project files are delivered through access-restricted application routes; a general public gallery of customer images is not part of this offer.

The reviewed R2 configuration specifies EU jurisdiction. This does not mean all processing is confined to the EU: Worker execution, network/security information, D1, communications and AI providers are separate processing steps. See section 7 for specific recipient and transfer information.

4. AI processing by OpenAI and Higgsfield

For content recognition, copy work and design we use two AI providers: OpenAI and Higgsfield Inc., a company based in the United States.

What goes to OpenAI: the source image you upload, for content recognition, together with text and design details for copy editing and for reviewing the result. Our access is configured so that these inputs are not stored there. That is not a promise of complete non-retention: the provider's own security and abuse logs are unaffected by it.

Voice input: if you speak your idea, the recording is sent to OpenAI to turn it into text. We do not store the recording itself, only the recognized text in your draft. The storage setting described above does not apply to this conversion; OpenAI may retain the recording temporarily under its own rules for security and abuse detection. Voice input is optional; you can always type your idea instead.

What goes to Higgsfield: the design brief assembled from your confirmed content, technical format settings, and approved logo or motif references. We do not transmit your uploaded source image to Higgsfield; text taken from it may nevertheless form part of the request. Image references are made available through retrieval addresses that are valid for a limited time. When such an address expires, that does not delete a copy already transferred.

Recipients beyond Higgsfield: by its own account, Higgsfield performs generation using a combination of its own and third-party AI models, including models from OpenAI, and counts third-party providers of AI models and compute among its service providers. The brief and image references may therefore also reach those providers. Content moderation runs at model level and covers the request, the references and the result. The configuration of our own OpenAI access does not apply to that route — there, the agreements between Higgsfield and its providers apply, over which we have no influence.

Role and further use: in its own privacy policy, Higgsfield describes itself as the controller under the GDPR. Unless a separate agreement with a different allocation of roles applies to our account, Higgsfield also processes the transmitted content for its own purposes rather than solely on our instructions. As published on 26 July 2026, the provider's terms provide for further use of submitted content to improve its own services. We cannot currently rule out such further use. We have raised the point with the provider; it is not conclusively resolved, and we will update this passage once it is.

Transfers to third countries are possible with both providers. The safeguards that apply are set out in section 7.

So do not upload content whose further use by third parties would be unacceptable to you, in particular no images of identifiable individuals and no confidential records.

Accepting our Terms grants no general right to train, publish or advertise with your content. This purpose limitation must also match the provider agreements actually in force. Confirming your rights at upload is not blanket consent from other affected individuals and does not replace that contractual review.

5. Access by authorised people

Authorised people may access the account, input, project and output data needed for your support request, necessary troubleshooting, security incidents or legal obligations. Depending on the purpose, the basis is Article 6(1)(b), (f) or (c). Our legitimate interests include resolving problems, secure operation and asserting or defending specific legal claims. Access must be limited to the particular need.

Beta information: In the currently documented beta, administrators can view source images, inputs and outputs across accounts in an internal results overview. Technical visibility does not mean every review is lawful. Account creation, this notice and the Terms do not authorise general manual review for product improvement or advertising. Any separately offered use must have a separately stated basis; voluntary consent must be capable of refusal without disadvantages to other use and withdrawal for the future.

6. Communications and payment

Email and support

When you contact us, we process sender/contact details, message content, necessary attachments, technical delivery information and handling history. We use them to respond, administer contracts and handle complaints or claims. Article 6(1)(b) applies to your own pre-contractual or contractual requests, otherwise Article 6(1)(f) supports appropriate communication; statutory documentation may rely on Article 6(1)(c).

Incoming messages to our business addresses, such as contact@dslop.app and support@dslop.app, are received by Cloudflare Email Routing and forwarded to the Rüger Solutions business mailbox at IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, Germany, where they are stored and read by us. We send replies from the business address through Cloudflare Email Sending or from the IONOS mailbox. Both providers thereby process sender, recipient, subject, content, attachments and technical delivery information.

IONOS stores the mailbox as our processor; the data processing agreement under Article 28 GDPR is part of its contract terms, and processing takes place in the EU. With Cloudflare, processing outside the European Economic Area is possible (see section 7). Emails are not end-to-end encrypted. Accordingly, please do not email us special categories of personal data under Article 9 GDPR or complete customer datasets. For confidential matters, agree a different route with us.

Stripe, where paid purchases are offered

A purchase handled by Stripe involves data required for the order and payment, including contact and billing details, amount, currency, order/transaction identifiers and payment status. Stripe processes payment details in its payment flow. We receive information necessary for allocation, contract performance, refunds and records, not automatically every card detail entered.

Our bases are Article 6(1)(b) for performance, Article 6(1)(c) for mandatory records and Article 6(1)(f) for necessary fraud prevention or claims. Stripe may act as an independent controller for its own payment, regulatory, security or fraud-prevention purposes; not all processing is on our instructions. For an order using Stripe Managed Payments, Sold through Link, LLC is the merchant of record for the transaction and provides payment receipts. Sandbox test payments move no real money, but order and contact details can still be processed in Stripe's test environment.

7. Recipients and international transfers

Recipients include the hosting/security, AI, email and applicable payment providers involved in each step, and, where necessary, professionally confidential advisers and competent authorities. Access must be limited to what their tasks require and supported by a suitable basis.

Processing outside the European Economic Area may occur depending on the provider and product. An Article 6 basis does not replace the additional requirements of Articles 44 et seq. Where applicable, safeguards may be an actually applicable adequacy decision or agreed standard contractual clauses with necessary additional measures. These are not alternatives assumed automatically to have been satisfied.

Outside AI processing we use the following in detail:

  • Cloudflare for execution (Workers), structured data (D1), files (R2) and network and security functions. R2 storage is set to the EU jurisdiction. That setting does not apply to Workers execution, D1 or network/security processing, where processing outside the European Economic Area may take place. What governs is the data processing addendum applicable to our account, including the standard contractual clauses agreed in it and the sub-processor list maintained under it.
  • IONOS for the business mailbox, see section 6.
  • Google only if you choose it, for sign-in with Google, see section 2.
  • Stripe for hosted Checkout, payment and test-transaction data and, where applicable, invoices, fraud prevention and refunds. For Managed Payments transactions, Sold through Link, LLC is the merchant of record. Checkout indicates whether an order uses test or live mode and whether Managed Payments applies. Stripe explains its own data processing in its Privacy Policy.

There are no other recipients. We use no external analytics, tracking or advertising services; the internal use of our own account and billing records is described above. To protect registration and sign-in from bots, the page loads Cloudflare Turnstile from challenges.cloudflare.com; Cloudflare processes technical browser and environment signals for that purpose. Fonts are hosted on our own domain. We currently use no other external embeds.

Read this together with the specific AI and email information. You may request information or a copy of relevant safeguards at contact@dslop.app, subject to permitted protection of confidential information. Ordinary website use is not consent to arbitrary international transfers.

8. Cookies and local browser data

HTTPS login uses __Host-dlop_session, which associates the session with the account. It is not readable by scripts and is set with Secure, HttpOnly and SameSite=Lax. Its configured maximum lifetime is 30 days; logout or session revocation may end access sooner. During a Google sign-in we also set __Host-dlop_oauth with the same protections for at most 10 minutes; it only holds random values that secure the return from Google and is deleted afterwards. Cookie lifetime is not automatically a deletion period for all server records.

The studio also uses local browser data; each item is listed below. Browser data is separate from server-side projects: clearing it does not automatically delete server projects. An actually used Access or payment service may introduce additional functional storage, which we would then add here.

Access strictly necessary for the expressly requested function falls under section 25(2)(2) TDDDG. Further processing of personal data also needs a GDPR basis. Storage or access that is not strictly necessary must not merely be labelled necessary; any required prior consent must be obtained. Preselected options must not circumvent refusal or subsequent withdrawal.

Beyond the above, the studio uses the following local browser storage. It stays on your device, is not transmitted to us and is not used to recognise you across websites:

KeyLocationContent and purposeDuration
dlop.generative-v2.brandLocal storageOnly if you choose to save a brand: stored brand profile with colours and, where applicable, a logoUntil you delete it in the studio or clear your browser data
dlop.ui-preview.v1Local storageOnly if you choose to save: local drafts and stored brandUntil you delete them in the studio or clear your browser data
dlop.current-projectLocal storageIdentifier of the most recently opened project so the studio resumes thereUntil you switch project or clear your browser data
deslop-project-idLocal storageOlder project identifier serving the same functionUntil you clear your browser data
dlop.pending-job.v2Session storageRunning generation job, so a reload does not lose itEnds when you close the browser tab
dslop-guestIndexedDBWhen trying the studio without an account: your draft with images, text and settings, so it can move into your account after sign-inUntil it moves into your account; the studio discards drafts older than 7 days; or until you clear your browser data

All of these serve the function you expressly requested and fall under section 25(2)(2) TDDDG; no consent is required for them. The two brand stores additionally require your deliberate choice and can be deleted again in the studio. Optional ad measurement below requires your prior consent. Declining and allowing are equally easy; Dslop remains available if you decline.

Optional ChatGPT ad measurement

If you arrive through our ChatGPT ad, we separately ask whether we may measure its effectiveness. Only after you select “Allow” do we set a random identifier in __Host-dslop_ads and load the OpenAI Measurement Pixel. Dslop links that ad visit with a subsequently created, verified account and completed paid purchases. This association and cookie expire after 30 days. Existing accounts and internal tests are not new customers. Without consent, neither this cookie nor the OpenAI Pixel is used for this purpose.

OpenAI receives page views, verified registrations and completed purchases with amounts and currency, plus random event and browser identifiers. Connecting also exposes the IP address and browser user agent as a technical necessity. The SDK processes the ad click reference oppref and the source domain. We do not pass names, email addresses, account numbers, uploaded photos, prompts or designs. Automatic advanced customer matching is not enabled for this setup. Events opt out of future user-level ad personalization (opt_out).

The Pixel uses __oppref for up to 30 days and __obref for up to 365 days. Local Storage holds your choice under dslop.ads-choice.v1 and previously reported random event identifiers under dslop.ads-sent.v1, each for no more than 30 days. Refusal is remembered only so we do not repeatedly ask. Our own report covers consenting visits only and therefore does not represent all customers.

The legal basis is Article 6(1)(a) GDPR and, for relevant device access, section 25(1) TDDDG. You may decline or withdraw just as easily through “Privacy choices” on the website. Further reports stop, Pixel cookies are removed and our ad association is deleted. Withdrawal applies going forward; it does not automatically recall events already sent to OpenAI. Contact us for access or erasure requests.

OpenAI generally processes conversion data as an independent controller under its Conversion Terms, Ad Tools Data Processing Addendum and Privacy Policy. Those sources cover international transfers, recipients, rights and OpenAI retention. Cookie lifetimes do not promise a corresponding server-side deletion period at OpenAI.

9. Retention and deletion

CategoryPeriod or determining criterion
Account data and password hashFor the existing account; after termination only as needed for settlement, legal retention or specific claims.
Session dataFor access until expiry or revocation; for how expired server records are handled, see the security data entry in this table.
Projects, inputs, intermediate files and outputsWe do not delete projects, uploads, intermediate files or outputs automatically after a period of time; they remain available and downloadable for as long as your account exists. There is therefore currently no 30-day deletion and no other expiry period. You can request deletion at any time. If your account ends, we remove the content as part of account termination; secure anything you wish to keep beforehand. Any automatic period introduced later will be announced in advance and will not be applied retroactively to existing content; content retention and download availability must be distinguished from credit balance.
Security, access and authentication logsIn detail:
  • Session records in D1 carry an expiry of 30 days from creation. They are deleted once an expired session is accessed again, and also on sign-out, on a password change for all other sessions, and on a deletion request for all sessions of the account. Independently of that, an automatic run removes expired records at the latest 24 hours after expiry, even if the session is never accessed again.
  • Sign-in, registration and online withdrawal attempts are recorded for abuse limitation with a timestamp and a reference to the IP address, or to the email address for sign-in. Only a short window is evaluated: 15 minutes for sign-in and one hour for registration and online withdrawal. An automatic run deletes these entries after 24 hours. The margin over the evaluated window only ensures that a running period is not cut short mid-evaluation.
  • Backups are provided by Cloudflare for the services used. Deletion in live data does not take effect immediately in every backup copy; such copies are overwritten on their own cycle and are not evaluated for other purposes.
  • Data required for a specific security incident may additionally be retained, purpose-limited, for as long as investigating the incident or pursuing or defending claims requires.; data needed for a specific incident may require longer purpose-limited retention. |

| Job, credit and payment evidence | As needed for performance, traceability and claims; mandatory records for their applicable statutory periods. Accounting duties do not justify retaining every customer image for the same period. |
| Support messages | Until the request is resolved, and afterwards only where needed for the contractual matter, statutory documentation or a specific claim. |
| Provider copies and backups | The periods applied by each provider, see section 7; link expiry or account suspension is not complete deletion. |

You may request deletion at contact@dslop.app. The currently documented account function records a deletion request and revokes sessions; it does not establish that all D1, R2, provider and backup data are deleted immediately. Remaining deletion must be handled according to the request, applicable rights and permitted retention. A limited retention ground does not authorise new general use of the content.

10. Your rights

Subject to applicable conditions, you have rights of access, correction, erasure, restriction and data portability. You may withdraw consent at any time for the future without affecting the lawfulness of earlier processing.

Objection: You may object to processing based on Article 6(1)(e) or (f) on grounds relating to your particular situation. You may object to direct marketing, including related profiling, at any time without giving a reason.

Contact contact@dslop.app. Reasonable identity checks may be needed to prevent unauthorised disclosure, but we do not routinely require a complete identity-document copy. We generally inform you of action on a rights request within one month; permitted extensions are notified and explained. This is not a blanket promise that every category is retained for exactly one month or deleted only then.

You may complain to a supervisory authority, particularly where you habitually reside, work or believe an infringement occurred. In Baden-Württemberg, this includes the State Commissioner for Data Protection and Freedom of Information: https://www.baden-wuerttemberg.datenschutz.de/.

11. Other people's data and automated decisions

We mainly obtain data from you and technical use of the service. Customer content or correspondence may contain information about others. Depending on the matter, affected people may include customers, business contacts, people named in content and correspondents. Where we act as controller, applicable indirect-collection information duties also apply; a customer confirmation does not automatically replace them.

The design functions described here do not make solely automated decisions producing legal or similarly significant effects within Article 22 GDPR. AI generation is not by itself such a decision. You may ask for human review of security restrictions or disputed account measures. Introducing relevant profiling or decision processes later requires separate information and assessment.

12. Changes

We update this information for actual processing changes and legal requirements. Material changes are communicated appropriately. An updated notice creates no retrospective consent and does not replace a required new legal basis.

---

Dslop · AI-powered design with approved content.
Redesign flyers & postersImprove an AI posterCreate flyers & postersRestaurant flyersAI product photos
Legal noticePrivacyTermsWithdrawalCancel contracts here