By using the PrimaGuide, you agree your personal data is handled as described in this document.

The data protection laws in different countries describe, how an IT system should store, manage and protect the end-user data. This document describes in an understandable and transparent way, what data and why is stored in the GpsNose platform (called GpsNose in the following text), so the end-user can understand and accept or reject using it.

GpsNose consists of:

• www.gpsnose.com server (= "the server"), and
• Android/iPhone "PrimaGuide" mobile application (= "the mobile app").

GpsNose allows people to explore their neighborhood and interact with other people. To fulfill this goal, GpsNose needs to gather, store and handle the data entered by the end-user: by you.

GpsNose © SwizzBits s.r.o. is given to you completely free of charge; neither the software nor the data is generating any profit currently. It’s a technical experiment how to live with a better "social" platform, which is both anonymous and real, as opposed to all those "can’t live without it" commercial platforms available today, which steal your privacy and are unrelated to the real world around you.

Check the online documentation at https://www.gpsnose.com/Home/About for more details.

GpsNose and its creators don’t guarantee anything to you, neither technically nor legally. You can’t expect/demand/complain about anything. We hope you like GpsNose but don’t blame anybody but you when anything gets wrong - take it or leave it :-)!

THE GPSNOSE SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

The GpsNose server is reached at www.gpsnose.com and is used by:

• The web homepage, when visited by the web-browser
• The mobile devices, when access by the GpsNose mobile application

The information you enter in GpsNose can be as little as an anonymous guest name, or as much as all your private data, which you would like to share with the others. It's always up to you, what you enter and share with others.

GpsNose never asks about your real identity information (your real name, home address, phone number, mobile ID etc.) and so it ensures the most possible freedom for anonymity.

On the other hand, to be able to protect you from any potential malicious anonymous user, the server must be able to identify the connecting end-point – only the technical device and not the user himself, as it protects the identity of the malicious user the same way, as it protects you. This is done by remembering:

• The user’s IP-addresses used to access the server
• The user’s application-ID on his mobile device

This design enables the server to reject the access to some malicious user without knowing, who is he actually. The server knows only the technical connection-details.

EXAMPLE: GpsNose can’t tell, who is an anonymous user like "gerry80". The only known information about "gerry80" is:

• "The last time gerry80 connected, was at this location"
• "gerry80 used these IP addresses for communicating with the server"
• "gerry80’s application-ID is 1234abcd"

When "gerry80" tries to SPAM or stalk users around, his login can be locked and the server connection is denied. But GpsNose has no idea, who is "gerry80" – it can only reject the access for him.

When the mobile application or the website is used, the server stores this data:

• Anything you explicitly create in GpsNose, such as your profile, places etc.
• Technical helper-data derived from the data you entered, to allow answering fast queries like: "Are there any messages waiting for me?" or "Is there any Nose in my neighborhood?"
• IP-addresses, from which you accessed the server

There is a special debugging scenario, in which an insider-user (a well-known beta-tester, who communicates intensively with the GpsNose developers) describes some complicated issue. Testing-feedback from daily life, like "When I entered this location two days ago, the system behaved not the same it behaves today" – these scenarios are very hard to analyze and debug.

Such person may agree for switching-on a debugging flag for him, which allows the server to record all his requests/responses, with all the available technical details, like time, IP-address, GPS, request/response-body etc. The developers can then analyze all this information and the problem can be fixed. The user is always asked, informed and aware of such technical troubleshooting monitoring and the data recorded is used solely for the technical fine-tuning purposes.

Generally, the data you enter into GpsNose, is saved and used only in GpsNose. The only exception to this rule is, when another website (called "mashup" in GpsNose) is connected to the GpsNose, which is always a transparent and explicit connection, visible to the end-user.

A mashup can be connected to GpsNose to:

• Display some data from GpsNose
• Allow its users to login with the GpsNose mobile app

The mashup is always a kind of data-view about the GpsNose data, i.e. it enables to read/write data from/to GpsNose in the same way, as the www.gpsnose.com website does and nothing more.

A mashup cannot read/write data, which you did not expect or agree to, like your location or email.

When you sign-in with the mobile app’s QR-code scanner, the mashup site gets your login-name. The mashup can specify which additional data it wants to read about you; you’re then informed and asked in the mobile app, if you really want to sign-in, as the mashup will get some additional information, like your email for example. You are always informed what’s going on, so it can’t happen, that after a login with your mobile app, the calling mashup site reads your email without your permission!

The data access from/to GpsNose website is available by using:

• Simple <iframe> HTML element
• AJAX/JSON API

EXAMPLE: A www.we-love-fishing.net website is connected to GpsNose as a mashup web using a few simple HTML elements. It can:

• Display all its community members faces and all the news the community recently generated.
• Rely on the GpsNose user-management, so it doesn’t need to implement the login-process itself. The community members can use their mobile devices to sign-in into the mashup website and use the community-specific data about fishing. Visiting the www.gpsnose.com website reveals the same data, also that coming outside the fishing-community.

