Rasterless

Privacy Policy

Effective 15 November 2026 · version 1.3

Language. This English text is the authoritative version. We publish it in Türkçe, Deutsch, Nederlands, Polski, Português (Brasil) and Español so that you can read it in the language you use the site in. Those translations are provided for your convenience; if a translation and this English text disagree, this English text governs. That does not take away the protection of the mandatory consumer and data protection rules of the country where you live. You may write to us in any of those languages and we will answer in the same one.

The short version

rasterless.com converts raster images (PNG, JPEG, WEBP, BMP, GIF, AVIF) into vector files (SVG, PDF, EPS, DXF, PNG). It is free.

Three things worth knowing before anything else:

  1. We do not train anything on your images. The conversion uses machine learning (AI), but your images are never used as training data. Not now, not later.
  2. You can convert and preview without an account. You only need to sign in with Google to download a file.
  3. Your files do not stay with us. Uploads and results are removed by a retention policy shortly after the job runs.

1. Who is responsible for your data

The controller is the individual founder who operates rasterless.com, established in the Netherlands. Write to [email protected] for anything in this policy, including any request under the rights described in section 5.

We are a one-person operation and not yet an incorporated company, so there is no trade register entry or registered office to give you. A Dutch private limited company (*besloten vennootschap*) is being formed. When it is registered this page will name it, together with its KvK number, its VAT number and its registered address, and it will take over as controller. Until then [email protected] is the address of record and it is read by the controller personally.

We have not appointed a data protection officer. Our processing is not of a kind that requires one under Art. 37 GDPR: we carry out no large-scale systematic monitoring and process no special-category data at scale.

We have not appointed a representative in the EU under Art. 27 GDPR either, and we do not need one: that obligation applies to controllers established *outside* the EU, and we are established in the Netherlands.

Because we offer the service in Turkish to people in Türkiye, Turkish data protection law (KVKK, Law No. 6698) is also relevant to us. The Turkish version of this page is written to meet the disclosure duty that law imposes, and it is the version that governs for KVKK purposes.

2. What we process, why, and on what legal basis

WhatWhyLawful basis (GDPR Art. 6)How long
The image you upload, and the vector file we produce from itTo run the conversion you asked for and give you the resultArt. 6(1)(b) — performance of a contract, and steps taken at your request before entering into oneObjects in storage carry a one-day lifecycle rule and are removed by it
Job record (job status, format, size, timing)To track your conversion from upload to downloadArt. 6(1)(b)Becomes invalid after 65 minutes and is deleted automatically, which can take up to a day
Your IP addressAnonymous rate limiting — 10 conversions per hour without an account. Rate limiting is also what keeps automated abuse in check; we run no separate bot-screening product todayArt. 6(1)(f) — our legitimate interest in keeping a free service available and not being overwhelmed by automated abuseWe do not store the address itself. We store a keyed hash of it (HMAC-SHA256 with a secret key only we hold) as the key of a rate-limit counter. The hash is still personal data, because we hold the key. The counter expires after 2 hours and is then deleted automatically, which can take up to a day. Not written into our telemetry
Your Google account identifier and email address, via Google sign-inTo let you download files, and to apply the signed-in quota (60 per hour, 300 per day)Art. 6(1)(b)For as long as your account exists
Technical telemetryTo see that the service is working and to fix it when it is notArt. 6(1)(f) — our legitimate interest in operating a reliable service30 days
Request logs, kept automatically by Google Cloud Run: time, address requested, browser type (user agent) and referring page. A request that reaches us through our network edge is logged with the edge's address, not yours; a request sent to the service's direct address, bypassing our network edge, is logged with the sender's IP addressTo operate the service and to see attempts to bypass our network edgeArt. 6(1)(f) — our legitimate interest in operating and securing the service30 days
Records of copyright notices and strikes against an accountTo apply the repeat-infringer rule in the Copyright and Takedown Policy consistentlyArt. 6(1)(c) — a legal obligation to act on notices, and Art. 6(1)(f) — our legitimate interest in applying our own policy fairlyFor as long as the account exists, and 12 months after
theme and lang on your own deviceTo remember the appearance and language you choseArt. 6(1)(f) — our legitimate interest in the site behaving the way you left it. Stored on your device only; we never receive themUntil you clear site data

