Who we are
Tulip is a LaTeX writing and collaboration workspace, and an untitled.life product. This policy explains how Tulip handles information when you browse the website, sign in, work on projects or contact us.
For privacy questions or requests about your information, contact [email protected].
Information we handle
- Your account. Google sign-in provides your account identifier, verified email address, name and profile photo. We store these with your membership date. We also store profile information you choose to provide, such as your affiliation, and your account plan and quota settings. Tulip does not receive your Google password.
- Your work. Projects include source files, uploaded documents and images, project settings, notes, saved templates, comments, review proposals, version history, and the identity and time associated with changes. Uploaded PDFs and supported documents may have text extracted to support search and reading.
- Compilation. Server compilation, when available to your account, processes source and attachments and stores build results such as PDFs, auxiliary files and logs. Browser compilation runs on your device; it does not make an otherwise shared or server-saved project local-only.
- Sharing. We store collaborator email addresses, roles, invitations and ownership-transfer requests. An invitation may include the recipient’s email even if they have not created a Tulip account.
- Feedback and support. We store your submitted name, email, topic, subject, message and submission time, linked to your account when you are signed in. Feedback is stored in a private backend inbox, not published on the website.
- Operation and security. Servers handle technical request information, including IP addresses, request paths, response status and errors. We also record daily totals of authenticated API requests, writes, errors and server compile requests for account support and service operation. These totals do not contain source text, request bodies or search queries; they do not measure browser-only compilation or time spent editing.
Why we use this information
We use information to sign you in, save and recover your work, compile documents, synchronize collaboration, show authorship and history, deliver invitations, manage access and quotas, and respond to feedback or support requests.
We also use operational information to diagnose failures, prevent abuse and unauthorized access, and meet applicable legal obligations. Optional connections are used for the actions you request. The current service does not include advertising trackers or cross-site advertising cookies.
What collaborators can see
Sharing a project gives the invited people access to its files and project activity according to their role. Your name, profile photo and, where needed for access management, email may be visible to collaborators. Comments, proposals and history show who contributed and when.
Only the owner manages sharing and ownership transfers. Editors can edit, reviewers can comment and propose changes, and viewers have read-only access. Removing someone’s access stops future authorized access through Tulip; it cannot recall a file they already downloaded or copied. Project owners and collaborators should have permission to include other people’s information in their work.
Services that help Tulip work
Production project records are stored in PostgreSQL, and attachments and server build outputs in private S3-compatible object storage. Tulip’s hosting infrastructure currently runs on DigitalOcean. Authorized operators can access information needed to administer accounts, investigate problems and operate the service.
- Google authenticates your sign-in. Its handling of your Google account is described in Google’s privacy policy.
- DigitalOcean provides hosting infrastructure. See DigitalOcean’s privacy policy.
- Resend delivers project invitations and other emails sent through Tulip. Delivery involves the recipient’s email and message contents, including the inviter’s name, project name and invitation link. See Resend’s privacy policy.
Using online hosting, email or a connected service can involve processing outside your country. Contact us if you need information about your deployment’s processing location or safeguards. Links to publishers, videos and other external websites take you to services with their own policies.
Optional account connections
Where enabled, you can connect GitHub, Zotero, Mendeley or Dropbox. Their authorization screens describe the access being requested. Availability depends on Tulip’s provider configuration; connecting an account is optional.
Tulip stores the connected account’s identity, granted permissions and connection details, together with access credentials and, where used, refresh tokens. Credentials are encrypted on the server. Attaching a connection to a project requires an explicit owner action. Connecting alone does not import references, push commits or upload backups. A requested repository import, bibliography refresh, commit push or backup exchanges the relevant data with that provider.
Project collaborators do not receive your personal connection credentials. Disconnecting removes Tulip’s stored connection and linked project credentials, while preserving files already imported. You can also revoke Tulip’s authorization in the provider’s account settings. ReadCube currently uses file import rather than an account login connection.
Cookies and storage on your device
Tulip uses a sign-in cookie to maintain your session, with a lifetime of up to 14 days, and short-lived cookies for sign-in security. Administrative sign-in has a separate session. These cookies support authentication and access protection.
Your browser also stores editor preferences, walkthrough progress, public template metadata, downloaded editor and TeX assets, and cached PDF previews. Private PDF caches are scoped to your Tulip account and may include the source snapshot and source-to-PDF mapping used for that build. This storage makes reopening and compilation faster.
Signing out does not erase every local cache. Clear saved PDFs and TeX files in Account settings → Storage, or clear this website’s data in your browser. Clearing site data also removes local preferences and can require signing in and downloading assets again. On a shared device, sign out and clear site data before handing it to someone else.
Keeping and removing information
We keep account and project information while it is needed to provide your workspace, preserve collaboration and history, address support or security issues, or comply with applicable requirements. Archived projects remain stored. Deleting a file does not erase its earlier saved versions in project history.
Owners can delete their projects; collaborators can leave projects shared with them. A deletion removes the project from normal access, but an attachment can remain if another project, saved template or version still references it. Exports and copies held by other people are outside Tulip’s deletion controls.
Daily authenticated API activity totals are pruned to a rolling 90-day window. Other support, security and delivery records are retained according to their operational purpose; there is no single automatic deletion deadline for all records. For account deletion or a request covering information beyond the available project controls, contact [email protected]. Account deletion is currently handled by request, rather than a self-service button.
Your choices and privacy requests
You can edit your name and affiliation, manage active sessions, change project access, export project source, disconnect integrations and clear local caches using Tulip’s account and project controls. Your profile photo and verified sign-in email come from your Google account.
Depending on applicable law, you may have rights to access, correct, export or delete personal information, or to object to or restrict particular processing. Send requests to [email protected], including the account email and what you want us to address. We may need to verify your identity before providing or changing private information. We will explain any limits, including information needed for security, legal obligations or other people’s contributions.
You may also raise a concern with the relevant data protection authority where that right applies. If you received an invitation without signing up, you can contact us about the invitation and your email address.
Protecting your information
Tulip uses HTTPS, authenticated project access, role checks, private storage and encrypted integration credentials to protect the service. These protections do not make project contents end-to-end encrypted, and no online service can guarantee absolute security. Keep your Google account secure and share projects only with people you trust.
Report a suspected privacy or security problem to [email protected]. Please avoid including passwords, provider tokens or unnecessary sensitive data in feedback messages.
Changes to this policy
We update this page when data handling changes and show the revision date above. Material changes will be brought to users’ attention through an appropriate service notice. This policy should be read with our Terms of Service.
Questions about this page? Contact [email protected].