The main tool used in GpsNose is the mobile application "GpsNose" running on your mobile device. The mobile app must communicate with the server regularly to:

• Store the items you create, like places or images
• Inform you about any potential platform notifications
• Show your profile to the other users inside the current area

The mobile app does:

• NOT Know nor sent your real person-identification
• NOT Have access to any of your private data stored on your mobile device, such as SMS, phone-calls, device ID etc.
• NOT Record your movement tracking, unless you’re explicitly recording a GPS track/tour at your will

Generally speaking, you can be sure the mobile app does read/store/send only such data, which is needed for its obvious functionality and not for gathering/tracking anything else.

The mobile app tries always to read your GPS location, as all the data you see is related to your current location. This is completely different from all the other platforms today, which show you some location-unrelated "friends" data. GpsNose data is always location-based.

When you let GpsNose run in the background (can be set in the app settings), it will read your current location also in the background - this has two main reasons:

• To stay area-visible: otherwise, you disappear from your area, nobody sees your distance to him and even your close relatives you explicitly share your location with (like your family members) can't see you on the map anymore
• To notice any area-talks: when there are chats going on in the area you're passing by, you wouldn't realize it, when your app is not running in the background

The GpsNose data stored on your mobile is used for caching, to protect your mobile data usage from unnecessary re-reading the information. When GpsNose mobile app is running, it stores:

• Everything you entered into the GpsNose platform, from any device
• Cached data, which was read-in from the server by the GpsNose app

When GpsNose mobile app is running, it sends this data to the server:

• The items you explicitly create on your mobile device, as Places, Tours, Photos etc.
• The last used location of your profile, which is immediately visible in your area, in the form like "guest15 < 100km"

The data you publish from the GpsNose mobile application, can also be reached from the website www.gpsnose.com. When the website is accessed with a web-browser, the browser reads/sends the data from/to the server.

The communication between the browser and the server is known as state-less, as the underlying HTTP protocol is also state-less. It means, the browser must resend some data over and over again, as the server "forgets" what happened in the previous browser-request.

EXAMPLE: The user switches the web language from "DE" to "EN", which causes a browser-to-server request/response round-trip. The user expects then, that the next following request will be answered in the correct language, the one the user selected just before. But the server handling the following requests has no idea anymore, that the language was changed before!

To be able to handle this, the browser must handle all this status-information, to assure the state-full expectations of the user. This information, stored in the browser, is mostly realized by using the cookies.

A cookie is just a little data package with a given name, expiry-time and a few other properties. Most web-browsers can show the user the stored cookies, for every web-domain the user visited.

When a website stores a cookie, such as "The selected language is EN", other websites can’t normally read/modify it, unless the website where the cookie was generated, wants to share its cookies with another website.

GpsNose does not share any cookies with other websites: the cookies, which were generated by www.gpsnose.com, are read/written only by the GpsNose website. GpsNose stores only the minimum needed data in the cookies, needed for the "normal"/expected user-experience, such as:

• The currently selected language for displaying the web-pages content, or
• The user’s current time-zone for displaying the correct date/time information.

GpsNose is available worldwide and it tries to adapt to the most broaden public, giving its users the most possible data-freedom.

As a general rule, you should enter only anonymous data everywhere – GpsNose supports anonymity in every possible aspect, so you don’t have to enter any private data.

You can see your own data on your mobile device and all this data can be changed or deleted at your will at any time.

In some countries, the laws describe, how the user can request his private data to be exported or deleted from an IT system. To provide the best user-experience, GpsNose implements this functionality as user-callable functions in the mobile app.

You can modify and delete selectively your data in the mobile app. Should additional support be needed, you can email us to info@gpsnose.com. After your identity is verified, the data-support (like questions to export, deletion etc.) will be provided free of charge as soon as possible.

You can use the GpsNose platform for free – and as such the expectations on the free-of-charge support must be understood adequately ;-). We do our best to help you, but don’t expect miracles please!

You can export all your data to be exported as XML, so it’s usable also in another software system should you need it there. In the mobile app GpsNose:

1. Go to the "Settings" menu and select the "Synchronize own data" menu item
2. Click the refresh-icon to have all your data downloaded in your mobile device and wait until the synchronization process completes
3. Select which data you would like to be exported with the on/off toggles beside the data-labels
4. Click the save disk-icon and wait until the process completes

In the bottom of the screen you see the available free memory your device currently has. If the memory is full, you can’t export the data of course all at once, but you can select individual data partitions, like only the impressions for example.

You can delete all your data from the GpsNose platform straight from the mobile app GpsNose:

1. Go to the "Settings" menu and select the "Delete profile" menu item
2. To confirm the permanent profile-deletion, enter your current login-password (when you are deleting an already-activated user profile), or your guest’s login-name (when you are deleting a guest-profile)

All your data is deleted from the GpsNose platform and you are logged off.