Privacy Policy
Effective date: August 20, 2026 Last updated: October 12, 2026
This Privacy Policy explains how Spej Corp ("Spej", "Plooms", "we", "us", or "our") collects, uses, discloses, and protects information in connection with the Plooms websites at plooms.ai (including per-customer subdomains such as yourcompany.plooms.ai and me.plooms.ai), our applications, and our services (together, the "Services").
Plooms is a private, single-tenant AI workspace: chat, document and application creation, connectors to your own accounts, and a personal or organizational knowledge graph, all grounded in what you and your organization actually know. Privacy is a core design goal of the product, and this policy describes how that works in practice.
If you use Plooms through an organization (your employer or another entity that provides you access), that organization is the controller of your workspace data and its own privacy policies and agreements also apply. For questions about how your organization uses Plooms, contact your administrator.
1. A note on how Plooms is built
Two design facts shape everything below:
- Single-tenant and per-user isolation. Each customer runs in an isolated environment, and within it each person's chats, files, and knowledge graph are private to them unless they explicitly share. We do not commingle one customer's data with another's.
- Your content is not used to train AI models. When Plooms uses AI to answer you or generate a document, your content is sent to our model-serving provider only to produce that result. That provider does not retain your content after the request and does not use it to train models. We do not use your content to train, fine-tune, or improve any model.
2. Information we collect
a. Information you provide.
- Account information — your name, email address, and the credentials you set (we store passwords only as salted hashes and require two-factor authentication).
- Content you create or upload — your chats and prompts, documents, spreadsheets, presentations, images, and files you upload, and the projects, agents, and "skills" you configure.
- Billing information — for paid plans, your subscription and payment records. Card details are handled by our payment processor (Stripe) and are not stored on our servers.
- Support and communications — messages you send us.
b. Information from accounts you connect (connectors). If you choose to connect a third-party account — such as Google Workspace, Microsoft 365, Box, Slack, or Microsoft Teams — Plooms reads only the specific mailboxes, labels, folders, files, sites, or channels you select — and, if the account has a calendar, the events on it when you ask about your schedule or one of your events in a chat, which are read at that moment and not kept. Connections are per-user and opt-in, the access you grant is revocable at any time, and stored access tokens are encrypted at rest. We ingest only what you choose; we do not access anything you have not authorized.
c. Information we collect automatically. When you use the Services we collect standard technical and usage data such as IP address, device and browser type, log and diagnostic data, and events needed to operate, secure, and meter the Services (for example, to enforce prepaid usage limits). We use strictly necessary cookies and similar technologies to keep you signed in and secure.
On our public websites only — plooms.ai and admin.plooms.ai — we also measure aggregate page views through Cloudflare Web Analytics. It sets no cookies, does not fingerprint your device, and does not follow you across sites; it records only aggregate visit counts and the general referrer and country of a visit. It does not run on the application hosts where your content is stored and processed, and it never has access to your content or to anything from a connected account.
We do not knowingly collect information from anyone under 18. The Services are not directed to children.
3. How we use information
We use information to:
- provide, operate, secure, and maintain the Services;
- build and maintain your personal or organizational knowledge graph and answer your questions with provenance;
- generate the documents, images, video, applications, and other outputs you request;
- process payments, meter usage, and administer your subscription and prepaid wallet;
- authenticate you, prevent fraud and abuse, and protect the security of the Services and our users (including our automated fleet-defense system, which inspects security-relevant signals such as request metadata to detect and stop attacks);
- provide support and respond to you; and
- comply with law and enforce our agreements.
AI processing. To answer you or create an artifact, relevant content is sent to our model-serving provider to generate the result and returned to you. As stated above, that content is not retained by the provider after the request and is not used to train models, and we do not use your content to train models. When you enable web search for a chat, your query (not your private data, unless you include it) is sent to a search provider to retrieve results.
We do not sell your personal information, and we do not use your content or connected-account data for advertising.
4. How we share information
We share information only as follows:
- Service providers (subprocessors) who process data on our behalf under contract, limited to what they need to perform their function:
- Microsoft Azure — cloud hosting and infrastructure;
- Cloudflare — DNS, content delivery, DDoS protection and load balancing for our public websites (plooms.ai and admin.plooms.ai), and the cookieless page-view analytics described in Section 2(c). Cloudflare does not serve the application hosts where your content is stored and processed, and receives no connector content;
- Stripe — payment processing;
- Resend — transactional email;
- Sentry — error and performance monitoring (configured to scrub personal data);
- DeepInfra — AI model inference and text embeddings (does not store request content after the request, except generated images, which it keeps briefly; trains on nothing).
- Your organization, if you access Plooms through one (your administrator can manage your account and access workspace data per your organization's policies).
- At your direction, when you share an item, invite a collaborator, or authorize an agent or connector to send a message or write to a connected service.
- Legal, safety, and business transfers — to comply with law or valid legal process, to protect the rights, safety, and security of Plooms and its users, or in connection with a merger, acquisition, financing, or sale of assets (subject to this policy).
5. Data retention and deletion
We retain your information for as long as your account is active and as needed to provide the Services, then delete or de-identify it within a commercially reasonable period, unless a longer period is required by law or to resolve disputes and enforce agreements. Security and audit logs are retained on a rolling window (currently up to 90 days for detailed security event records). You can delete individual content within the product, and you can delete your account and associated data as described below and in Section 7.
Deleting connected-account data. When you disconnect a connector you choose what happens to what was already brought in. If you ask us to delete it, we remove it everywhere it was stored — the extracted text and its search index, the stored copies of any files, and the entries derived from it in your knowledge graph. It stops appearing in answers immediately, and the underlying records are erased shortly afterwards. If you would rather keep it — for example because you are reconnecting an account whose sign-in expired — we keep it and only the connection is removed.
Deleting your account. If you have a personal Plooms account, you can delete it yourself from Profile → Delete account, after confirming your password. Your access ends immediately — every session is signed out and every connector is disconnected and revoked at the provider — your subscription is cancelled, and everything that is yours (chats, documents, memory, files, artifacts and connected-account data) is then erased from our systems, typically within minutes. If your account is provided by an organization, your administrator removes it; you can also email [email protected] to request deletion of any account and its associated data. We keep only what the law requires us to: billing records held by our payment processor, and an anonymous record that an account existed and was deleted.
6. Security
We use administrative, technical, and physical safeguards designed to protect information, including single-tenant isolation, encryption of data in transit and of stored credentials/secrets at rest, hashed passwords, mandatory two-factor authentication, least-privilege access, network hardening, and continuous automated threat monitoring and response. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
7. Your rights and choices
Depending on where you live, you may have rights to access, correct, delete, restrict or object to certain processing of, or port your personal information, and to withdraw consent. You can exercise many of these directly in the product (edit your profile, delete content, disconnect connectors, and — for personal accounts — delete your account) or by contacting us at [email protected]. We will not discriminate against you for exercising your rights.
California residents (CCPA/CPRA). You have the right to know what personal information we collect and how we use and disclose it, to request access and deletion, and to correct inaccurate information. We do not sell or "share" (as defined for cross-context behavioral advertising) your personal information. You may exercise these rights, including through an authorized agent, by emailing [email protected].
EEA/UK residents (GDPR/UK GDPR). Where applicable, our legal bases for processing are performance of our contract with you, our legitimate interests in operating and securing the Services, your consent (for example, to connect an account or enable web search), and compliance with law. You have the rights described above and may lodge a complaint with your local supervisory authority. Where we act as a processor for a business customer, we process personal data on that customer's documented instructions under a data processing agreement.
8. International data transfers
We are based in the United States and may process information in the United States and other countries where we or our service providers operate. Where required for transfers of personal data from the EEA, the United Kingdom, or Switzerland, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses.
9. Third-party services
The Services let you connect and interact with third-party services (for example, Google, Microsoft, Box, Slack). Your use of those services is governed by their own terms and privacy policies, and their handling of your data is their responsibility. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements: we use Google user data only to provide and improve the features you connect, we do not transfer or sell it except as needed to provide those features or as required by law, and we do not use it for advertising or to develop, improve, or train AI or machine-learning models.
10. Google user data
This section describes, specifically, what Plooms does with data from a connected Google account. It supplements the rest of this policy; nothing here overrides Sections 5 or 7.
Limited Use. Plooms' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Specifically:
- we use Google user data only to provide the user-facing features described in the table below;
- we do not transfer or sell Google user data, except as necessary to provide those features, for security purposes, or to comply with applicable law;
- we do not use Google user data for advertising;
- we do not use Google user data, or anything derived from it, to develop, improve, or train any AI or machine-learning model, whether generalized or personalized. Plooms does not train or fine-tune models at all; and
- we do not transfer Google user data to any AI provider that uses it to train models. Our AI provider, DeepInfra, receives only the text needed to produce the result you asked for, does not store it after the request, and does not use it for training.
The use of raw or derived user data received from Google Workspace APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Humans do not read your Google data. No Spej employee accesses Google user data except with your explicit permission (for example, if you ask for support on a specific problem), where required for a documented security investigation, or where required by law.
What we request, and why. Connecting Google is optional and per-user. You choose which mailbox labels, Drive folders, and transcripts to include, and you can change or remove that selection at any time.
| Google scope | What it lets Plooms do | Where the data is stored | How long |
|---|---|---|---|
openid, email, profile | Confirm which Google account you are connecting, and check it matches your Plooms account | Account record only (your email address) | While connected |
gmail.send | Send an email from your account when you ask Plooms to, in a chat or from an agent. Plooms shows you the recipients, subject, and text first, and sends only after you confirm — unless you have set that agent to run fully on its own | Plooms keeps no copy of the sent email (it is in your Gmail Sent folder). The message you confirmed stays in that chat or in that agent's run history, like any other reply, and the AI requests that wrote it are recorded in Plooms' internal operational traces | The sent email: not retained. The chat or agent run: until you delete it. Operational traces: up to 90 days, even after you delete it |
calendar.events | See your events when you ask about your schedule or one of your events in a chat, and create, update, or delete an event when you ask | Not stored: your events are read from Google when you ask, and Plooms keeps no copy. What the assistant writes about them is saved in that chat (and in what Plooms remembers from your chats), like any other reply; the later AI requests that include that reply (your next messages in the chat, and remembering it) are also recorded in Plooms' internal operational traces | Your events: not retained. The chat: until you delete it. Operational traces: up to 90 days, even after you delete the chat |
meetings.space.readonly | Requested only if you tick "Include Meet transcripts" when connecting. Bring your Google Meet transcripts into your knowledge base, once you choose to include them | Your workspace database and knowledge graph | Until you delete it |
gmail.readonly | Bring the content of the mail labels you select into your knowledge base, so answers can cite it. A conversation is read in full when any of its messages carries a label you selected; attachments are not downloaded | Your workspace database (text + search index) and knowledge graph | Until you delete it |
drive.readonly | Bring the content of the Drive folders you select into your knowledge base, so answers can cite it | Your workspace database, your workspace file storage, and knowledge graph | Until you delete it |
We request gmail.readonly and drive.readonly — rather than a narrower scope — because Plooms ingests the content of the labels and folders you select as a background sync, on your behalf and without you picking each file individually. Google's narrower alternatives do not support that: drive.file covers only files chosen one at a time in a Google file picker, and gmail.metadata returns headers without the message content that answers are grounded in. We do not request any broader scope, and Plooms never asks for permission to modify or delete your mail or your files. Google describes drive.readonly as access to all your Drive files; Plooms reads the content only of files in the folders you select. To notice files added to or changed in those folders, it reads Drive's list of recent changes — file names, types, and folder locations, not their content — and ignores everything outside your selection.
What we access, and what we derive from it. Plooms accesses only the Google data listed in the table above. From it, Plooms creates derived data that stays in your own workspace and serves only you: extracted text, a search index, entries in your knowledge graph, and the answers and documents you ask for. We do not create aggregated or anonymized datasets from Google user data, and we do not use Google user data — raw, derived, aggregated, or anonymized — for analytics, benchmarking, research, advertising, or any purpose other than providing the features you use. The only aggregate figures we keep are usage counts that contain no Google content, such as how much AI processing your account used, for metering and billing.
Who receives it. We share Google user data only with:
- Microsoft Azure, which hosts the environment where your workspace stores and processes it;
- DeepInfra, our AI provider, which receives the passages needed to answer your question, create what you asked for, or build your search index, only for the length of that request (see Limited Use above);
- people and services you direct it to — for example, the recipients of an email you ask Plooms to send, a colleague you share an item with, a Slack channel where you ask @Plooms a question, or our web search provider when you turn on web search for a chat (the search query only); and
- authorities, where the law requires it, as described in Section 4.
We do not sell Google user data, and we do not share it with advertisers, data brokers, or any other third party. Our other service providers — Stripe, Resend, Sentry, and Cloudflare — receive no Google user data.
How we protect it.
- In transit: encrypted with TLS 1.2 or higher — between you and Plooms, and between Plooms and Google or DeepInfra.
- At rest: your workspace's databases and files sit on encrypted Azure disks. Your Google access and refresh tokens are additionally sealed with a key unique to your deployment, held in a separate key vault and never in the database.
- Isolation: each customer runs in its own environment, and inside it your Google data is visible only to you unless you choose to share something.
- Access control: every account requires two-factor authentication, and no Spej employee reads Google user data except as described above.
- Monitoring: firewalls and automated threat detection protect every environment.
How long we keep it. Google content you bring in stays in your workspace until you delete it, disconnect Google and choose to delete it, or delete your account. Answers that quote it are saved in the chat where you asked, until you delete that chat. Records of AI requests (operational traces), which can include the passages sent to the AI, stay inside your workspace's environment and are deleted automatically after 90 days.
Deleting it. You can disconnect Google at any time, from Connectors in the product. Disconnecting revokes Plooms' access token at Google. You are then asked, separately, whether to delete everything already brought in; choosing to delete removes the extracted text, the search index entries, any stored file copies, and the knowledge-graph entries derived from them. You can also delete individual items at any time, delete a personal account from Profile → Delete account, or email [email protected] to request deletion of your account and all associated data.
11. Changes to this policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email or by prominent notice in the Services and update the "Last updated" date. Your continued use of the Services after the effective date constitutes acceptance of the updated policy.
12. Contact us
Spej Corp 320 West Ohio Street, Suite 3W, Chicago, IL 60654 Email: [email protected]