Privacy Policy
Last updated: 11 November 2026
This Privacy Policy describes how dgmads ("we", "us") collects and processes personal data through the dgmads platform — which currently consists of three coordinated products: the consumer mobile app dgmads (mobile app) (open and free to join), the dgmads Business (mobile app), and the website dgmads.com. We process data under the EU General Data Protection Regulation (Regulation 2016/679 — "GDPR"). This document is meant to be plain and useful — if anything is unclear, please write to info@dgmads.com.
1. Who is the Data Controller
dgmads is the Data Controller for the personal data processed across all three dgmads products.
Registered office: Palermo, Italy (company incorporation in progress; a project of Ivan Territo and Pietro Martorana). VAT / company number: assigned at incorporation.
For any data-protection request — access, rectification, erasure, objection, portability — you can write to info@dgmads.com. We reply within one calendar month, as required by GDPR Art. 12(3).
Considering the nature, scope and purposes of the processing, the appointment of a Data Protection Officer (DPO) under GDPR Art. 37 is not required. This assessment is reviewed periodically and any update will be reflected on this page.
2. What we collect, in general terms
The exact data we collect depends on which product you use and what you actively do inside it. We try to keep the dataset as small as possible. Categories of personal data we may process include:
- Identification & profile data: name or chosen display name, email born date, nationality, profile picture, photos, bio and interests, jobs, preferred languages, and — for Place Managers — the public details of the venue they represent.
- Communication data: messages exchanged between users (e.g. mate requests, meeting invites, chat), alerts you send to a venue, broadcasts a venue sends to nearby users, and reports you file about content or users (we store the report, the reason you select and a snapshot of the reported content, so our staff can review it even if it is later edited or deleted).
- Activity & content data: meetings or events you create or join, venues you save as favorites or visit, mate relations, accommodation bookings, suggestions you submit.
- Approximate location data: when you opt-in to location services, we use your position to surface nearby places, events, meetings to deliver geotargeted broadcasts, and also showing targeted ADV if Base user. We work with reduced precision whenever possible and we cache nearby results to avoid unnecessary queries. We never store your real position taken with GPS, unless it is used to set the user's position in app.
- Payment data: subscription tier, payment history, invoice references and discount codes used. Card numbers are NEVER stored on our servers — payments are processed by the relevant app-store (Google Play, Apple App Store) or by a PCI-DSS compliant payment processor. Free periods of a premium tier you received (welcome period, codes) are recorded in the same way, with an amount of zero.
- Welcome-period check: when a new account receives a free welcome period we keep a one-way hash of its email address and of the installation identifier of the device it first signs in from, together with the end date of that period. The address and the identifier themselves are not stored in this record, which is used only to give the welcome period once per person.
- Problem reports: when you use "Report a problem" in dgmads (mobile app) we store the type of problem, the screen you pick and the text you write, with your name, email, subscription tier, account age, the position set in the app and your device ID, so we can reproduce and fix it.
- Account-deletion feedback: when you delete your account in dgmads (mobile app) we ask why. For some reasons we ask for a short detail — the city you are in, a price you would find fair, the app you use instead, or which notifications bothered you. We store it with your name, email, subscription tier, account age and device ID, how the flow ended (you stayed or confirmed the deletion) and whether you signed in again before the erasure.
- Sign-up source: how your account was created — in dgmads (mobile app) (with the sign-up method, device type and app language), from the public page or an event of a community on dgmads.com, or through an invite link when we offer one. We store which community, event or invite it was. If we show a community these results, it only sees totals, never who signed up.
- Phone number, only for communities that ask for it: when a community on dgmads.com asks for a phone number to sign up for its events, we store the number you enter, linked to your account, for that community only, with the date you gave it and the version of these terms in force. We never show it on your profile or to other users.
- Early-access requests on dgmads.com ("Contact us" form): your name and email, whether you are a digital nomad / remote worker or a place to work from, the topics you pick, and — only if you fill them in — the city and country where you live and your questions or suggestions; also whether you agreed to receive news about the launch, with the date of the request.
- Add to calendar: when you tap it on an event in dgmads (mobile app), the app hands the event (title, description, place, start and end) to your phone's own calendar, which asks you to confirm. We never read your calendar or your contacts.
- Device & technical data: device model, operating system, app version, language and timezone, FCM push-notification token and crash logs.
- Usage statistics in dgmads (mobile app) (Firebase Analytics): screens you open, features you use (e.g. searches, mate requests, meetings and events you create or join), the steps of the subscription page and the purchase outcome, which version of a screen you saw when we test two layouts (A/B test), your subscription tier, app version and device type. Never your name, email address, photos or messages. By default these events are sent WITHOUT any identifier (no installation ID, no account ID) and are only counted in aggregate. Only if you consent (see section 3) are they linked to a random installation ID and to your random account ID, so we can understand how the app is used over time.
- Web analytics on dgmads.com (Google Analytics 4) only when you give consent through the cookie banner — pages visited and their order, device, browser and screen, country (derived by Google from your IP address, which is not stored), language, connection type and speed, page load times, referrer and UTM tags. If you are signed in to dgmads.com, these statistics are linked to your account ID. See the Cookie Policy for the full list and how to withdraw consent.
- Cookies and equivalent identifiers on dgmads.com — strictly necessary cookies are always active; analytics cookies only after your explicit consent. No third-party advertising cookies are used.
3. Why we process your data and on which legal basis
Each processing activity is anchored to one of the legal bases listed in GDPR Art. 6:
- To create and run your account, deliver the features you actively use, and let users and venues find each other — performance of the contract (Art. 6(1)(b)).
- To show your display name and profile picture to other users inside dgmads (mobile app) where the feature needs it: search, meetings, mates lists and chats. Your mates may also see them on in-app screens that invite them to chat with you (for example a plan offer that unlocks private chat) — performance of the contract and legitimate interest in presenting our plans (Art. 6(1)(b)(f)). We never use your picture to promote the service to people who are not your mates, nor outside the app.
- To process subscriptions, upgrades, downgrades, refunds and invoices visible on dgmads.com — performance of the contract and legal obligation (Art. 6(1)(b)(c)).
- To send transactional and service notifications (push, email) related to meetings, events you signed up for (for example when the organiser cancels or changes them), mate requests, broadcasts, payment status, security alerts — legitimate interest and contract performance (Art. 6(1)(b)(f)).
- To store the phone number a community asks for and show it to that community's owner and admins (section 4), when you sign up or sign in for its events on dgmads.com — performance of the contract, at your request, to take part in that community's events (Art. 6(1)(b)). The community decides to ask for it and how to use it, and needs its own legal basis for that use (section 4).
- To measure which channels, communities and events bring new users (sign-up source) — legitimate interest in growing the service and in supporting the communities that publish on it (Art. 6(1)(f)). It is not used for profiling or advertising.
- To handle early-access requests from the "Contact us" form on dgmads.com: contact you about your request, answer your questions, and decide in which cities and countries to expand first and which features to build first (from the city and country and the topics you give us, counted together with those of other requests) — pre-contractual steps at your request and legitimate interest in planning the service (Art. 6(1)(b)(f)). It is not used for profiling or advertising.
- To send you emails about the launch and other dgmads news, only if the dedicated box in the "Contact us" form is ticked when you send it. You can untick it: it is not needed to send the request — your consent (Art. 6(1)(a)). You can withdraw it at any time by writing to info@dgmads.com.
- To prevent fraud, abuse, spam and unauthorised access, and to enforce our Terms — legitimate interest and legal obligation (Art. 6(1)(c)(f)).
- To check the text of public meetings and events against our community guidelines with an automated system (see section 5) — legitimate interest in keeping the platform safe and enforcing our Terms (Art. 6(1)(f)).
- To measure how dgmads (mobile app) is used and improve it (usage statistics and A/B tests of screen layouts, see section 2): anonymous statistics without identifiers — legitimate interest (Art. 6(1)(f)); statistics linked to your random IDs — your consent (Art. 6(1)(a)). Consent is asked separately when you sign up, is never pre-selected and is not a condition for using the app. If you have not said yes, the app may ask you again: from its second start, then 30 days after you say no, then at most once every 60 days. If you switch it off in Settings we do not ask again. You can give or withdraw it at any time from Settings → Privacy and account.
- To measure how dgmads.com is used and improve it (web analytics, see section 2 and the Cookie Policy), linked to your account ID if you are signed in — your consent through the cookie banner (Art. 6(1)(a); Codice Privacy Art. 122). Refusing has no effect on what you can do on the site.
- To keep proof of what you accepted: the version of these documents you accepted and your latest choice about usage statistics, each with its date — legal obligation and legitimate interest (Art. 6(1)(c)(f), Art. 7(1)).
- To fix the problems you report with "Report a problem" — legitimate interest in a working service (Art. 6(1)(f)).
- To understand why users leave, act on the problems they report and, if you write to us, answer you — legitimate interest in improving the service (Art. 6(1)(f)). This feedback is never used for marketing.
- To produce aggregated, anonymous statistics (e.g. visit frequency at a venue, popular routes) — legitimate interest (Art. 6(1)(f)). Aggregated stats cannot be tied back to an individual.
- For optional marketing communications — only after your explicit, separate opt-in consent (Art. 6(1)(a)). You can withdraw consent at any time from your in-app settings.
4. How the three products share data
The three products are part of the same platform, so some data flows naturally between them — but only what is needed for the feature you are using:
- A broadcast sent by a Place Manager through dgmads Business (mobile app) reaches nearby users of dgmads (mobile app) who have opted into that broadcast category.
- Events of a community are also published on its public page on dgmads.com, visible to anyone without an account. If you sign up for an event, the page shows your first name, the first letters of your surname and your nationality flag (for example "Anna Ros. 🇮🇹") among the first 10 participants, and the total number of sign-ups. The organiser of the event (the community's owner, its admins and whoever manages that event) sees the full list of participants; the owner and the admins can download the sign-ups of the last 30 days (event, name, surname, nationality flag, the phone number you gave the community if it asks for one, sign-up date) to organise the community's events. You can cancel your sign-up at any time from dgmads (mobile app): your name disappears from the page within a few minutes.
- A Community account can give other users of dgmads (mobile app) a role on its page: admin (manages every event of the community and its creators) or creator (manages only the events they create). The role is assigned directly, without a confirmation step, by looking up the email address of your account; the owner and the admins of that community then see your name, your email address and your profile photo in their members list, and you receive a notification. Events you create as admin or creator, or that the owner or an admin hands to you to manage, show your first name, the first letters of your surname and your profile photo (or your initials) on the public page and in dgmads (mobile app), where they link to your profile. You can leave a community at any time from the website; the owner is notified and the events you created stay, with your name, under the community's management.
- If you follow a community — signing up for one of its events on dgmads.com makes you follow it, and so does becoming mates with its account in dgmads (mobile app) — its owner and its admins see you in the community's list of followers: your first name and surname, your nationality (if it is on your profile) and since when you follow it. They can copy or download that list (name, surname, nationality, date) to organise the community's events. You stop following by removing the mate in dgmads (mobile app), or with "Stop following" at the bottom of the community's pages on dgmads.com (after signing in): you then leave the list, and your sign-ups to its upcoming events are cancelled.
- A community may require a phone number — the one you use on WhatsApp — to sign up or sign in for its events on dgmads.com (it is then asked in the form, with this explanation). Its owner and its admins see the number next to your name in its list of followers and can call it, copy it or download it with the list — not its creators, not other users, not the public. The community asks for the number to reach the people at its events, for example in its WhatsApp group: it decides how to use it and is responsible for that use as an independent controller, including adding you to groups where other members can see your number. We only store the number and show it to that community. It is saved when you sign up for one of its events, and you cannot sign up without it while the community asks for one. You can change it at any time on its event sign-up page; to delete it, stop following the community (which also cancels your sign-ups to its upcoming events). If the community stops asking for numbers, the one you gave stays with it until you stop following the community, delete your account, or its page is closed.
- A meeting created as a consumer becomes visible to the Place Manager of the venue it refers to, so they can reply and improve the experience. But the data of the participants are anonymised
- Subscription and billing information that you manage on dgmads.com is the same data shown inside dgmads Business (mobile app), so renewals stay in sync.
5. Automated moderation of public meetings and events
Meetings and events are public listings, visible to other users before they decide to join. To keep them safe, the text you write in them — title or name, description, and for events the link and contact details — is checked automatically when you publish or edit it, against the rules in section 4 of our Terms of Service (violence, hate speech, harassment, explicit sexual content, spam and scams, gratuitous vulgarity).
The check is performed by Google Vertex AI (Gemini) on servers located in the European Union. Only the text of the listing is sent: no name, email, account identifier, photo or location. Google processes it as our sub-processor and does not use it to train its models.
The outcome is stored with the listing: approved, sent to a person for review, or rejected with a short reason. A rejected listing is hidden from other users; you still see it, together with the reason. Nobody is scored or profiled: the check concerns a single text, not you as a person, and it has no legal or similarly significant effect on you.
Our staff can review and overturn any automated outcome. If you think a listing was rejected by mistake, write to info@dgmads.com and a person will look at it. You can also edit the text: it is checked again.
The outcome is kept as long as the listing exists and is deleted with it.
6. Sub-processors and where the data lives
We rely on a small number of trusted sub-processors. Each of them is GDPR-compliant and bound by a Data Processing Agreement.
- Google Firebase (Google Ireland Ltd.) — Authentication, Cloud Firestore database (configured on the EU multi-region eur3), Cloud Storage, Cloud Messaging (push notifications), Crashlytics and Analytics. When services need to cross to the United States (e.g. Analytics) the transfer relies on the EU Standard Contractual Clauses included in the Google Cloud Data Processing Addendum.
- Google Vertex AI (Google Ireland Ltd.) — automated moderation of the text of public meetings and events (section 5), processed in the EU multi-region, under the same Google Cloud Data Processing Addendum.
- Apple App Store and Google Play — to process in-app subscriptions and one-off purchases on mobile.
- Stripe Payments Europe Ltd. — for subscription, upgrade and invoice flows handled through dgmads.com. Card numbers are stored by Stripe (PCI-DSS Level 1), not by us.
- Transactional email provider — to deliver account, security and invoice emails.
7. Retention
We keep personal data only as long as is needed for the purpose that justified its collection:
- Active accounts: for the entire lifetime of the account.
- Closed or deleted accounts: erased from production within 30 days; residual backups are rotated and deleted within a further 90 days.
- Invoices and accounting records: 10 years, as required by Italian Codice Civile Art. 2220 and DPR 600/1973 Art. 22.
- Security and abuse-prevention logs: 6 months as a default, up to a maximum of 12 months (Provv. Garante 27/11/2008).
- Crash logs: up to 90 days. Usage statistics: up to 14 months, then deleted automatically. Withdrawing consent stops linking new events to you; statistics already collected are not deleted unless you ask (section 8).
- Accepted Terms / Privacy Policy version and your latest usage-statistics choice (with how many times you said no when the app asked): for the lifetime of the account.
- Sign-up source: for the lifetime of the account.
- Welcome-period check (hashed email address and device identifier): 12 months after the end of the welcome period, also if the account is deleted earlier, then deleted automatically.
- Phone number given to a community: until you stop following that community, you delete your account, or the community's page is closed. Copies the community made (downloaded lists, WhatsApp groups) are its responsibility.
- Problem reports: until we have dealt with the problem, then deleted.
- Account-deletion request (date, the reason you picked, the detail or note you wrote and the related feedback record): kept with the deletion record as evidence that we honoured it, like the deletion emails below.
- Early-access requests ("Contact us") without consent to news: until the service launches where you live or you create an account, and in any case no longer than 24 months from the request; deleted earlier if you ask (section 8).
- Early-access requests with consent to news: your name and email are kept to send you news until you withdraw that consent; the other details of the request (city and country, topics, notes) follow the 24-month limit above.
- Marketing consents (if you opt in to newsletters): re-validated after 24 months of inactivity.
- Account-deletion request emails: 3 years after fulfilment, as evidence that we honoured the request.
8. Your rights
Under GDPR Articles 15–22 you have the right to:
- Access the personal data we hold about you and obtain a copy.
- Have inaccurate data rectified or incomplete data completed.
- Have your data erased ("right to be forgotten"), where the legal basis no longer applies.
- Restrict or object to processing based on legitimate interest.
- Receive your data in a portable, machine-readable format.
- Withdraw any consent you previously gave, with effect for the future — for usage statistics directly from Settings → Privacy and account in dgmads (mobile app).
- Lodge a complaint with your national supervisory authority — in Italy the Garante per la protezione dei dati personali (garanteprivacy.it); in the United Kingdom the Information Commissioner's Office (ico.org.uk); in other EU/EEA countries the local DPA.
9. Age limit
dgmads is reserved for adults. The minimum age to register and use the service is 18 years old. By creating an account you confirm that you meet this requirement. Any account found to be in breach of this rule will be removed in accordance with our Terms of Service.
10. Security
We apply technical and organisational measures appropriate to the risk — including encryption of data in transit, hashed password storage, role-based access controls, automatic session timeouts, rate limiting on authentication endpoints, mandatory email verification and code obfuscation on production builds.
No system is 100% secure: if we become aware of a personal data breach likely to result in a risk to your rights, we will notify the competent authority within 72 hours and, where required, inform affected users without undue delay.
11. Changes to this Policy
We may update this Policy from time to time — for example when we launch a new feature or change a sub-processor. The most recent version is always available on this page. For material changes we will notify you through the app and / or by email before the change takes effect.