JAZZSERVE PRIVACY POLICY

Last updated: 7 August 2026


1. WHO THIS IS ABOUT

JazzServe operates jazzserve.com and JS Connect, an internal work tracker
used by our team and by people we work with. JS Connect is reachable through
a browser at jsconnect.jazzserve.com and through our mobile application.

This policy explains what we collect, why, and what you can ask us to do
about it. Questions go to hello@jazzserve.com.


2. WHAT WE COLLECT

Your identity, from Google. You sign in with a Google account. Google tells
us your email address, your name and your profile picture. We never see or
receive your Google password.

What you write. Issues, comments, worklogs, and the files you attach. This
is the content the service exists to hold, and it is visible to the people
your organisation has given access to.

Technical records. Our servers log the time of a request, the address it
came from, and which endpoint was called. These logs exist to keep the
service running and to investigate problems.

That is the whole list. We do not use advertising identifiers, we do not
track you across other websites, and our mobile application contains no
analytics or advertising software.


3. WHY WE COLLECT IT

To let you in and to decide what you may see. Your identity determines
which boards, issues and conversations are yours to read and change.

To operate the service. Storing your work and showing it back to you is the
service itself.

To keep it secure and working. Technical records let us find faults and
notice abuse.

Under the GDPR, we rely on the performance of our agreement with you or your
employer for the first two, and on our legitimate interest in a secure,
functioning service for the third.


4. SIGNING IN WITH GOOGLE

When you sign in, our server performs the exchange with Google and receives
your email, name and picture. It then issues its own access token to the
application you signed in from.

On a mobile device, that token is kept in the operating system's secure
storage — the Android keystore or the iOS keychain — and is removed when you
sign out. In a browser, it is kept in a session cookie.

Where you have explicitly allowed it, the service may also send email as
you, using permission you grant to Google. It does so only for messages you
ask it to send, such as sending a proposal to a customer.

You can withdraw our access to your Google account at any time through your
Google account settings, at myaccount.google.com. Doing so ends your ability
to sign in.


5. WHO ELSE SEES IT

We do not sell your data. We do not share it for advertising. Nobody buys,
rents or receives it for their own purposes.

Three companies process it on our behalf, because the service runs on their
infrastructure: Amazon Web Services, which hosts it; Google, which
authenticates you and, where you have allowed it, delivers email you send;
and our email provider, for messages the service sends about your account.

We will hand over data if a court or a competent authority lawfully requires
it, and not otherwise.


6. HOW LONG WE KEEP IT

Your account and the work recorded against it are kept while your account is
active, because that is the record your organisation relies on.

Technical logs are kept for a limited period and then discarded.

Ask us to delete your personal data and we will, except where we must keep
something to meet a legal or accounting obligation. Content you contributed
to shared work — a comment on an issue, for instance — may remain as part of
that record, and we will detach it from your identity where we can.


7. WHAT YOU CAN ASK FOR

If you are in the European Union, the GDPR gives you the right to see the
personal data we hold about you, to correct it, to have it deleted, to
receive a copy in a portable form, to object to processing based on our
legitimate interest, and to complain to your national data protection
authority.

You have these rights wherever you are as far as we are concerned. Write to
hello@jazzserve.com and we will answer within a month.


8. HOW WE PROTECT IT

Everything travels over TLS. Access tokens are stored hashed, never in plain
text. On mobile devices, credentials live in the platform's secure storage.
Access to production data is limited to the people who need it to run the
service.

No system is perfectly safe, and we will not pretend otherwise. If a breach
puts your rights at risk, we will tell you and the relevant authority
without undue delay.


9. CHILDREN

JS Connect is a tool for working adults. It is not directed at children, and
we do not knowingly collect data from anyone under sixteen.


10. CHANGES

If this policy changes we will replace this page and update the date at the
top. Changes that materially affect you will be announced in the service
itself.


11. CONTACT

hello@jazzserve.com