Privacy policy
This policy explains what personal information Jumpfold collects through this website and the beta program, why we collect it, and what you can ask us to do with it. We have tried to write it the way we write everything else: plainly, and without claiming more than we can show.
1. Who we are
Jumpfold ("we", "us") operates jumpfold.com and is developing the Jumpfold application, a document continuity service for professionals. We are the controller of the personal information described in this policy. You can reach us at info@jumpfold.com.
2. What we collect
Information you give us
When you request a beta seat we collect what you enter in the form: your name, your work email address, your role, and optionally your firm or practice, the device platforms you use, and a short note about how your work moves between devices today. We ask you not to include client names or confidential details in that note, and we do not need them.
When you email us, we keep the correspondence so that we can reply and keep a record of what was agreed.
Information collected automatically
- Country. Our hosting provider tells us the country a form submission came from. We store the country code with your signup record.
- Rate-limiting hash. To limit abuse of the form, we may store a salted, one-way hash of the network address a submission came from. The address itself is not stored and cannot be recovered from the hash. If the salt is not configured, nothing address-related is stored.
- Service logs. Our hosting provider, Cloudflare, generates request logs in the ordinary course of serving a website. Our own application logs record only the role selected and the country of a submission, not names, email addresses or free-text notes.
This website does not use analytics services, advertising pixels or social media widgets, and it sets no cookies. Fonts and images are served from jumpfold.com itself, so loading the site does not contact any third party other than our hosting provider.
3. How we use it
- To contact you about the beta program: to offer a seat, to send setup instructions, and to ask for your feedback.
- To decide the order in which seats are offered, using your role and the platforms you use.
- To respond to your questions and requests.
- To keep the form working and protect it from automated abuse.
- To comply with legal obligations that apply to us.
We do not sell personal information, we do not use it for advertising, and we do not send marketing about other products. If we later want to use your information for a purpose not listed here, we will ask first.
Where data protection law requires a legal basis, we rely on your consent for beta communications, which you can withdraw at any time, and on our legitimate interest in running and protecting a small pre-release program.
4. Who we share it with
| Recipient | Purpose |
|---|---|
| Cloudflare, Inc. | Hosts this website and the database in which beta signups are stored, and provides the request logs described above. |
| Our email provider | Delivers the messages we send you about the beta. |
| Professional advisers and authorities | Only where required by law, to establish or defend legal claims, or to protect the rights and safety of people using the service. |
We do not share beta signup information with any other company, and we do not share it between beta participants.
5. How long we keep it
- Beta signup records are kept for as long as the beta program runs. When the program closes we will either ask you whether you want to keep hearing from us or delete the record.
- Deletion requests are completed within 30 days. See the data deletion policy for exactly what happens.
- Application logs are kept for up to 30 days.
- Backups of the signup database may hold a deleted record for up to 35 days after deletion, after which the backup itself expires.
- Email correspondence is kept for as long as needed to deal with the matter, and then for up to 24 months.
6. Your rights
Wherever you are, you can ask us to tell you what information we hold about you, correct it, delete it, give you a copy of it, or stop using it for a particular purpose. Write to info@jumpfold.com. We will respond within 30 days, and we may ask you to confirm the request from the email address on the record.
If you are in the European Economic Area, the United Kingdom or Switzerland, these rights are set out in the GDPR and its UK and Swiss equivalents, and you also have the right to lodge a complaint with your local supervisory authority. If you are a California resident, the California Consumer Privacy Act gives you rights to know, delete and correct, and to be free from discrimination for exercising them; we do not sell or share personal information as those terms are defined in that Act.
7. Cookies and tracking
This website sets no cookies and uses no tracking technologies. If that changes, we will update this policy and, where the law requires it, ask for your consent first.
8. Security
Connections to jumpfold.com are encrypted in transit. Signup records are stored in a managed database with access limited to the people running the beta program, under individual credentials. No method of storage or transmission is perfectly secure, and we will tell you promptly if we learn of a breach affecting your information.
9. International transfers
Our hosting provider operates globally and the beta signup database is stored in North America. If you are outside the region where your information is processed, it will be transferred there. Where the law requires it, transfers are made under standard contractual clauses or an equivalent recognised mechanism.
10. The Jumpfold application
This policy covers the website and the beta signup process. When the Jumpfold application is made available to beta participants, it will come with its own privacy notice describing how it handles your documents. The design principles it will follow are already fixed:
- Only folders, documents and browser links you explicitly select are ever read. Signing in does not capture content.
- Passwords, cookies, browser sessions and authentication tokens are never captured or transferred.
- Document content is encrypted in transit and at rest. The service uses keys it manages on your behalf so that your work can be recovered if you lose a device; it is not a zero-knowledge system, and we will say so plainly rather than imply otherwise.
- Operational logs contain identifiers and timings, not document names or content.
11. Children
This website and the beta program are for working professionals and are not directed at anyone under 18. We do not knowingly collect information from children.
12. Changes
If we change this policy we will update the effective date above and, for changes that matter to you, tell beta participants by email before they take effect.
13. Contact
Questions, requests and complaints: info@jumpfold.com.