Glysten Privacy Policy
Last updated: 2026-11-10
1. Scope, and the one thing that decides everything else
This policy explains what personal information Glysten's software for businesses — Glysten Books, Glysten Construction, Glysten Sign and online payments (together, the "Service") — handles, and what we as the Provider do and do not see. It forms part of the Terms of Service.
Three other notices cover people this one does not: the Glysten Personal Privacy Notice, for anyone who uses Glysten Personal for their own finances; and the Signer Privacy Notice, for anyone a business sends a document to sign. Section 6 says, in brief, what the Service holds about the people a business deals with.
Almost every answer below depends on which deployment you have:
- Self-Managed Deployment — the Service runs on infrastructure you control. Your records, your users' accounts, and everything in them stay on your systems. We do not receive them, and we cannot see them. For that data you are the controller and we are not a processor of it at all; this policy then describes only our website and your dealings with us as a customer.
- Hosted Deployment — we run the Service for you. Your records are on infrastructure we control, so we hold that data and Sections 5 to 11 apply in full. You remain the controller of it; we process it on your instructions.
2. Who we are
Glysten Technologies, LLC, an Oregon limited liability company (the "Provider"), as in the Terms of Service. Contact details are in Section 14.
3. Our website
Our public website describes our products. Its one form is for starting a free month of them. It takes your email address and sends a six-digit code to it. Once you have entered the code, it takes your name, your company's name, a username and a password, the products you chose, and your acceptance of the Terms, and opens your account (Section 5 says what an account keeps). You are then sent to our payment processor Stripe's own checkout page to give a payment card. That page is Stripe's, not ours: the card's details go to Stripe and never reach us, and Stripe may set cookies of its own there, under Stripe's privacy policy. An email address whose sign-up is never finished is removed from the sign-up's record once that sign-up expires.
To stop the form being flooded, the Service counts requests against a keyed hash of your IP address, of the network it belongs to, and of the email address you gave. Those counts are kept in our database, as the hash and not the address, and each is deleted after about an hour. Inquiries sent through the form the site had before sign-up opened are kept as sign-up inquiries (Section 10).
To see how fast our pages and screens are, your browser tells us, when you leave a page, which page or app screen it was, how long it took to show, how far it moved while loading and how long it took to answer a click or key press, and, for a slow one in the app, the name of the button or the kind of field and of our script that was busy, never the key or anything typed. We keep only daily counts of these, and a slow one's longest time, for 60 days. Your IP address is used only to limit how often one address may send, held in memory for a minute and never written; we never keep it, your browser details, a cookie or who you are. This runs only on our own site.
To count our public site's visitors, the server keeps, for each visit, a scrambled code made from your IP address and browser details with a key that lasts one day and is then deleted; once it is gone, a code can no longer be matched to an address or to another day (a backup our host takes that day still holds that day's key until the host overwrites it). The codes, each with the first page it opened, are kept two days, then only daily counts by page. No address, browser details or cookie is stored, no cookie is set, and nothing is shared. A browser sending Global Privacy Control is counted as a page view only, with no code; Do Not Track is not read. This runs only on our own site.
Otherwise the site collects nothing from you: it runs no advertising or tracking, only counts its visitors and measures its own speed (above), and its own pages make no requests to anyone else's servers — its fonts are served from our own. The one cookie it carries is set by our hosting provider's network, not by us (Section 4).
4. Cookies
The Service sets two cookies for the people who use it, and our hosting provider's network sets a third. All three are strictly necessary to use the service.
- A session cookie (
__Host-lw_session) keeps you signed in, for up to 14 days. - A remembered-device cookie (
__Host-lw_device) is set only if you tick "remember this device" after entering a sign-in code, and lets this browser skip the code for 14 days. Changing your password forgets every remembered device, and the Account screen lists them so you can forget any one.
Both are HttpOnly (no script can read them), SameSite=Strict (never sent with a request from another site) and Secure over HTTPS.
__cf_bmis set by Cloudflare, which our hosting provider, DigitalOcean, runs in front of the site. It is set on every page, including this public site, helps tell people from automated traffic, and expires after 30 minutes. The Service never reads it.
Two pages are opened by people who are not our customers:
- The signing page sets one cookie,
gl_sign, that keeps a signer recognized for up to an hour of inactivity, sent only to that signer's own link. It isHttpOnly,SameSite=StrictandSecurelike the others. - The payment page loads Stripe's code, so that card and bank details are typed into Stripe's own fields. Stripe may set cookies of its own there, to prevent fraud, under Stripe's privacy policy. No other page of ours loads Stripe's code.
We set no advertising, analytics, or tracking cookies anywhere, so there is nothing here to opt out of.
5. What the Service stores about the people who use it
Whether this reaches us depends on your deployment (Section 1). In either case, an installation stores:
| What | Why |
|---|---|
| Username (an email address) and display name | To identify who is signed in and label their entries |
| A hash of the password — never the password itself | To sign you in |
| Two-factor secrets and recovery codes, if enabled | To protect the account |
| Role, and per-entity access grants | To decide what each person may see |
| Session records: a token hash, IP address, browser user-agent, timestamps | To keep you signed in and let you end a session |
| Known sign-in locations: IP addresses, when first and last seen, any label | To recognize an address you have signed in from before, so that an installation set to hold sign-ins from new addresses holds only those |
| Held sign-in attempts: IP address, browser user-agent, time, outcome | Only where an installation holds sign-ins from new addresses: to let an account owner approve or refuse one |
| Failed sign-in counts and lockout times | To slow down password guessing |
| The countries you have signed in from, where the country is known | To tell an account's owners when somebody signs in from a country they have not used before |
| Security alerts: what happened (a sign-in locked by wrong passwords, a full copy of a book downloaded, an AI app reading a great deal, a sign-in from a new country), whose sign-in it was, the IP address and its country where known, and when | To email the account's owners about unusual activity as it happens, and let them look back at it. A burst of failed sign-ins from one address is reported to us instead, with the address and the count and nothing else |
| An audit log of actions taken in the books | So an account owner can see who changed what |
| Each acceptance of these terms: which revision, when, IP address, browser user-agent | To show who agreed to which terms |
| Your choice about letting the Help assistant read the books, and when you made it | So it reads them only if you said it may |
| How many questions you asked the Help assistant each day, and what they cost | To apply usage limits |
| Keys you create for AI apps — stored only as a hash — and when each was last used | So you can see every connection and revoke it |
| Passkeys, if you add one: the public half of the key, the site it was made at, a label you give it, and when it was made and last used | To confirm it is you before a bank is connected. The private half never leaves your device |
| A keyed hash of the fingerprint our payment processor gives the card or bank account that started a free month, with the account and subscription it started | So that a free month is given once per card. It is not the card number, which never reaches us. It is kept after the account closes, with no end date, so that closing an account does not free the card for another free month |
| What you send in the Feedback box: your words, what kind of thing it is (a problem, an idea or something else), the screen you were on, the company you had open (its name) and the record on screen (its kind and number; the picture of the screen shows its name), the release, your browser and window size, a picture of the screen you were on with every number written in digits blurred (a chart keeps its shape) and any code or key shown for copying left out, any picture you attach, your name and sign-in email address, and whether we may email you about it | So we can fix what you report, and reply if you said we may. The pictures are removed 90 days after the item is marked done or archived, and your name and email address a year after you sent it; the words stay until we delete them. We read what you send with the help of an AI assistant (through an AI provider, named below), which sorts it and helps us fix what you report; it is not used to train any AI |
| The errors your browser meets in our code while you use the Service: which screen, the kind of error, our script and line, and for the browser's own errors a short message with anything that could be data taken out; with the account it happened in. Never the page's text or anything you typed | So we can find and fix what broke. We keep the latest 200 across every account, none older than 30 days, and an account's are deleted when it closes |
| A picture of your signature, if you save one in Glysten Sign, kept encrypted and readable only by you; and, each time you choose to print it on a document you send (such as a proposal), a copy kept encrypted with that document as sent | So it can be printed as yours only when you send something and say so, and so every later copy of a document you sent matches the one that went. Deleting yours stops it being printed on anything after; documents already sent keep it as they were |
The Service finds which country an IP address is in without sending the address to anyone: it looks it up in a published list of address ranges kept on our own server. IP Geolocation by DB-IP (https://db-ip.com), licensed under CC BY 4.0.
Apart from the speed measure in Section 3 and the errors above, both only in the Hosted Deployment, the Service sends no usage analytics or telemetry to us. What its AI features send, and to whom, is in Sections 8 and 11.
6. Personal information about other people, inside your records
This one deserves saying plainly. Your records can contain personal information about people who are not our users and have never heard of us — customers, clients, vendors, subcontractors, tenants, employees, partners and shareholders, and the people you send documents to sign. Depending on what you use, that can include names, addresses, bank transaction detail, receipts and statements you attach, and taxpayer identification numbers, including Social Security numbers — for partners and shareholders if you produce Schedules K-1, and for the people you pay if you record W-9s to prepare Forms 1099.
Taxpayer identification numbers from W-9s are held apart from the rest of the books, shown on screen only as their last four digits, and used in full only to build a 1099 file. They are never sent to an AI provider or to an AI app you connect. A record of each 1099 file Glysten Books prepares is kept permanently, as a tax record.
- You decide what goes in, why, and how long it stays. You are the controller of it, and you are responsible for having a lawful basis to hold it and for meeting your own obligations to those people.
- In a Self-Managed Deployment we never receive any of it.
- In a Hosted Deployment we store it on your behalf. We do not use it for any purpose of our own. We access it only to operate the service, fix a fault, provide support you have asked for, or comply with the law.
Given what this data is, keep the access grants in the Service narrow, and treat an export of your records as the sensitive document it is.
6A. Your clients and subcontractors, in Glysten Construction
Construction holds your clients' names, email addresses, phone numbers and addresses, and your subcontractors' and vendors' names, contact details, license and contractor-board numbers, insurance and bond dates, the certificates you upload, and your notes. It holds no bank details and no taxpayer identification numbers of its own; it reads a vendor's name and contact details from Glysten Books, never a W-9. Plans, photos and documents you upload are kept with the job, and anything you uploaded keeps whatever the file itself contains. Proposals, change orders, invoices and lien waivers are emailed to the people you choose, in your business's name, and replies go to you. Construction's Help assistant does not read your jobs, and an AI app you connect cannot reach Construction at all.
6B. The people you send documents to sign
To let someone sign, the Service keeps their name and email address, what they put into the document (their signature, typed or drawn, initials, dates, text and ticked boxes), when they opened, signed or declined and their reason for declining, and, at each step, their IP address, their browser's description of itself, and how they were recognized. The completed copy carries a certificate listing each signer's name, partly hidden email address, time of signing and IP address, and it is emailed to every signer and to you. A signer needs no account, and the Signer Privacy Notice tells them all of this. No AI reads the documents or the signing record.
6C. The people who pay you online
When someone pays you online, the payment is made on your own Stripe account (Terms, Section 32). Their card or bank details go to Stripe and never reach us. The Service keeps what it needs to record the payment: the payer's name and email address, the amount, fees and date, the method, the card brand or bank name, and the last four digits. It emails the payer a receipt.
7. How we use information, and why
- To provide, operate and secure the Service — our contract with you, and our legitimate interest in a service that works and is not broken into.
- To authenticate people and detect unauthorized access, including emailing an account's owners when something unusual happens in it — our legitimate interest in security, and yours.
- To take payment and keep records — our contract with you and our legal obligations.
- To answer questions you ask the Help assistant, and — only where you have turned it on — to read your books to answer them (Section 11).
- To answer support requests you send us.
- To send you service messages about outages, security, or changes to these terms. These are not marketing and you cannot opt out of them while you hold an account.
We do not sell personal information, we do not share it for cross-context behavioral advertising, and we do not use your books to train artificial-intelligence or machine-learning models. We have never done so.
8. Who else is involved
- Cloud hosting (for example DigitalOcean), for a Hosted Deployment only. They store the data; they do not use it. The encrypted copies we keep for recovery are stored with Dropbox. The key never leaves us, so Dropbox cannot read them.
- Our own mail. A message you send to a glysten.co address passes through Cloudflare's email forwarding and is kept in our Google mailbox.
- An AI provider — today Anthropic, or Google for an installation set up for Gemini — when you use an AI feature, and when we read what you send in the Feedback box. It receives what that feature sends (Section 11), or the Feedback item. On a Hosted Deployment we use its paid, commercial service, under terms that do not permit it to train its models on what we send. On a Self-Managed Deployment the provider is yours to choose, under your agreement with it.
- An AI app you connect to your books, such as Claude or ChatGPT. It reads what you can see and sends it to its own provider under your agreement with that provider, not ours.
- A payment processor, which handles subscription payments under its own terms. We do not store full card numbers.
- An email service — today Resend — for the email the Service sends: sign-in codes, invitations, security alerts, the note that your account is ready, and each request to try one of our products, which is sent on to us by email; and, for you, the invoices, proposals, change orders, lien waivers, receipts and documents for signature you send, the signing codes, and the completed signed copies, with the documents attached. It receives the address each message goes to and what the message says. On a Self-Managed Deployment it is one you set up, under your own agreement with it, or none.
- Stripe, for online payments to you, on your own Stripe account and under Stripe's agreements with you (Section 6C).
- A time-stamping service, only where one is used to date a completed signed document: it receives a fingerprint of the signature, never the document or anything about the signers.
- Plaid, only if you connect a bank through it. You sign in to your bank on Plaid's pages or your bank's own, never ours, so we never see your bank password. Plaid passes us your accounts' names, last four digits and balances, and their transactions, and handles your data under its own privacy policy. Read it before you connect an account.
- SimpleFIN Bridge, only if you connect a bank feed through it. Your bank transaction data passes through SimpleFIN under their privacy policy. Read it before you connect an account.
- Professional advisers, or a successor in a merger or sale of the business. A buyer would be bound by this policy for information collected under it.
- Law enforcement or a regulator, where we are legally required. If we are compelled to disclose data belonging to a Hosted Deployment customer, we will tell you unless the law forbids it.
A current list of subprocessors is available on request.
9. Where information is held
For a Hosted Deployment, in the United States. We will not move Your Data outside the United States without notice to you.
10. How long we keep it
- Sign-up inquiries: up to two years, then deleted.
- Account and billing records: for the life of the account, and afterwards for as long as we need them for tax, accounting and legal purposes — generally seven years.
- Session, known-IP, sign-in country and held-sign-in records: these age out automatically; sessions expire, and the rest are kept while they are useful for security.
- Security alerts: one year, then deleted.
- Acceptances of these terms: kept as a legal record, including after an account is closed or a person is removed, with the account records above.
- Help assistant conversations: not kept by the Service's server at all. Today's conversation is kept in your own browser, and the daily counts of questions and their cost are kept with the account records.
- 1099 files Glysten Books prepared: kept permanently, as a tax record.
- Documents sent from Glysten Construction are kept exactly as they were sent, and a job is archived rather than deleted, for as long as the business it belongs to is kept. Deleting a business removes its Construction records.
- Documents sent for signature, and their signing records, cannot be changed or deleted once sent. They are kept, even if the business they belong to is deleted, until your account closes.
- Your records, in a Hosted Deployment: for as long as your account is open. If your subscription ends, the account becomes read-only and its records stay where they are; nothing deletes them on a schedule. They are deleted when we carry out a request to close the account. Two things are kept when an account's records are deleted: the audit log of actions taken in the books, as the record of who changed what, and the record of each 1099 file prepared, as a tax record about the people named on it. Copies in backups, where backups exist, are not deleted one by one: they go when the backup that holds them is overwritten in the ordinary course.
- Your records, in a Self-Managed Deployment: entirely up to you. We hold no copy to delete.
11. Automated decisions, and where a person is still required
The Service automates a good deal, so it is fair to ask what it decides by itself.
- Categorization rules and payee matching suggest an account for a bank transaction based on how you have coded that payee before. A suggestion is only ever pre-filled into a dropdown.
- Duplicate detection flags a transaction that looks like one already in your books. It flags; it never discards.
- Tax computations total figures from entries you made and place them on a form. They are arithmetic, not judgment.
- A client's signature on a proposal marks it accepted in Glysten Construction and creates the client as a customer in your books. It posts nothing.
- The Help assistant answers questions using an AI provider. Without your books it is sent the Service's help text and your question. With your books — which is off until you turn it on for yourself — it is also sent the entries, figures, names and notes it reads to answer you, never more than your own access allows; a picture or document you attach goes with the question it is attached to. It can draft entries and propose changes, but each one waits for you to approve it.
- Teaching Glysten Books a statement layout sends the AI provider an outline of the statement page in which names, addresses, account numbers and transaction descriptions are blanked; figures, dates and headings are sent as printed.
Nothing in the Service posts to your books, files anything, or moves money on its own — not the rules, and not the AI. Every one of those is a person clicking a button. We do not make automated decisions that produce legal or similarly significant effects about anyone — no credit scoring, no eligibility decisions, no profiling for advertising — and we do not use your books to train artificial-intelligence or machine-learning models. The Terms of Service, Section 13, set out the AI features in full.
12. Security
For a Hosted Deployment we use commercially reasonable safeguards, including encryption in transit and at rest, access controls, and limiting staff access to those who need it. Passwords are stored only as hashes. A second step is required at every sign-in, for everyone: a code sent by email, or one from an authenticator app. A person may require the authenticator app for their own sign-in.
No system is perfectly secure. If we become aware of a breach affecting your personal information we will notify you without undue delay, and notify regulators where the law requires.
For a Self-Managed Deployment the security of the machine, the database and the backups is yours. The Service gives you the tools — hashed passwords, two-factor, held sign-ins, per-entity access, an audit log — but it cannot secure a server you have left open.
13. Your rights
Depending on where you live, you may have the right to know what personal information we hold about you, to get a copy, to correct it, to delete it, to limit how we use it, and not to be discriminated against for exercising any of those rights. California residents have these rights under the CCPA as amended by the CPRA; several other states provide similar ones.
You may also withdraw consent where we relied on it, and complain to a data protection authority in the place you live if you think we have handled your information badly. You do not have to come to us first, though we would rather hear from you and fix it.
We do not sell or share personal information for advertising, so there is no opt-out to offer.
To exercise a right, contact us at Section 14. We will verify your identity before we act, and respond within the time the law allows.
If your information is in someone else's records — you are a customer, client, vendor, subcontractor, tenant or partner of one of our customers, or somebody who signed a document or paid one of them — then that customer, not us, controls it, and you should contact them. If you contact us about a Hosted Deployment we will pass your request on to them. In a Self-Managed Deployment we have no access to their books and cannot help beyond telling you so.
14. Contact
Privacy questions and rights requests: [email protected].
Security concerns, including a vulnerability you have found: [email protected].
15. Children
The Service is business software and is not directed at children. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us information, tell us and we will delete it.
16. Changes
We may update this policy. For material changes we will email you at least fifteen days before they take effect, and the "Last updated" date above tells you which revision this is. Prior revisions are available on request.