Privacy policy

Who is responsible

ROOTLESS ENTREPRENEUR LLC, identification number 001435285, of 33 Valleywood Rd, Hopkinton, MA 01748, USA, decides how and why your data is used. In European terms, we are the data controller. Write to support@implements.app about anything on this page.

What we collect

Your account

Your email address, a name if you give one, and an encrypted form of your password if you set one, with the date you last changed it. We never see the password itself. If you add a passkey, we keep only its public key, which cannot sign anyone in by itself; your face or fingerprint never leaves your device. With each passkey we note which password manager holds it, the device and browser you added it on, and the tool it last logged you in to, so your account page can tell them apart.

If you join before confirming your email

You can join and pay straight away. Until you follow the link we email you, your account is a guest account: the address you typed waits on it, unconfirmed, and becomes the account's address once you follow the link. Meanwhile we give that address to Stripe so your receipts reach you.

Where you're logged in

For each session, the device and browser it runs in (read from what your browser tells every website it visits), whether it is a tool installed on your home screen, and when it was last active. Your account page lists them so you can log out anywhere you don't recognize. Each note is removed after its session ends.

Your preferences

The color theme you chose and when you chose it, whether the tools show the pegboard (the dotted background) and when you chose that, the tools you pinned to your board and when you last opened each, for Recent, and the settings you choose inside a tool, such as the Unit Converter's pinned units, how your invoices look, or the sample polls you deleted. They are kept with your account so they follow you from device to device, including into installed tools.

If you sign in with Google

Google tells us your email address, your name, a link to your Google profile picture, and an identifier for your Google account. They are kept with your account, and your name becomes the name on it unless you gave one yourself. The picture is not shown anywhere. We never receive your Google password or anything else in your Google account.

Your subscription

Whether it is active, which plan, when the period ends, and the identifiers Stripe gives us. We never see or store your card number. That goes straight to Stripe.

Where you heard about us

If you answer the optional question after paying: which answer you picked (search, an AI assistant, a friend, a shared link, social media or other) and when. It is kept with your account and copied to your customer record at Stripe.

The page you started from

When you start a subscription from a tool's page, the home page or the pricing page, that page's name (such as tools-pdf-kit) is carried in the address to checkout and kept with the subscription's record at Stripe. Nothing else about your visit goes with it, and no cookie is set for it.

What you put in the tools

Trips, expenses, polls, to-do lists, forms, invoices, editable QR codes and anything else you save, including details you enter about other people, such as a name, an address or a way to pay them.

Answers to a form

When someone answers a form made with Forms, we keep what they typed, and when they sent it, for the person who made the form. That person decides what the form asks, and the answers stay until they delete them, the form or their account. We keep nothing else about whoever answered: no account, and their IP address only in the hashed counts that stop abuse.

Scans of an editable QR code

How many times each of your editable codes was scanned on each day. Nothing about who scanned it: no address, no device and no location.

A logo on your invoices

If you add one: the image and its file name. Your device draws the image again before sending it, which leaves hidden details, such as where a photo was taken, behind. It is kept privately, printed on your invoices' PDFs, and sent to the people you share an invoice link with when they download it. Removing it, or deleting your account, deletes the file.

Support messages

What you write to us, the address to reply to, and when you sent it.

Problem reports

If you use Report a problem in a tool: what you write, the tool and screen you were on, the version of the app, your device and browser, whether the tool was installed and online, the address to reply to, and your account if you were logged in. Nothing from inside the tool, and no error messages. A picture of the screen goes only if you add one; it comes to us by email and isn't kept in our database.

Reports of a shared page

If you report a page someone shared, from the foot of the page, from a QR code's + page or from Support: the page's address, what you picked as wrong with it and anything you add, an address to reply to if you give one on Support, when, a hashed form of your IP address, and your account if you were logged in. It comes to us, never to whoever shared the page.

Technical data

