Website Privacy

1. What this policy covers

This policy explains what happens to information when you visit veesly.com or send us a message through the support form on this website.

It does not cover our apps. Streak Keeper has its own Privacy Policy, which describes what the app does on your device — that is a separate document, and this one does not change it. Each Veesly app keeps its own.

It also does not cover other websites you reach by following a link from here.

2. Who is responsible

Fabian Sielawa, publishing apps under the name Veesly from Poland, is the controller for the processing described here.

For anything about this policy, or to exercise the rights described in section 14, write to privacy@veesly.com.

We have not appointed a Data Protection Officer. We are not required to have one, and we would rather tell you that than imply a role that does not exist.

3. Reading the website

You can read every page on this website — product information, the FAQ, and all legal documents — without giving us anything and without signing in. There is no account system.

The website itself does not place cookies, does not use browser storage, and does not run analytics. Section 11 covers this in full.

Our hosting provider still handles the technical request needed to send you the page. Section 8 covers that.

4. The Streak Keeper support form

If you use the support form, you give us three things: your email address, the issue type you pick from the list, and the message you write.

The form has one hidden field that people never see and never fill in. It exists to catch automated submissions, and its contents are discarded.

We use what you send to read your request, route it to the right mailbox, reply to you, and keep the correspondence while the matter is open. Requests you mark as a data deletion request go to privacy@veesly.com; other Streak Keeper requests go to streak@veesly.com. Your email address is used as the reply address so we can write back.

We do not use your message or your address for marketing, and we do not add you to any list.

5. Why we may process this information, and on what basis

We do not rely on a single legal basis for everything, because the purposes are genuinely different.

Answering support and general enquiries, and keeping the correspondence while the matter is live, rests on our legitimate interests under Article 6(1)(f) GDPR. The interest is being able to support the apps we publish and reply to people who contact us. Using the form is your choice, you decide what to put in it, and you can stop the exchange at any time.

Handling a request to exercise a data protection right rests on Article 6(1)(c) GDPR, because responding to such requests is a legal obligation. Where we need to keep a record that a request was made and answered, that record rests on the same obligation.

Protecting the form from automated abuse, so that it stays usable, rests on Article 6(1)(f) GDPR. The interest is keeping a small support channel working and not having it flooded. Section 6 describes exactly what this involves.

Keeping correspondence beyond the immediate exchange, where we need it to establish, exercise or defend a legal claim, rests on Article 6(1)(f) GDPR; where a law requires us to retain something, on Article 6(1)(c).

We do not treat submitting the form as consent, because consent is not the basis we rely on. That also means there is no consent for you to withdraw here — instead you have the right to object, described in section 14.

6. Preventing abuse of the form

To stop the form being used automatically, we limit how many submissions can be accepted from the same source in a short period.

To do that without keeping network addresses, the website turns the requester's address into a one-way keyed value and stores only that, together with the times of recent accepted submissions. The application does not write the address itself to this store. The value is pseudonymous rather than anonymous: it is derived from something about you, and we describe it that way deliberately.

These records expire after 15 minutes and are then deleted. They are used only to decide whether the next submission is accepted. They are not used to recognise you, build any kind of profile, measure traffic, or for anything to do with marketing.

This 15-minute period applies only to these abuse-prevention records. It has nothing to do with how long an email you send us is kept — see section 10.

7. Sending your message

When you submit the form, the website composes an email and sends it through an authenticated mailbox to the relevant Veesly address. The message travels over our email provider's servers and is then stored in our mailbox, in the same way any email to us would be.

The email contains what you wrote, the issue type, your email address as the reply address, and the time of submission. It does not contain your IP address, your browser or device details, your location, or any identifier used for tracking.

8. Hosting and email provider

This website and our email are provided by Hostinger, which supplies the hosting, server operation, and the mailboxes and mail transmission we use.

Hostinger acts as a processor for this information — it handles it to provide those services to us, under a data processing agreement, and not for its own purposes. Hostinger also uses its own sub-processors to run its infrastructure.

This means it is not accurate to say that information you send stays only with us, or that no service provider is involved. It reaches our provider as part of delivering the website and the mail.

9. Server logs

Our own application code does not write logs of support submissions. It does not log the message body, your email address, or your network address, by design.

Separately from that, the hosting infrastructure records ordinary technical logs — the kind any web server keeps in order to serve requests, detect faults and protect against attacks. Those logs are created and retained by our hosting provider under its own arrangements, not by our application, and can include network addresses and request details.