Our own telemetry contains no personal data — not even a hashed IP address. That was a deliberate decision, and we intend to keep it. Google Cloud Run's request logs are separate; see the "Request logs" row above for what they contain.

Filenames. We do not store your filename on our servers. The name you want the download to have travels in the request header for that one request, and is not kept.

Limits. Uploads are capped at 25 MB and 40 megapixels. Images over 1.5 megapixels are downscaled before tracing.

How the conversion runs. The conversion is automated and combines geometric tracing with machine learning (AI). The machine-learning part runs on our own infrastructure (Google Cloud Run, see section 3); no third-party AI service receives your image.

2a. API keys and API requests

This section concerns you if you use the API or the MCP server described in section 5a of the Terms of Service. Section 2 applies to those requests too; the table below adds what is specific to them.

WhatWhyLawful basis (GDPR Art. 6)How long
Your API key record: a keyed hash of the key, the four characters after its fixed prefix and its last four characters, the Google account the key belongs to, when it was created and last used, and whether it has been revokedTo recognise whose request reaches the API or the MCP server, to apply that key's quota, to list your keys on the developers page, and to suspend or revoke a key when neededArt. 6(1)(b)As long as your account exists; a revoked key stays in the record, marked as revoked. When your account is deleted, its key records are deleted within 30 days
Usage counters for each keyTo apply the per-key quota and to show it at GET /v1/account and on the developers pageArt. 6(1)(b)The hourly counter expires after 2 hours and the daily counter after 48 hours; each is then deleted automatically, which can take up to a day
The image you send through the API or the MCP server, or that the MCP server downloads from a link you give it; the files we produce from it; and the job recordAs on the site: to run the conversion you asked for and return the result to the program that sent the requestArt. 6(1)(b) — performance of a contractAs in section 2: objects in storage carry a one-day lifecycle rule and are removed by it, and the job record becomes invalid after 65 minutes and is deleted automatically, which can take up to a day. The signed download links in a response expire after 1 hour
Request logs for API and MCP requests, kept automatically by Google Cloud Run in the same way as in the "Request logs" row of section 2. A program sends these requests, not a browser page: there is no referring page, and the user-agent field names the program if it sends oneTo operate the service and to secure itArt. 6(1)(f) — our legitimate interest in operating and securing the service30 days

Your key. We never store or log the key itself. In Firestore, listed in section 3, we keep a keyed hash of it (HMAC-SHA256 with a secret key kept on the server), together with the four characters after rl_live_ and the last four, so that you can tell your keys apart. Each key belongs to the Google account that created it on the developers page, and an account can have up to 2 active keys at a time. You can revoke a key there, and it stops working from the next request. If we suspend or revoke one of your keys, the developers page shows it, and we tell you by writing to the email address of that Google account.

AI clients. If you use the MCP server through an AI client (an assistant, editor or command-line tool that supports remote MCP servers), the company behind that client is not one of our providers in section 3. It processes your prompts, the files you give it and the results it receives under its own terms and its own privacy policy, and we are not responsible for that processing. We receive the request the client sends us (and, if the request gives a link, the image at that link) and nothing beyond it, and we send the result back to that client, because that is where you asked for it to go. Some clients connect from their company's cloud, not from your machine: a Claude custom connector, for example, reaches us from Anthropic's cloud, so the IP address of those requests is Anthropic's. This does not change how the conversion runs (section 2): no third-party AI service takes part in it, and the client is simply where the image comes from and where the result goes, because you chose it.

California. For section 8, the API key record belongs to the "identifiers" category, next to your Google account email and user identifier.

3. Who else sees your data

We use these providers to run the service. We do not sell your data, we do not show advertising, and we use no third-party analytics beyond what is listed here.