Server logs, which hold the pages requested and times. Where we count requests to stop abuse, your IP address is hashed before it is stored, so the stored value cannot be turned back into an address.

Error reports

When something breaks, a report of what went wrong: the error, where in our code it happened, the page it happened on, your browser and operating system, and the pages and requests just before it. Reports do not include your IP address, your cookies, what you typed or clicked on, or anything you saved. Links that act as a key, such as a share link to a form or an invoice, have that key removed before the report is sent.

Page views and speed

When a page loads, Cloudflare Web Analytics notes the page's address (without anything after a ?), your browser, operating system and type of device, your country, and how long the page took to load. It sets no cookies, stores nothing on your device and does not follow you to other sites. We use it to see which pages are slow.

There is no advertising, no tracking pixels and nothing that follows you around the web. Nothing records what you do on a page: no session recordings and no click tracking. Apart from the page speed measurement above, the only report that leaves your browser is the error report, and only when something breaks. We do not sell or share your data for anyone's marketing.

Why we have it, and on what basis

• To run the service: your account, your content, your subscription and your preferences, and the list of where you're logged in that keeps your account safe. This is what performing our contract with you requires.
• To take payment and meet tax rules: a legal obligation, and our contract.
• To answer support messages: our legitimate interest in helping you, and our contract.
• To keep the service standing up, through rate limits and logs: our legitimate interest in preventing abuse.
• To find and fix what is broken or slow, through error reports and page speed measurement: our legitimate interest in a service that works.
• To know which pages and channels bring members, through your answer to the optional question after paying and the page a subscription started from: our legitimate interest in knowing what works. Neither needs a cookie.
• To email you about the service, such as confirming your address, a sign-in link and code, resetting a password, or a change to these documents: our contract, and our legitimate interest in telling you about changes that matter.

Who else sees it

Only the companies that make the service work. Each one handles data on our instructions under a contract, and none of them may use it for their own purposes.

• Supabase hosts the database and the login system: your account and everything you save.
• Stripe takes payments: your card details go directly to them, along with your email address and the identifiers linking a payment to your account, the page your subscription started from, and your answer to where you heard about us if you gave one.
• Brevo sends email: your address and the contents of the message.
• Amazon Web Services hosts the server the site runs on.
• Cloudflare sits in front of that server. Every request passes through it, including your IP address, so it can block attacks and serve the files that never change from somewhere close to you. It also measures page speed, as described above. It sets no cookies.
• Sentry receives the error reports described above, and stores them in the United States, like the rest of the service.

If you choose to sign in with Google, Google is involved too, but as a separate company rather than one working for us. It learns that you signed in to implements, and what it does with that is covered by Google's privacy policy. You can remove implements's access from your Google account settings at any time.

People you send a Date Poll, Forms or Trip Split link to see the first word of the name on your account, as in “Maya asks” or “Shared by Maya”, when you have set a name under Account. Nothing else about your account shows on those pages.

We may also disclose data where the law requires it, or to establish or defend a legal claim.

Where your data is

We are in the United States, and the service runs on servers there. If you are in the European Economic Area or the United Kingdom, using implements means your data is transferred to the United States. Where that transfer needs a legal safeguard, we and our providers rely on the European Commission's standard contractual clauses or an equivalent mechanism. Each request first reaches Cloudflare at one of its data centers near you, which may be outside the United States, on its way to our server.

How long we keep it

• Your account and content: until you delete your account. Deleting is immediate, and takes your profile, your subscription records in our database, and everything saved in every tool with it.
• Deleted items inside a tool: a deleted to-do is kept for up to 30 days so a device that was offline cannot bring it back, then purged. A deleted invoice stops showing at its link the moment you confirm Delete, and goes for good once the few seconds to Undo have passed or, if the app closed before then, in a clean-up from ten minutes on. A deleted trip, form or editable QR code goes once those seconds have passed, or as the app closes. If that last request is lost on the way, the device sends it again the next time you open a tool or log out, and until then its link can keep working.
• Payment records: Stripe keeps invoices and payment records after you delete your account, because tax and accounting rules require it, and with them the page your subscription started from and your answer to where you heard about us. This is the one thing deletion does not remove.
• Support messages, problem reports and reports of shared pages: kept so we have a record of what was asked, with the link to your account removed when the account is deleted.
• Where you're logged in: each session's note is removed after the session ends, and all of them with your account.
• Rate limit counters: hashed and deleted within a day.
• Error reports: deleted automatically by Sentry within 90 days.

