This policy explains what personal data Walksy collects, why, who else handles it, how long we keep it and what rights you have. It is the information we owe you under Articles 13 and 14 of the EU General Data Protection Regulation (GDPR).
We have tried to write it plainly. Where something applies only to the app, we say so.
Who we are
Walksy is run by Osema Fadhel as an individual. Walksy is not a company. In this policy, “Walksy”, “we” and “us” mean Osema Fadhel.
We are the controller of the personal data described here: we decide why and how it is used.
- Help with the app, your account and your data, including privacy requests: [email protected]
- Anything else: [email protected]
We have not appointed a data protection officer (DPO).
What this covers
This policy covers:
- the walksy.app website, in English and Italian;
- the waitlist on the website;
- the Walksy app for Android and iOS, from its release, and the live-share page at app.walksy.app that its links open.
The app is not released yet. Until it is, the app sections describe how it will work.
It does not cover services that have their own policies, even when you reach them through Walksy: Google Play and the App Store, Google and Apple when you sign in with them, and Google Maps or Apple Maps when you ask for directions.
At a glance
| What | Why | Legal basis | How long |
|---|---|---|---|
| Website requests: IP address, browser, page | Deliver the site and protect it from abuse | Legitimate interest (Art. 6(1)(f)) | A few months, at our providers |
| Your language choice | Open the site in your language | Stored only on your device | Until you clear it |
| Waitlist email address | Keep your place, send one welcome email, tell you when the app is out | Consent (Art. 6(1)(a)) | Until you ask us to remove it, and at most 12 months after the app launches |
| Spam check on the waitlist form | Keep bots and fake sign-ups off the list | Legitimate interest (Art. 6(1)(f)) | See “Waitlist” |
| Account and profile | Give you an account and show your profile | Contract (Art. 6(1)(b)) | While your account exists |
| Location and tracks | Record walks and run group hikes | Contract (Art. 6(1)(b)) | Tracks while your account exists; live positions 48 hours at most |
| Live-share links | Let someone you choose follow your walk | Contract (Art. 6(1)(b)) | 48 hours after the hike starts |
| Posts, comments, trails, chat | The community features you use | Contract (Art. 6(1)(b)) | While your account exists, with the exceptions under “Deleting your account” |
| Notifications | Tell you what is happening | Contract (Art. 6(1)(b)) | 30 days |
| App analytics | Learn which features are used | Consent (Art. 6(1)(a)) | 2 months |
| Crash and performance reports | Keep the app stable, fast and secure | Legitimate interest (Art. 6(1)(f)) | Up to 90 days |
| Reports, moderation and the automated checks of what you post | Keep people safe and meet our duties under the Digital Services Act | Legal obligation (Art. 6(1)(c)) and legitimate interest (Art. 6(1)(f)) | Nothing from a check that passes; cases 12 months after they close |
We do not sell personal data. We do not show ads, and we do not share data with advertisers.
Website visits
Two providers deliver the website’s pages to your browser: Google hosts the site, and Cloudflare’s network sits in front of it and protects it from bots and attacks.
What our providers see when you load a page
Every time your browser asks for a page, Cloudflare and Google receive the request: your IP address, the type of browser you use, the address of the page and the time. They use this to deliver the page and to detect abuse, and keep the IP data for a few months. They do this for us, as our processors.
Cloudflare also runs a short check in your browser to tell people from bots, and stores the result in a cookie, cf_clearance. The cookie policy explains it.
Our legal basis is our legitimate interest in running a website that works and is protected from attacks (Art. 6(1)(f)).
What nobody else sees
- The fonts are served from walksy.app itself. Loading a page sends no request to any other company.
- There is no analytics, no advertising, no social media buttons and no tracking pixel.
- Nothing is stored on your device when you visit, except your language choice and Cloudflare’s security cookie.
Your language choice
If you switch between English and Italian, your browser saves your choice, so the site opens in the right language next time. It stays on your device and is never sent to us. See the cookie policy.
Waitlist
The waitlist form is protected by a Google spam check (reCAPTCHA), which keeps bots and fake sign-ups off the list. Google runs it for us, as our processor.
What we collect
| Data | Where it comes from |
|---|---|
| Your email address | You type it |
| The time you joined | Added automatically |
| That you signed up on the website | A fixed value |
| Your language, English or Italian | The version of the site you signed up on, so the emails are in your language |
| A one-time code from the spam check | The spam check creates it when you press the button. We delete it once it has been checked. |
| The result of the spam check | The spam check returns it when we verify the code |
Signing up twice with the same address does not create a second entry.
What happens, step by step
- When you start using the form, your browser loads the spam check. Nothing from Google loads before that. The spam check may set cookies, and it collects signals about your device, your browser and how you use the page, to tell people from bots.
- When you press the button, your entry is saved in our database, in the EU (Belgium). The list cannot be read from the website.
- Our server then checks the result of the spam check. If the check fails, the entry is deleted straight away.
- If the check passes, we keep its result with your entry, delete the one-time code and send you one welcome email, from [email protected].
- Our server keeps a log of what happened, for example “email sent”. The log does not contain your email address, and it is deleted after 30 days.
Why, and on what basis
We use your address to keep your place on the list, to send you the welcome email and to tell you when the app is available. We do not use it for anything else, and we share it only with the processors named in this policy.
The legal basis is your consent (Art. 6(1)(a)). You give it by typing your address and pressing the button. The note under the form tells you what will happen.
The spam check runs on our legitimate interest in keeping bots and fake sign-ups off the list (Art. 6(1)(f)).
Leaving the list
Write to [email protected] from the address you signed up with, and we will delete it. You can withdraw your consent at any time. That does not affect what we did before.
The welcome email does not have an unsubscribe link yet, so writing to us is the way to leave.
How long we keep it
Until you ask us to remove it, and at most 12 months after the app launches. Entries that fail the spam check are deleted within moments. The log of what happened is deleted after 30 days.
The waitlist is kept separately from the app. Joining it does not create a Walksy account, and we do not copy your address into the app.
Your Walksy account
This section and the ones after it, up to “Moderation and safety”, are about the app. They apply from its release.
Signing in
| How you sign in | What we receive |
|---|---|
| Email and password | Your email address and password. The password is never stored as plain text, and we never see it. We email you a link to verify your address, a link to set a new password when you ask for one, and a note each time your password changes. |
| Your email address, name and profile picture, as your Google account shares them | |
| Sign in with Apple | Your name and email address. If you choose “Hide My Email”, we receive an Apple relay address instead. |
Our sign-in service also records when you created the account and when you last signed in. For security, it logs IP addresses and keeps them for a few weeks. Sign-in is handled in the United States (see “International transfers”).
We send these account emails ourselves, through Resend (see “Who processes data for us”). Each one carries your email address and is written in your app’s language. The note that your password changed also says when, in your phone’s time zone, and whether it was on an Android phone or an iPhone. If you ask for a new password for an address that has no Walksy account, nobody is emailed, and the app answers the same either way. To stop these emails being misused, we count requests for each address and each internet connection over an hour, under a one-way code that holds neither; the counts are deleted within two hours. We keep the time of the last password change we emailed you about, so that you get one note per change, and delete it with your account.
When you sign in with Google or Apple, they decide for themselves what they do with your data, under their own policies.
Your public profile
Any signed-in Walksy user can see your public profile. There is no option to make an account private. People can find you by searching for your username or your first name.
| On your profile | Notes |
|---|---|
| Username | Unique to you |
| First name | |
| Profile photo | We make smaller copies for display |
| Bio | |
| City, region and country | Picked from a list based on GeoNames. Shown by default; you can hide it. |
| Numbers of followers and people you follow | |
| Completed hikes, total kilometres and XP | Calculated from your walks |
| Search keywords | Made from your username and first name, so that search works |
Your private profile
Only you, and our systems, can see:
- your email address;
- your surname;
- the full record of the place you picked;
- an identifier for each device you use, so that we can send it notifications;
- your notification preferences;
- your answer on whether to share your location with your group during hikes;
- the language of your app.
Signing up
When you sign up, you tick a box to accept the Terms of service and to confirm that you have read this policy.
Why, and on what basis
We need this data to give you an account and the features you signed up for. The legal basis is the performance of our contract with you, that is, the Terms (Art. 6(1)(b)).
Location and walks
Walksy is an app for walking, so it uses your location. A track can say a lot about a person: where they live, where they go, when they go out. This section explains exactly what we collect, who sees it and how you can limit it.
Permission
The app asks for permission to use your location. At the moment it asks before you sign up, and you cannot skip that step. You can change the permission in your phone’s settings at any time. Without it, the app cannot record walks.
A rough position for “near me”
To show trails near you and to suggest the nearest town for your profile, the app uses a rough position: your phone’s last known position, or one low-accuracy reading. That position stays on your phone. The app only asks our servers for what is in the area around you, about 5 km across.
On the map, the app can show where you are. That dot is drawn on your phone.
While you record a walk
When you start a walk, the app uses GPS in the foreground and in the background. Recording goes on when the screen is off or when you use another app. It stops when the walk ends.
For each position, the app keeps a breadcrumb on your phone:
| Data | Why |
|---|---|
| Latitude and longitude | To draw your track |
| Altitude and accuracy | For elevation, and to know how far to trust a point |
| Time and speed | For distance, pace and duration |
| Whether the position is simulated (mock location) | To tell real walks from faked ones |
Breadcrumbs stay on your phone and are left out of your phone’s cloud backup. They are deleted from the phone once the walk has been saved to our servers.
The app also reads some sensors. It does this on your phone:
- the barometer and motion sensors, to measure elevation better;
- the battery level, which your group and anyone you share a live link with can see;
- the connection status, to know when it can upload.
What we keep on our servers
When you save a walk, we store your full track, with a timestamp for each point.
- Your full track is only ever yours to see, on a group hike as on a solo walk.
- On a group hike, we also make a “walked line”: your track from where you joined the hike’s trail to where you left it, so the way from your door to the trailhead stays off it. Group hikes are public, so every signed-in user who can see the hike can see your walked line.
- A solo walk is private while you are on it: nobody else can see that you are out. Once it is finished, and it counts as a walk, it shows on your profile: its title, date and figures, and a walked line with the parts inside your privacy zones cut out.
To work out elevation for tracks and trails, our servers look up their points in the Copernicus elevation model, a public dataset that Amazon Web Services hosts as open data. These lookups contain coordinates only, and nothing that identifies you.
Privacy zones
You can set up to 5 privacy zones, for example around your home. Each zone has a name, a centre and a radius. Only you can see them. Whatever we make public from your solo walks and trails leaves out the parts inside your zones. You can also choose to hide the start and end of each of them, by 200, 500 or 1,000 metres; that is off unless you turn it on.
Live positions during a group hike
During a group hike, if you choose to share your location with the group, the app sends your live position to the other participants. That is your latitude and longitude, accuracy, altitude, speed, direction, battery level and recent trail. Only people on the same hike can see it.
From these positions, Walksy can alert the group when someone seems to have split off, has gone quiet for a while or has a low battery.
Live positions are deleted when you save the walk, and in any case within 48 hours.
Directions
If you tap “Directions”, the app opens Google Maps or Apple Maps with the destination. From then on, Google or Apple handle your data as independent controllers, under their own policies.
Legal basis
Recording walks, saving them and sharing them with your group is the service you ask for. The legal basis is the performance of our contract with you (Art. 6(1)(b)). The permission on your phone is a separate control, and you can change it at any time.
Live sharing with someone at home
You can make a link that lets someone follow your walk without a Walksy account: a partner, a parent, a friend at home.
What the link shows
- your username and profile photo;
- your position and how accurate it is;
- your battery level;
- your recent trail;
- when your phone last sent a position, and whether you have finished;
- the hike’s title, planned route and expected finish time.
Who can see it
Anyone who has the link can open it. There is no password. Share it only with people you trust, and remember that they can forward it.
When a browser opens the link, it does not send the link’s secret part to the server, so that part does not end up in server logs or in the previews that messaging apps make of links.
How long it works
The link stops working 48 hours after the hike starts, or as soon as you close it. For a few seconds after you close it, it may still show your last position.
The person watching
The live-share page is at app.walksy.app. When someone opens it:
- We keep their IP address in a scrambled form, never the address itself, to stop people guessing links or overloading the service. It is deleted automatically about two hours after their last view. The legal basis is our legitimate interest in protecting the service (Art. 6(1)(f)).
- Our hosting provider receives the request (IP address, browser, time), as it does for every page we host.
- Our map provider receives the viewer’s IP address, the area of the map on screen and data about how the map is used. The map may keep an identifier in the browser’s local storage.
For you, the legal basis is the performance of our contract (Art. 6(1)(b)): you choose to make the link.
What others can see
| Who | What they can see |
|---|---|
| Any signed-in Walksy user | Your public profile; who you follow and who follows you; your posts, with their comments and likes, unless you have blocked them; the comments and likes you leave; group hikes you organise or join, with their participant lists; your walked lines on group hikes; your finished solo walks that counted, with their walked lines; trails you have made public |
| People on the same group hike | Also your live position while you share it |
| People in a chat with you | The messages in that chat |
| Anyone with your live-share link | What the link shows (see “Live sharing with someone at home”) |
| Only you | Your private profile, privacy zones, private trails, the full track of every walk, a solo walk while you are on it, the breadcrumbs on your phone, your reports and your blocks |
| Our moderators | What they need to handle a report (see “Moderation and safety”) |
Walksy has no public web profiles. To see your profile, posts or hikes, someone needs a Walksy account. There are two exceptions: a live-share link you make, and image files. Anyone who has the exact web address of a photo can open it.
Content, chat and community
Posts
After a walk, you can post about it: text, a place name, the walk’s stats and photos.
Before uploading a photo, the app removes the hidden data stored in it, such as the GPS position where it was taken. We then make smaller copies for display.
Comments, likes and follows
You can comment on posts, like them and follow people. Each comment and like keeps a copy of your name and the address of your profile photo, so that it can be shown quickly.
Group hikes
A group hike has a title, a date, a meeting point and places along the way. Group hikes are always public, and so is the list of who is going.
Participants can vote to remove someone from a hike. We store the vote. Individual ballots are not shown to anyone.
Trails
You can create trails and keep them private or make them public. Only you can see a private trail. For a public trail, we cut out the parts inside your privacy zones, and hide its ends if you choose to. Once a day, we send the public shape of trails to our map provider, so that they appear on the map for everyone.
Chat
You can chat one to one or in groups. Messages are text only. Only the people in a chat can read it.
Messages are encrypted in transit and when stored, but not end to end. You can report a message by holding it down (see “Reports, blocks and votes”).
Reports, blocks and votes
When you report something (a chat message included), block someone or vote in a group hike, we store it. See “Moderation and safety”.
Legal basis
These are the features you sign up for. The legal basis is the performance of our contract with you (Art. 6(1)(b)).
Notifications and devices
Push notifications
To send push notifications, the app registers your device with our notification service. We link an identifier for your device to your account, together with your notification preferences. You can turn notifications off in the app or in your phone’s settings.
The notifications in the app’s list are deleted after 30 days.
Checking that the app is genuine
To make sure that requests come from the real Walksy app on a real device, the app asks Google (on Android) or Apple (on iOS) to confirm it. The check keeps none of what it sends them.
The legal basis is our legitimate interest in protecting the service and its users from abuse (Art. 6(1)(f)).
Language
We store your app’s language, so that notifications reach you in it.
App analytics and crash reports
Analytics, only if you agree
The app asks the first time you open it, before it sends any usage statistics. “Allow” and “Don’t allow” sit side by side, the same size, and nothing is collected until you answer.
If you agree, the app collects usage statistics, so that we understand how Walksy is used: which screens are opened, which features are used and how long a session lasts. It collects an identifier for this installation of the app, these events, your device model, operating system, app version and language, and your approximate country or region. Analytics data is not linked to your Walksy account, and the app does not read your device’s advertising ID.
You can change your mind at any time in Settings › Privacy or, before you sign in, under “Privacy choices” on the first screen. Turning statistics off stops the collection and clears the analytics data still on your phone, together with this installation’s identifier.
The legal basis is your consent (Art. 6(1)(a)). We keep analytics data for 2 months.
Map data for Mapbox, only if you agree
The maps in the app are drawn by Mapbox. Mapbox’s map software can send Mapbox de-identified data about where your phone is and how the map is used, which Mapbox uses to improve its maps. The app keeps this off unless you allow usage statistics, and the same switch in Settings › Privacy turns it off again. You can also turn it off from the map itself, under the “i” in its corner.
Whatever you choose, Mapbox counts each session in which the app shows a map, so that it can bill Walksy. That count carries no location.
The legal basis is your consent (Art. 6(1)(a)).
Crash reports and performance
When something goes wrong, the app sends a crash report: what went wrong in the code, the device model, operating system and app version, free memory and disk space, and whether the app was in the background. Reports also include short technical notes that the app writes before an error, and cover errors that did not crash the app. They are linked to your account’s internal id, a random string that is neither your name nor your email address, so that we can find out what went wrong for you.
The app also measures how fast it starts, how smoothly screens draw and how long it takes to load data. These measurements record which web addresses the app contacted, without what it sent or received, together with device information, an identifier for the installation and the country worked out from the IP address.
The legal basis is our legitimate interest in keeping the app stable, fast and secure (Art. 6(1)(f)). You can object at any time by writing to [email protected].
You can turn off crash reports and performance data in the same places. Reports written while they are off are deleted from your phone, never sent.
Crash reports are kept for up to 90 days. Performance data linked to an IP address is kept for 30 days, and other performance data for 60 days.
Moderation and safety
What we process
- Reports: who reported, what (a post, comment, trail, account, group hike or chat message), the reason, the explanation if one was given, the statement of good faith for a report of illegal content, and when. We also look at how new the reporting account is (see “Automated steps”).
- A copy of the reported content, as it was when it was reported, so that a decision can be checked later.
- Decisions: what a moderator decided and why, the statement of reasons sent to the author, the outcome sent to reporters, requests for review, warnings and suspensions.
- Blocks: who blocked whom.
Who sees it
Moderators work in a separate moderation tool, which only people we authorise can open. The notice an author receives does not say who reported them.
Automated steps
Checks before anything is shown. What you write or post is checked automatically before anyone else can see it, against the community guidelines:
- Text, such as a post, a comment, your name and bio, a hike’s title and details or a trail’s name, is checked against a list of words, and then by Google’s text moderation in the EU. Text that breaks the guidelines is not saved, and you are told which rule it breaks while you can still change it. Chat messages are checked against the list of words only, and a message that matches it is removed before anyone is told of it.
- Photos are checked by Google’s image analysis (SafeSearch) in the EU. A new post waits, hidden from everyone but you, until its photos have been checked, usually a few seconds. If a photo shows nudity or sexual content, or graphic violence, the post is removed and you receive a statement of reasons that says an automated check decided, with a way to ask for a review. A profile photo that breaks the rules is not used.
- We keep nothing from a check that passes. When something is refused, we keep which rule it broke, and for a removed post the case described below. Google processes what it checks only to answer us, as our processor.
Reports. A post, comment or trail reported by several different people is hidden while it waits for review. Reports from brand-new accounts do not count towards this. Something a moderator has already found to be within the rules is not hidden again by reports: a moderator looks at it again. Accounts, group hikes and chat messages are never hidden by reports alone.
People. Every other decision is made by a person, and a person looks at any automated decision you ask to be reviewed. Automated checks can be wrong; a review that finds one wrong puts your content back.
Authorities
If content suggests a threat to someone’s life or safety, we tell the police or the judicial authorities, as Art. 18 of the Digital Services Act requires. We also hand over data when a court or another authority lawfully orders us to.
Legal basis
Handling reports, sending statements of reasons and informing authorities are obligations under the Digital Services Act (Art. 6(1)(c) GDPR). Keeping the platform safe, handling reviews and being able to defend our decisions are our legitimate interests (Art. 6(1)(f) GDPR).
How long we keep it
12 months after a case closes, then it is deleted. We keep it for that time even if the account involved is deleted, as Art. 17(3)(b) and (e) GDPR allow.
Who processes data for us
These providers handle personal data on our behalf, under data processing agreements (Art. 28 GDPR).
| Provider | What for | Where |
|---|---|---|
| Hosting the website and the live-share page; our database, file storage and server processing; sign-in; push notifications; app analytics, crash reports and performance data; the spam check on the waitlist form; the check that the app is genuine; making smaller copies of photos; checking text and photos before they are shown; our moderation tool | Database, file storage and server processing in the EU (Belgium); the checks of text and photos in the EU. Sign-in and the resizing of photos in the United States. Website hosting, notifications, analytics, crash and performance reports, the spam check and the check that the app is genuine on Google’s worldwide network, which includes the United States. | |
| Mapbox, Inc. | Maps in the app and on the live-share page, including the public trails shown on them; in the app, map data only if you agree (see “Map data for Mapbox”) | United States |
| Resend, Inc. | Sending the waitlist welcome email, and the app’s account emails: verifying your address, setting a new password, and the note that your password changed | United States |
| Cloudflare, Inc. | Delivering the website through its network and protecting it from bots and attacks; receiving the email you send to our @walksy.app addresses and passing it on to us | Cloudflare’s worldwide network, which includes the United States |
The maps in the app also send our map provider data about how the map is used and how it performs, which can include your location. You can turn this off from the ⓘ button on any map.
Some companies receive data as independent controllers, not on our behalf:
- Google and Apple, when you sign in with them;
- Google Maps and Apple Maps, when you ask for directions;
- Google Play and the App Store, when you download the app;
- authorities, when the law requires us to share data with them.
International transfers
Some personal data goes to the United States, as the “Where” column of the table above shows. When personal data leaves the European Economic Area, we rely on:
- the EU-US Data Privacy Framework, where the recipient is certified under it (European Commission adequacy decision of 10 July 2023);
- otherwise, the European Commission’s Standard Contractual Clauses (Art. 46(2)(c) GDPR), with extra measures where needed.
You can ask for a copy of these safeguards at [email protected].
How long we keep data
| Data | How long |
|---|---|
| Website request logs, at our providers | A few months |
| Waitlist entry | Until you ask us to remove it, and at most 12 months after the app launches |
| Waitlist entry that fails the spam check | Deleted at once |
| Log of what happened to your waitlist sign-up | 30 days |
| Account, profile, tracks, walked lines, posts, trails and chats | While your account exists |
| Sign-in data | While your account exists, then up to 180 days in our sign-in service’s backups. IP addresses logged at sign-in: a few weeks. |
| Breadcrumbs on your phone | Until the walk is saved to our servers |
| Live positions | Until you save the walk, and 48 hours at most |
| Live-share links | 48 hours after the hike starts, or until you close the link |
| Scrambled IP addresses of people watching a link | About two hours after the last view |
| Notifications | 30 days |
| Moderation cases, reports and notices | 12 months after the case closes |
| App analytics | 2 months |
| Crash reports | Up to 90 days |
| Performance data | 30 days if linked to an IP address, 60 days for the rest |
| Backups of our database | 7 days |
| Deleted or replaced photos | Up to 7 days |
| Emails you send us | As long as we need to handle your request |
Some of these deletions happen automatically and can take up to a day longer than the period shown.
Deleting your account
You can delete your account in the app, in Settings. For your protection, you need to have signed in recently. If you have not, the app asks you to sign in again. Without the app, see Delete your Walksy account.
What is deleted
- your sign-in account, your profile and your username;
- your follows, in both directions;
- your place in the hikes you joined, with your tracks and walked lines;
- your direct chats, with their messages;
- your posts, with their comments, likes and photos;
- the comments and likes you left on other people’s posts;
- your messages in group chats: they are emptied, and the chat shows a deleted message in their place;
- your live position, your live-share links and your reports on trail conditions;
- your feed, your notifications and your blocks, in both directions;
- the trails you created;
- your stored files;
- the records we keep about you to prevent abuse of the service;
- your moderation records, except the cases we keep as described below.
What stays, for now
- Your name in the lines a group chat writes about a walk (for example, that you set off) and in the record of a removal vote.
- Other people’s notifications that mention you stay until they expire, within 30 days.
- Moderation cases about you are kept for 12 months after they close, with the copy of the reported content they hold.
If you want any of these removed now, write to [email protected] and we will deal with it as an erasure request (Art. 17 GDPR).
Sign in with Apple
If you signed in with Apple, deleting your account also revokes Walksy’s access to your Apple ID.
Backups
Deleted data can stay in our backups, and among deleted files, for up to 7 days, and in our sign-in service’s backups for up to 180 days. After that it is gone.
The waitlist
Deleting your account does not touch the waitlist, which is kept separately. To leave the waitlist, write to [email protected].
Your rights
Under the GDPR, you have these rights:
| Right | What it means |
|---|---|
| Access (Art. 15) | Ask what data we hold about you and get a copy. |
| Rectification (Art. 16) | Have wrong data corrected. You can edit most of your profile yourself in the app. |
| Erasure (Art. 17) | Have data deleted. You can delete your account yourself in the app. |
| Restriction (Art. 18) | Have us pause the use of data while a question about it is settled. |
| Portability (Art. 20) | Receive the data you gave us, in a common machine-readable format, where we process it on the basis of consent or contract. |
| Objection (Art. 21) | Object to processing based on our legitimate interest, for reasons related to your situation. We then stop, unless we have compelling legitimate grounds or need the data for legal claims. |
| Automated decisions (Art. 22) | Not be subject to a decision based only on automated processing that significantly affects you. We do not make such decisions. |
| Withdrawing consent (Art. 7(3)) | Withdraw consent you gave, for the waitlist or for analytics, at any time. This does not affect what we did before. |
When we correct or delete data at your request, we also tell the recipients we shared it with, unless that is impossible or would take disproportionate effort (Art. 19).
How to use them
Write to [email protected]. The app has no self-service data export yet, so requests for access and portability also go to this address.
We answer within one month. If a request is complex, or we receive many, we can take up to two more months, and we will tell you why within the first month. It is free, unless a request is clearly unfounded or excessive.
We may ask you to confirm who you are, usually by writing from the email address linked to your account.
After a person’s death, their rights can be exercised by someone who has an interest of their own, acts on their behalf or has family reasons worth protecting, unless the person forbade it (Art. 2-terdecies of the Italian Privacy Code).
Complaints
If you think we handle your data unlawfully, you can complain to the Italian data protection authority, the Garante per la protezione dei dati personali (www.garanteprivacy.it), or to the authority in the EU country where you live or work, or where the problem happened. We would be glad if you wrote to us first, so that we can try to fix it.
Children
Walksy is not for children. You must be at least 16 years old to use the app (see the Terms of service).
The app does not check age yet.
When you sign up, you confirm that you are at least 16 years old.
If we learn that an account belongs to someone below the minimum age, we delete it. Parents and guardians can write to [email protected].
Security
- Data is encrypted in transit and at rest.
- Each person can see only what they are allowed to see. Private data is visible only to its owner.
- Moderators work in a separate tool, which only people we authorise can open.
- The positions your phone records during a walk are left out of your phone’s cloud backups.
- We keep the IP addresses of people who watch a live-share link only in scrambled form.
No system is perfectly secure. If a data breach puts your rights at risk, we will notify the Garante within 72 hours. If the risk is high, we will also tell you without undue delay. Articles 33 and 34 GDPR require both.
Changes to this policy
When we change this policy, we update the date at the top. If a change matters to you, for example a new purpose or a new kind of recipient, we will tell you in the app or by email before it takes effect. Where a change needs your consent, we will ask for it.
Contact
- Help with the app, your account and your data, including privacy requests: [email protected]
- Anything else: [email protected]
When you write to us, we use your address and your message to answer you. We keep the exchange as long as we need to handle it and, for requests about your rights, as long as we need to show how we handled them.