We are not going to quote a retention period for those logs, because it is set by the provider for the hosting plan rather than by us, and we would rather say that than state a number we cannot stand behind.

10. How long we keep things

Support and enquiry correspondence is kept only for as long as it is reasonably needed — to handle and resolve your request, to keep a proportionate record of what was asked and answered, to deal with a related dispute or legal claim, or where a law requires us to keep it. When none of those still applies, it is deleted.

Abuse-prevention records expire after 15 minutes, as described in section 6.

We do not currently publish a fixed retention schedule in months or years for support mail. If we adopt one, we will state it here rather than leave this vague.

11. Cookies and browser storage

This website does not set cookies. It does not use local storage or session storage. It does not use any similar technique to store or read information on your device.

Because of that there is nothing for you to consent to, and no cookie banner — a banner asking permission for cookies we do not set would be theatre, not transparency.

If that ever changes, this section changes with it, and anything that legally requires consent will ask for it before it runs.

12. Analytics and advertising

There is no website analytics on this site. No page-view measurement, no heatmaps, no session recording, no A/B testing tool.

There are no advertising trackers or pixels, no advertising network, and no profiling for advertising. We do not sell personal data, and we do not share it for behavioural advertising.

This statement is about this website. Other websites you reach through a link from here have their own practices, and we have no say in them.

13. Who else sees your information

Our hosting and email provider, as described in section 8, because it operates the systems the website and our mail run on.

Anyone we are legally required to disclose to — a court or competent authority acting within its powers.

That is the list. We do not sell personal data, we do not trade it, and we do not pass it to advertisers or data brokers.

14. Your rights

Subject to the conditions in the GDPR, you can ask us for access to the personal data we hold about you, and for a copy of it. You can ask us to correct it if it is wrong, and to erase it. You can ask us to restrict how we use it.

Because we rely on legitimate interests for support correspondence and abuse prevention, you have the right to object to that processing on grounds relating to your situation. If you object, we stop unless we can show compelling legitimate grounds that override your interests, or we need the information for legal claims.

The right to data portability applies where processing is based on consent or on a contract and carried out by automated means. That is not the basis we rely on for support correspondence, so this right will not usually apply here — we would rather explain that than list every right as though they all applied equally.

We do not rely on consent for the processing described in this policy, so there is no consent to withdraw. If that ever changes, withdrawing will be as easy as giving it.

To exercise any of this, write to privacy@veesly.com. We may need to ask you something to be reasonably sure who you are, and we will keep that to a minimum.

15. Complaints to a supervisory authority

If you think we have handled your personal data wrongly, please tell us first — we would like the chance to put it right.

You also have the right to lodge a complaint with a supervisory authority, in the EU Member State where you live or work, or where you believe the problem occurred.

In Poland, that authority is the President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych), ul. Stanisława Moniuszki 1A, 00-014 Warszawa, telephone 22 531 03 00, kancelaria@uodo.gov.pl. Their current details are published at uodo.gov.pl.

16. International transfers

Our hosting and email provider operates internationally and uses sub-processors, some of which are established outside the European Economic Area. Your information may therefore be processed outside the EEA in the course of hosting this website and carrying our mail.

Where that happens, the provider's data processing agreement relies on the Standard Contractual Clauses adopted by the European Commission for transfers to third countries.

We are not claiming that no transfer outside the EEA takes place, and we are not naming a specific data centre country, because neither would be something we could stand behind for this account.

17. Security

The website is served over HTTPS. The support form is validated on the server as well as in your browser, is limited in how often it can be used, and sends mail over an authenticated, encrypted connection. Credentials are held in server configuration outside the published website and are not part of anything sent to your browser.

We take reasonable technical and organisational measures for the information we control. No website, and no email system, can be promised to be completely secure — email in particular passes through systems neither of us controls.

18. Children

This website is a product and company website. It is not directed at children, and it has nothing aimed at them.

We do not knowingly process personal data of children through it. If you believe a child has sent us information through the support form, write to privacy@veesly.com and we will delete it.

19. Automated decision-making

We do not make decisions about you by automated means that produce legal effects concerning you or similarly significantly affect you, and we do not profile you.

The abuse-prevention limit in section 6 is a technical control on how often the form accepts submissions. It does not evaluate you, and if it stops a submission you can still simply email us.

20. Changes to this policy

If we change how this website handles information, we will update this policy before or when the change takes effect, and change the date shown at the top.

This policy describes the website as it is actually built. It is not a description of what we might do later.

21. Contact

Privacy questions and requests: privacy@veesly.com

General enquiries: hello@veesly.com

Support for our apps: support@veesly.com