Your rights

Wherever you live, we offer everyone the same rights: to know what we hold, to get a copy, to have mistakes corrected, to have your data deleted, and to object to how we use it. If you are in the EEA or the UK, these are your rights under the GDPR.

• Deletion is self-service. Open your account page and use Delete account. It happens at once.
• For a copy of your data, or anything else, write to support@implements.app. We answer within 30 days.
• If you are in the EEA or UK and think we have handled your data badly, you can complain to your local data protection authority.

Cookies and storage on your device

We use no advertising or analytics cookies, so there is no consent banner to click through. What we do store is needed for the service to work at all:

• Session cookies, set when you log in, so the site knows it is you. They cannot be read by scripts in the browser, and they are removed when you log out.
• A few small cookies that scripts cannot read either: sign_in_email, the address this browser asked a sign-in link for, kept a day so an expired link can be sent again; session_noted, which session's browser we have already noted for Where you're logged in; and password_reset, which for 30 minutes after you follow a password reset link lets you choose a new password without the old one. All three are removed when you log out.
• A theme cookie, theme, with the color theme chosen on this device and when, so pages open in it without a flash. It is kept a year and stays after you log out, since it holds nothing about you.
• A pegboard cookie, pegboard, with whether the tools show the pegboard (the dotted background) on this device and when that was chosen, so a tool opens as chosen without a flash. It is kept a year and stays after you log out, since it holds nothing about you.
• Local storage, for things that make the app usable: the last answer about whether your subscription is active (so an installed tool opens offline), a count of changes not yet synced, a note that this device was logged in (so a tool can say if you were logged out from another device), whether you dismissed the install prompt or the suggestion to add a passkey, which name you chose on a poll or a trip someone shared with you, a copy of the settings you choose inside the tools, so they open without waiting, and a note of a delete sent as the app closed, until it reaches us.
• Session storage, which the browser keeps for that one tab and lets go of once the tab is closed for good: work you haven't saved yet in a poll you are making or dates you are adding in Date Poll, and in a form or an invoice you are editing, so it comes back after a reload or a trip to your board. Making the poll, adding the dates or saving clears it.
• A local database and offline cache for tools that work without a connection, such as the To-do List, plus pages the app has cached for offline use. The plain QR codes you download are kept there too, so you can open one again; they carry their own information, a Wi-Fi password among it, and never leave the device. So is the signature you draw in PDF Kit, for the next time you sign; it never leaves the device either, and Clear deletes it. Doc Scanner keeps the photos and pages of a scan there until you start the next one, and they never leave the device. A problem report written offline waits there until it can be sent. PDF Kit notes the last tool you used and how many files it had, never the files, so your board can offer to pick up where you left off.

Logging out clears all of it on that device except the theme and pegboard cookies. Stripe sets its own cookies on Stripe's pages when you pay; that is covered by Stripe's privacy policy.

Security

Traffic is encrypted in transit. Passwords are stored only in hashed form, by Supabase Auth. Access to your rows in the database is enforced by the database itself, not only by the app. Payment details never touch our servers. No system is perfectly safe, and we do not claim otherwise; if a breach ever affects you, we will tell you and the relevant authority as the law requires.

Children

implements is not meant for children under 13, and we do not knowingly collect their data. If you believe a child has given us data, write to us and we will delete it.

Changes

If we change this policy in a way that affects you, we will email subscribers and update the date at the top before it takes effect.