Privacy policy
Last updated 11 November 2026
This page explains what personal data devquake.com and its apps on *.devquake.com collect, why, how long we keep it, and what you can ask us to do with it. In short: we collect what we need to run your account and keep it safe, we never sell data, and analytics only run if you say yes.
This policy is available in English, German, Romanian, Hungarian, Italian and Spanish; every language version is equally valid.
1. Who is responsible
The controller of your personal data is Kurazs Lorant Alexandru, Telegrafului 34, Timisoara, Timis, Romania 300135. For anything related to your data, write to contact@devquake.com.
2. What we collect and why
| Data | When | Why | Legal basis (GDPR) |
|---|---|---|---|
| Name, email address, password (stored only as a one-way scrypt hash); if you sign in with Google, your Google account id and the email address Google confirmed (we never receive your Google password); if you sign in with Apple, your Apple account id and the email address Apple gives us (it may be a private relay address that forwards to you), and your name the first time (we never receive your Apple password) | When you create an account | To give you an account and sign you in | Contract (Art. 6(1)(b)) |
| Your language (English, German, Romanian, Hungarian, Italian or Spanish), and the preferred language you chose in your profile | When you use the site in a language or pick one | To show the site and send you emails in your language | Contract (Art. 6(1)(b)) |
| Roles, projects you subscribed to, projects the owner assigned to you, and an internal rating set by the site owner | When the owner configures your account | To give you access to the right apps and manage the community | Contract; legitimate interest (Art. 6(1)(f)) |
| Ideas you share (title, description, the project, an optional picture), your votes and your comments on ideas and text files you attach to an idea (only the site owner can open them; they are never shown on the site) | When you share an idea, vote or comment | To collect and discuss ideas for new apps. Public ideas and comments show your name to signed-in members; private ideas only to you | Contract (Art. 6(1)(b)); legitimate interest for moderation (Art. 6(1)(f)) |
| Blog posts you write (text, pictures, category, tags, language), when you published or changed them, how often they were read (not by whom), reports you send about posts, staff decisions about your posts, and the blog nickname you choose | When you write or report a post | To publish the DevQuake blog. Published posts are public with your blog nickname if you picked one in your account, otherwise with your display name, also for search engines; drafts only you see. When a post is published, its links (only the links) are checked with Google Safe Browsing. Reports are seen only by staff. Removing your account deletes your unpublished posts; published ones stay under an anonymous name | Contract (Art. 6(1)(b)); legitimate interest in a safe blog (Art. 6(1)(f)) |
| In the Habits and journal app: the reminder time you set on a habit, your time zone (so reminders arrive at the right hour), your two email switches (reminders and the monthly summary), and a record of which reminders and monthly emails were sent | When you set a reminder time, use the app, or change a switch | To send you the reminder emails and the monthly summary you asked for, once each. The summary uses only your habit ticks, never your journal. You can switch both off on the Today page; everything is deleted when you leave the app or delete your account | Contract (Art. 6(1)(b)) |
| In the Habits and journal app: who you share a habit with (the buddy’s account number and the name shown at the time), the invitations you sent or received, the cheers sent and received, and the notifications about them | When you invite someone, follow a habit or cheer | To let a buddy see the title and streak of the habit you share, and to cheer you on. A buddy sees nothing else of your habits or your journal. You can remove a buddy or stop following at any time; everything is deleted when you leave the app or delete your account, and notifications after 30 days | Contract (Art. 6(1)(b)); your invitation |
| Warnings, strikes and blocks about your posts, comments and works (the reason, the staff note, who decided and when), conversations with the DevQuake team about an item and your answers, and the emails we sent you about strikes | When the owner reviews a report about something you published and warns you, messages you or blocks your account | To keep the blog and the art gallery safe and to treat members fairly: three counted warnings give a strike, three strikes block the account. Reports are private: we never tell you who reported | Legitimate interest in a safe platform (Art. 6(1)(f)); legal obligation (Art. 6(1)(c)) for the EU Digital Services Act’s statements of reasons |
| In the art gallery (devquake.com/art-gallery): your gallery profile (address name, artist name, bio, statement, colours, layout, banner, which of your social links it shows, your watermark text), your works (the pictures your browser prepared: a watermarked version, a clean version cut into shuffled tiles and small versions; title, concept, description for people who cannot see it, medium, year, size, tags, series, who may see it and whether visitors may download it), the original file you upload, its SHA-256 fingerprint and a picture fingerprint (dHash), the upload time, your exhibitions, your answers when staff ask to show a work in a curated exhibition, likes, comments and reports, staff decisions about your works, and how much space you use; your artist level and when it changed (worked out from these numbers, or bought with NPS points: the point is used up and not given back); visits to your works counted without cookies, as a daily code made from the visitor’s IP address and browser, deleted the next day so only daily totals remain | When you open the gallery’s workspace, upload or change a work, like, comment or report | To show your art only to the people you choose (private, by link, members or everyone). Your original is stored privately and only you can download it; others only ever receive the protected versions. The fingerprints prove when you uploaded a work and find copies: a new public work very similar to another artist’s is pointed out to our staff and to that artist. Reports and staff decisions keep the gallery safe; staff are told about new public works by email to our own mailbox | Contract (Art. 6(1)(b)); legitimate interest in protecting artists’ works and in moderation (Art. 6(1)(f)) |
| In the art gallery’s comic studio: your library (characters, objects, quotes and descriptions you write, which of your works are their pictures, and the characters and objects you draw in ArtQuake, kept as vector drawings with their connection points), your comic drafts (pages, layouts, drawings, pictures you place, guides and lettering with its fonts), and the comics you publish: their pages as pictures with your watermark, their texts and their address | When you add to your library, edit a draft or publish a comic | To let you build comics from your own art. The library and the drafts are private to you; a comic is shown only as you choose (private, by link, members or public), like a work. Pages count toward your gallery space | Contract (Art. 6(1)(b)) |
| Social networks you add (network, your name or profile link) and whether a share button is shown | When you add them under Social accounts | To show share buttons for your networks on blog posts and your profiles on your public author page. Sharing opens the network itself; DevQuake posts nothing for you | Consent (Art. 6(1)(a)); remove them at any time |
| What you share with a public link: a recipe from the cookbook (with its photo), the card of a finished workout (routine, date, time, calories, sets, exercises; no weights, heart rate or photos), with your name, or a CV from the CV Builder (what that CV shows, including the contact details and photo on it) or a business card (name, qualification, the contact details you put on it, your website’s logo and the link to your CV); a business card counts how many visitors opened it, each once, by a random number their browser keeps, nothing else | Only when you make a public link | So anyone you send the link to can open it, also without an account, and social networks can show a preview. Search engines are asked not to list it; the link stops working as soon as you turn it off | Consent (Art. 6(1)(a)); turn the link off at any time |
| Your approximate position (rounded to about 100 m) | Only when you press “Search for nearby stores” (shopping lists) or “Search for available utility services” (utility bills) and allow it in your browser | To find shops around you, or your country and county or state for utility suggestions. It is used once and not stored | Consent (Art. 6(1)(a)); your browser asks every time unless you allowed it permanently |
| Projects you liked and your ratings of them (quality and usefulness, 1 to 5 stars) | When you like or rate a project | To show which projects people find useful and decide what to build next; only totals and averages are shown publicly | Legitimate interest (Art. 6(1)(f)) |
| One-time sign-in codes (stored only as a hash, valid 10 minutes) and account activation links (stored only as a hash, valid 48 hours) | Every sign-in, and once when you create an account | To confirm it is really you | Contract; legitimate interest in security |
| Password-reset links (stored only as a hash, valid 60 minutes), the time and IP address of each request | When you use “Forgot your password?” | To let you choose a new password and to stop abuse of the reset form | Contract; legitimate interest in security |
| Sign-in details: date and time, IP address, approximate location of the IP (country, region, city), internet provider, whether the IP belongs to a VPN or proxy (and its provider), browser, operating system, device type, and your browser’s time zone, language and screen size | Every sign-up, sign-in and code entry, successful or not | To detect and stop account takeovers, lock an account for 3 hours after 3 wrong passwords in a row, show you your recent sign-ins, and produce security statistics | Legitimate interest in keeping accounts and the site secure |
| Name, email address, subject, message, IP address and browser, and our replies to it. Signed in, your account’s name and email are used, and you see your messages and our replies on your account, where you can delete them | When you use the contact form or write from your account | To answer you (on your account and by email) and to block spam | Legitimate interest in answering enquiries; pre-contract steps where relevant |
| Log of emails we sent you (type, time, delivery status; not the content) | When we email you | To troubleshoot delivery and prove security notices were sent. Automatic emails (sign-in codes, reminders, notices) are sent from no-reply@devquake.com; a reply to one reaches contact@devquake.com | Legitimate interest |
| Activity log of actions on the site (for example sign-ins, account changes, errors), with IP address and browser | While you use the site | Security, troubleshooting and abuse prevention | Legitimate interest |
| Profile picture (optional, 256x256), your personal invitation code and NPS score, who invited you, and the email addresses you invite | When you upload a picture, share your link or send an invitation | Your profile, and the invitation feature you use (the invited person gets one email naming you) | Contract; legitimate interest in letting members invite people |
| Which apps you tried for free and when the 24-hour trial started and ended | When you start a free trial of an app | To open the app for you for 24 hours, only once, and to delete what you created in it if you do not subscribe | Contract (Art. 6(1)(b)) |
| Your custom themes (name, colours, fonts), the members you shared them with, and the theme you last chose | When you create or share a theme | To show the site in your theme on every device you sign in on, and let the people you chose use it; they see the theme and your name | Contract (Art. 6(1)(b)) |
| Your birthday (day and month, the year only if you give it; or only the year, if an app you allowed saved just that), and for each year when we sent the birthday email and when and how you received the gift point | When you enter your birthday on your account page | To wish you a happy birthday by email and on the site and to give you one NPS point as a gift, once a year; the year is never shown. The apps you allow (Account → Connected apps) may read it and, if you allow it, change it; a family app shows it to your family. | Consent (Art. 6(1)(a)): remove your birthday at any time on your account page |
| Which apps you subscribed to, also after you leave one | When you subscribe to an app | So that connecting an app you had before subscribes you to it again without NPS points | Contract (Art. 6(1)(b)): part of how subscriptions and NPS points work |
| Claims made for you (a prize or reward of NPS points): what it is for, how many points it gives, whether you claimed it. The store keeps the claim with a hash of its link and secret code, and emails you both | When DevQuake gives you a prize or reward, and when you claim it | To let only you claim it, once, and to add its NPS points to your account | Contract (Art. 6(1)(b)): part of how prizes and NPS points work |
| In-app notifications: reminders of upcoming events from the apps you subscribed to (title, short text, link, when you read it) | When an app reminds you of an event it also emails you about | To show the reminder in that app and on devquake.com. “Clear all” under the bell deletes them from our database | Contract (Art. 6(1)(b)): part of the apps you subscribed to |
| DevQuake’s newsletter: whether you subscribed and when you changed it, and which newsletters we sent you (and in which language) | When you turn it on in your account (it is off until you do), or follow the blog’s Announcements | To email you when a new app or a native version of an app comes out, in your language; never to anyone who did not ask. Every email has a link to unsubscribe | Consent (Art. 6(1)(a)): you can withdraw it any time in your account or with the link |
| DevQuake’s native apps: a random installation number, the app version, the phone’s model and system version, when the app was installed, opened and last used and for how long, the country and city of the connection (not the IP address); clicks on “Install on …” with your account; when you sign in in an app, a sign-in for that device (the app and the device’s name), shown under “Signed-in apps” in your account until you remove it; if you allow notifications, the address Google (Android) or Apple (iPhone) gives that app on the device, and when the last one was delivered; a notification tells Google or Apple only that a message came and the few words the app needs (such as your pet’s name, a table, or for a shared expense its group, who added it, its title and amount), the app writes the text itself; switch it off or remove it under “Signed-in apps”. ArtQuake for Windows also keeps, on the computer only, the sign-in of that device (in Windows’ credential store), your settings and the changes still waiting to be sent while you are offline; your comics, library and pictures stay in DevQuake’s database, and the pages of a comic you publish are drawn and watermarked on your computer before they are sent | When you install and use a native app, or click its install button | To show how the native apps are installed and used, to offer updates, to keep older versions working until they are updated and to start the app you have on this device from “Your apps” | Legitimate interest (Art. 6(1)(f)): running and improving the apps you use |
| How often and how long you use each web app: per day, the times you opened it and the minutes it was open | While you use an app on its subdomain | Statistics of the apps’ use, shown only to the site owner | Legitimate interest (Art. 6(1)(f)): improving the apps |
| What one app keeps from another you connected it with: in Social canteen, the dishes a staff member picks from their Cookbook (name, ingredients, allergens) and which Shopping list is the organisation’s purchasing list | When you connect two apps (Account → Connected apps) and use the feature | To work with the other app’s data in this app; the canteen keeps the dishes for its kitchen, also after the person who picked them leaves it. Disconnecting stops new calls; what was already copied stays with the organisation | Contract (Art. 6(1)(b)): part of the apps you connected |
| Invitations an app emails for you (Social canteen staff invitations): the address you type is used once to send it and kept in our email log; a one-way code of the address and the time, to apply sending limits; the app keeps only a hidden form of the address (for example a***@gmail.com). Addresses that chose “Don’t send me invitations” are kept as the same one-way code. Replies go to contact@devquake.com, or to the contact email the organisation published | When you send an invitation by email from an app | To deliver the invitation, to stop misuse (at most a few invitations a day per member and per address) and to respect people who asked for no invitations. The codes of sent invitations are deleted after 90 days; the email log after 365 days | Legitimate interest (Art. 6(1)(f)): letting organisations invite their staff, and protecting the invited from unwanted email |
| In the Habits and journal app: your habits and their ticks, your journal pages (mood, text, stickers, category, event) and how your journal looks, with the cover picture you upload; short notes of what your connected apps report for each day (for example a finished workout or a darts game); if you lock it, a one-way code (scrypt) of your secret phrase, a one-way code of the browser it is open in and until when, and how many wrong phrases were typed | When you use the app | To keep your habits and your private journal. Nobody else sees them. We cannot read your phrase back or tell it to you; a forgotten phrase can only erase the pages. Everything is deleted when you leave the app or delete your account | Contract (Art. 6(1)(b)) |
| In the Venue app: your venue (name, country, currency, VAT rates), its menu (items, prices, allergens), the names and roles of the staff you add with a one-way code (scrypt) of their PIN, your tablets (a name, when they were enabled and last used, a one-way code of their cookie, who is on it), the tables and their bills (items, who served, the guests’ tip choice, how it was paid; no names of guests), deleted six months after they are finalised, the sales numbers by day and item, your menu’s design with the background picture made from your pictures, and which shopping list is the venue’s purchasing list (what was bought there is read for the reports, not kept), the expense group and utilities you chose for its costs, a copy of your open darts tournaments shown on its public menu, the waiters’ sections, guests’ calls from a table (the table and the time, no names; kept 30 days), and the devices that get notifications (the address your browser’s push service, such as Google, Mozilla, Apple or Microsoft, gives for it; the message itself is encrypted), and your stock: ingredients and drinks with their levels, the recipes of menu items, and every change of the stock with who made it (kept 90 days), and the waiters’ phones you pair (a name, a one-way code of their key, and the address Google or Apple gives for notifications; a notification tells Google or Apple only the table’s name, the phone writes the text), and guests’ orders from the table (the table, what was ordered and when, who answered; no names of guests; kept 30 days), and the daily closings (who closed the day, the cash counted and the difference; no names of guests), voided items (the item, the table, the reason and who voided it; kept 400 days), and reservations (a guest’s name, an optional phone number and note, the day, time, number of guests and table; deleted 30 days after the day), and the fonts you upload for your menu (the file and the name you give it, until you remove it or delete your venue), and the hygiene logs (what was checked, the temperature, whether it was in order, the action taken, the supplier’s name for a delivery, who recorded it and when; kept 2 years) | When you set up a venue | To run your café, bistro or bar. The menu is public at its address while you keep it public; staff names and PINs are never shown to anyone else. For your staff’s names you are responsible as their employer; everything is deleted with your venue or your account | Contract (Art. 6(1)(b)) |
| In the developer tools (devtools.devquake.com): nothing you type, paste or open is sent to us, except a sample you choose to include in feedback. We count each button you use: the tool, whether it worked (or the error shown), the format, the size class of the input, your device type, browser and system, your browser’s time zone and language, and your name if you are signed in (otherwise a number that changes every day, made from your IP address and browser; the IP address is not stored). Feedback you send, with a sample only if you tick it. Your browser keeps your last options; signed-in members can keep them in their account. If you ask the AI label check’s model, your browser downloads the model from Hugging Face and its runtime from jsDelivr, who see your IP address like any website; your picture is not sent | When you use a tool; when you send feedback; when you save your options | To see which tools work and improve them; to answer feedback; to remember your settings | Legitimate interest in improving the tools (Art. 6(1)(f)); contract for saved options (Art. 6(1)(b)) |
| Anonymous visit counts: a daily visitor number derived from your IP address and browser with a random salt that is deleted the next day; only daily totals are kept | Each page view on devquake.com | To show how many people visit (also on the landing page) | Legitimate interest; no cookies, and nobody can be identified from what is stored |
| Usage statistics via Google Analytics (pages viewed, which app you use, which app features are used such as “list created” or “product added” without any names or contents, approximate location, device, a random identifier in a cookie) | Only if you click “Accept analytics” | To understand which pages are useful and improve the site | Consent (Art. 6(1)(a)), which you can withdraw any time |
We cannot see your device’s MAC address or, if you use a VPN, your real location: we only see the VPN server. We do not sell your data and do not use it for advertising ourselves; signed-in members see no ads inside the apps, ArtQuake or the account pages. Google ads may show on the blog and in the store (always, also when you are signed in) and, to visitors who are not signed in, on public pages such as the landing page, the legal pages, the apps’ front pages, the developer tools and the art gallery; Google asks for your consent first (see Recipients). Ads in the art gallery are marked as child-directed, so they are not personalised. We make no automated decisions about you other than the temporary security lock described above.
4. Who else processes data
We only share data with service providers that help us run the site:
- Hostinger hosts the website, the database and our email, so all data above is stored on its servers.
- proxycheck.io receives the IP address of each sign-up and sign-in and returns its approximate location, provider and whether it is a VPN or proxy.
- Google (Google Analytics) receives cookieless signals without an identifier on every page, and usage data tied to a random identifier only if you accept analytics. Google may process it outside the EU, including in the United States under the EU–US Data Privacy Framework.
- Google Safe Browsing (Google Ireland Ltd): the links in a blog post when it is published, to find phishing and malware. No personal data is sent.
- Google AdSense (Google Ireland Ltd), only on pages that show ads and only when ads are switched on (the blog and the store; to visitors who are not signed in also the landing page, the legal pages, the apps’ front pages, the developer tools and the art gallery’s public pages): Google shows ads and, in the EU, first asks for your consent with its own message; with consent it may use cookies to personalise ads, except in the art gallery, where ads are marked as child-directed. Signed-in members never see ads inside the apps, ArtQuake or the account pages.
- OpenStreetMap services: Overpass receives your rounded position to find shops nearby; Photon (by komoot) receives your rounded position to find your country and county, and what you type into the utility profile’s address fields for suggestions. Only when you use these features.
- Wikimedia (Wikidata and Wikimedia Commons): the names of stores in shopping lists and of companies, schools and organisations in the CV Builder, sent by our server to find their logos. Nothing about you is sent, and the logos are kept on our servers.
- OpenRouteService (HeiGIT, Heidelberg, Germany): in the Social canteen app, the addresses of the people on a delivery route and of the organisation’s kitchen, to find them on the map and compute the order of stops. Only when an organiser asks for it; names are never sent.
- jsDelivr: when a picture is read on your device (a meter in Utilities, an ID card or driving licence in Social canteen), your browser downloads the text-reading program and its language data from this content network, which sees your IP address. The picture never leaves your device for this.
- Hugging Face: if you ask the AI label check’s model in the developer tools, your browser downloads the model from Hugging Face and its runtime from jsDelivr; both see your IP address. Your picture is not sent.
- OpenStreetMap map tiles: when a driver opens the map in Social canteen, their browser loads the map images of that area from openstreetmap.org, which sees their IP address and the area viewed.
We may also disclose data where the law requires it, or to protect the site and its users against fraud or abuse.
5. How long we keep it
Old data is deleted automatically once a day after these periods:
| Data | Kept for |
|---|---|
| Your account, picture, language, roles, subscriptions, likes, ratings, invitations, and your ideas, votes and comments | Until you delete your account (Your account → Delete account) or ask us to. The site owner may remove accounts that have not been used for a long time; you get an email when that happens. |
| What you created in an app (for example your shopping lists) | Until you unsubscribe from that app or delete your account; shared content stays with the other people, without your name |
| What you created in an app during a free trial, if you did not subscribe | 30 days after the trial ended |
| Your custom themes and who you shared them with | Until you delete the theme or your account |
| Your birthday and the record of each year’s gift | Your birthday until you remove it; the gift record until you delete your account |
| Which apps you subscribed to | Until you delete your account |
| Your gallery profile, works and their originals, exhibitions, likes and comments | Until you delete them or your account (deleting a work deletes its pictures and original at once) |
| Your comic library, drafts and comics | Until you delete them or your account (deleting a comic deletes its pages) |
| Warnings, strikes, blocks and conversations about your content | Until you delete your account. Warnings and strikes stop counting after 12 months without a new warning, but stay in your record so the team can see the history |
| In-app notifications | 2 months |
| Addresses you invited who never joined | 3 months |
| Accounts whose email was never confirmed | 30 days |
| Sign-in activity (sign-in details and snapshots) | 3 months |
| Your account activity (sign-ins, subscriptions, changes to your account) | 3 months |
| Password attempts used for lockouts | 3 months |
| Other activity log entries | 6 months (security events 1 year) |
| Expired sessions, one-time codes, activation and password-reset links | 7 days |
| Record of emails sent | 1 year |
| Contact-form messages and our replies | 2 years |
| Anonymous visitor hashes and their daily salt | 1 day (only daily totals remain) |
| Google Analytics data | Per the retention set in Google Analytics (at most 14 months) |
6. Your rights
Under the GDPR you can ask us to:
- give you a copy of your personal data (access and portability);
- correct it if it is wrong;
- delete it, including your whole account (you can do this yourself: Your account → Delete account);
- restrict or object to how we use it, including processing based on legitimate interest;
- withdraw your analytics consent at any time (with “Cookie settings”).
Email contact@devquake.com from the address on your account. We answer within one month. If you are not satisfied, you can complain to the data protection authority of the EU country where you live or work.
7. Security
Passwords are hashed with scrypt, sign-in codes and session tokens are stored only as hashes, every sign-in needs a code sent to your email, connections use HTTPS, and repeated failed sign-ins lock the account temporarily and notify you. Access to user data is limited to the site owner.
8. Changes
We update this page when what we collect or why changes, and show the date at the top. For significant changes we will also email account holders.