That is the complete list of providers. We disclose your data to no one else, with one exception you should know about in advance: if someone sends us a copyright notice about a file you uploaded, we forward the substance of that notice to you, and if you send us a counter-notice we forward its substance to them. That is how a notice-and-action procedure works — you cannot answer a complaint you have not seen. We redact the other side's postal address and telephone number by default; we cannot redact their identity, because you need it to respond. The legal basis is Art. 6(1)(c) and Art. 6(1)(f). Beyond that, we disclose your data to no one unless the law requires it.

4. International transfers

Our conversion service runs in the EU (europe-west1). Some of the providers above are established outside the EU and may process data outside it.

For each provider above that is established outside the EU, we rely on the standard contractual clauses adopted by the European Commission under Art. 46(2)(c) GDPR, as incorporated into that provider's data processing terms, together with the supplementary measures those terms describe. Our own conversion, storage and job records stay in the EU: the service runs in europe-west1 and the storage and database are in the same region.

You may ask us for a copy of the safeguard we rely on.

5. Your rights

Under the GDPR you may ask us to: give you a copy of your data (access); correct it; erase it; restrict how we use it; hand it over in a portable form; or stop processing based on legitimate interest (object).

Write to [email protected]. We answer within one month.

In practice, most of your data is gone before you could ask for it — uploads and results are removed by a retention policy within a day, and job records stop working after 65 minutes and are deleted automatically, which can take up to a day. What persists is your sign-in account. To delete that, write to [email protected] from the address you signed in with and ask us to delete your account. We do it within one month and confirm when it is done. There is no self-service delete button in the product yet; when there is, this paragraph will say so.

If you think we have got this wrong, you can complain to the data protection authority of the country where you live, where you work, or where the problem happened. In the Netherlands that is the Autoriteit Persoonsgegevens, in Germany the competent Landesdatenschutzbehörde, in Spain the Agencia Española de Protección de Datos, in Poland the Prezes Urzędu Ochrony Danych Osobowych, in the United Kingdom the Information Commissioner's Office, in Brazil the Autoridade Nacional de Proteção de Dados, and in Türkiye the Kişisel Verileri Koruma Kurumu.

6. Children

You must be at least 16 to use rasterless.com. This is a condition of use we set, not a data protection threshold — GDPR Art. 8 concerns consent, and we do not rely on consent. The service is a tool for making vector files and is not directed at children.

We do not verify age, and we are telling you that plainly rather than implying a check we do not perform. Signing in uses your Google account, and Google applies its own minimum ages. If we learn that an account belongs to someone under 16, we delete the account and any data attached to it.

7. Security

The service runs over HTTPS. Access to the storage buckets and the database is restricted to the service itself. Cloudflare's network applies rate limiting at the edge, and a Cloudflare Turnstile bot check runs on conversions started without an account. We do not claim any bot-screening control beyond those two. No service is perfectly secure, and we do not claim ours is.

If you find a vulnerability, please tell us at [email protected]. We will not pursue anyone who reports one in good faith and does not access other people's data.

8. If you are in California

We do not currently meet the thresholds that make the CCPA, as amended by the CPRA, apply to us: our annual gross revenue is far below the statutory threshold, we do not buy, sell or share the personal information of 100,000 or more consumers or households, and we derive no revenue at all from selling or sharing personal information. We review this at each revision of this policy. We set this section out anyway, because the rights below are ones we intend to honour whether or not a statute compels us to, and because the thresholds could be met as the service grows.

9. If you are in Brazil

This section applies if the LGPD (Lei nº 13.709/2018) covers you. We are the controller (*controlador*); the providers listed in section 3 are operators (*operadores*).

10. Changes

If we change this policy we will change the date at the top. If a change materially affects you, we will say so on the site.

11. Contact

We have no public postal address to give you while the service is run by one person and no company exists. When the Dutch company is registered, its registered address will be published here.

---

What changes when the company exists

This policy is complete and in force as it stands. Three things will be added to it, not changed in it, once the Dutch company is registered: the company's name, KvK number and VAT number; its registered address; and a self-service account deletion control in the product to replace the email route in section 5. None of those additions reduce any right described above.

Related pages