Privacy Policy
Effective: September 26, 2026 · Last updated: October 23, 2026
1. Who we are
Senemora LLC ("Senemora", "we", "us") is an Oregon limited liability company (registry number 263049190). We design and run operations software for businesses: a hosted workspace with an AI assistant, and the consulting, setup and support around it. Our mailing address is 5441 S Macadam Ave #6681, Portland, OR 97239, USA. For anything in this policy, write to privacy@senemora.com.
2. What this policy covers
This policy covers personal information we handle through our website (www.senemora.com), through the Senemora service (the workspaces we host, their AI assistant, and the pages they publish to share, book, quote or collect information), and through our dealings with customers. It does not cover other companies' websites or services, even when our service connects to them.
3. Our two roles
Customer data. A business that subscribes to Senemora (a "customer") decides what goes into its workspace and why: its files, records, messages, and the information its own clients enter on its pages. We handle that data only to provide the service, on the customer's instructions and under our agreement with them. For that data we are the customer's service provider (a "processor" or, under Japan's Act on the Protection of Personal Information, an entrusted party), and the customer is responsible for it. If you are one of a customer's clients, or appear in a customer's records, please contact that business first. We will help them answer you.
Our own data. For everything else (website visits, sign-in, account and billing details, support, security, and how the service is used), Senemora decides how the information is used and is responsible for it. Most of this policy is about that information.
4. Information we collect
Information you give us. Your name, email address, business name and message when you email us. For customers and their team members: name, email address, role in the workspace, language preference and notification settings. For billing: the billing contact, the plan chosen, invoices and payment records. When a customer pays by card, Stripe collects the card details on its own page, and we never see or store them. We keep only Stripe's references to the customer, subscription and payment. When a member sends feedback from the workspace: their name, email address and words, the part of the workspace they were in, recent errors, and any screenshots they choose to attach.
Workspace content. Whatever a customer and its members put in a workspace or have it handle: files, records, notes, recordings, conversations with the AI assistant, and email and text messages sent or received through the workspace or accounts the customer connects. It also includes information that visitors enter on a customer's published pages, such as a booking, a form or a signed quote. This is customer data (section 3). The service is not designed for payment card numbers, government identification numbers, health records or other sensitive categories unless we have agreed to it in writing with the customer.
Information collected automatically.
- Sign-in. Signing in sets one cookie that keeps you signed in. It ends after 30 days without use, and after 400 days at most. A short-lived cookie is also used while you sign in with Google or Microsoft, or connect a Gmail or Outlook account. Both are strictly necessary. We use no advertising or tracking cookies, and our website sets no cookies at all.
- Stored in your browser. The workspace keeps preferences and drafts in your browser's own storage, such as open threads, your chosen voice and where to return after signing in. On a customer's published pages, your browser keeps the link's access code for the visit, and keeps a drawn signature only if you ask it to remember it. None of this is used to track you.
- Server logs. Our servers record the IP address, time, requested address and response of each request, and the browser's own description of itself, to operate and secure the service.
- Product analytics. When someone uses the service, we record events such as "a module was opened", "a tool was used" or "a page was completed", with the workspace's name, the type of module and counts. The person is identified only by a one-way pseudonym derived from their email address. We never send the content, people's names, email addresses or file names. Visitors to published pages are never identified. In the workspace, your browser does not contact our analytics provider; our servers do.
- Website analytics. On www.senemora.com, your browser loads PostHog's script, which records the pages you view, when you leave, and whether you click one of our email links. PostHog receives your IP address and browser details, as any website does. Nothing is stored in your browser, so a reload counts as a new visit, and a browser that sends Do Not Track is not measured.
- Bot protection on published pages. Where it is turned on, a customer's published pages load Google reCAPTCHA. Google receives your IP address, browser and device details and how you use the page, and may use its own cookies. When you send something, such as a form, a booking or an acceptance, Google gives us a score of how likely it is that a person sent it, and we refuse the submission if the score is too low. We send Google only the token the page received, never what you entered. Google handles this information under its own Privacy Policy and Terms of Service, and says it uses it to provide and improve reCAPTCHA and for general security purposes, not for personalized advertising.
- Error reports. When something breaks, on our servers or in your browser, we send a technical report of the error, with names, email addresses and file paths removed. Reports from your browser pass through our servers first.
- Usage and diagnostics. We meter AI, search and messaging usage for each customer to charge it in Mora Points and apply limits. For AI, we receive from the workspace, and from OpenRouter, which model answered, how many tokens each request used and what it cost, never what the request contained. While a workspace's owner has turned on sharing with our support, we also receive diagnostic records of the AI assistant's work: timings, counts, outcomes, the models and modes used, and shortened inputs to the tools it used, which may include fragments of workspace content. These records do not include your messages to the assistant or its replies.
- Push notifications. If you turn on notifications, your browser gives us an address at its maker's push service (Google, Mozilla, Apple or Microsoft). Each notification we send there is encrypted, so the push service sees only that one was delivered.
Information from others. If you sign in with Google, Google tells us your verified email address and nothing else. If you sign in with Microsoft, Microsoft also sends basic profile details, such as your name, and we keep only your email address. When a member uses the Gmail add-on, Gmail gives us what section 7 describes. When a customer connects another account (such as Gmail, Outlook, an email or text-message sender, or Stripe or Square), that service sends us the data the connection is for, as workspace content. Stripe tells us when a payment to us succeeds or a subscription changes. If a business joins with a customer's referral code, we record which customer referred it. To find and contact possible customers, we may note business contact details that people publish themselves, such as on a company website.
5. How we use information
We use personal information to:
- provide, operate and maintain the service, including signing people in and delivering the messages a workspace sends;
- send service messages, such as sign-in links, alerts a member has asked for, and notices about the service or an account;
- meter usage, apply plan limits, invoice and collect payment, and credit referral rewards;
- answer questions and provide the setup and support a customer asks for;
- find and contact businesses that may want our service;
- keep the service and its users secure, and investigate and fix problems;
- understand how our website and service are used, in pseudonymous or aggregated form, so we can improve them; and
- comply with law and enforce our agreements.
We do not sell personal information. We do not share it for cross-context behavioral advertising, and we do not show advertising. We do not use workspace content to train AI models. People at Senemora look at workspace content only when a customer asks us to, when it is necessary to maintain or secure the service, or when the law requires it. Only authorized people bound by confidentiality do so. When a customer asks us to set up or work in its workspace, we may do that work with an AI tool, such as Anthropic's Claude, under terms that forbid the provider from training on it.
6. The AI assistant
To answer a request, the assistant sends the relevant workspace content to an AI model, including pictures of receipts, bills or contracts it is asked to read. When a cloud voice reads text aloud, that text goes the same way, and so does the audio of a recording the workspace transcribes. Each workspace sends these requests to OpenRouter itself. Our central service, which keeps track of what each customer's AI use costs, never receives what a request contains. We choose which models answer, which can differ from one mode of the assistant to another, and may switch to another allowed model when one is unavailable.
Zero data retention, on by default. Unless a customer chooses otherwise, its workspace requires zero data retention: OpenRouter passes its requests only to providers that neither store the content nor use it to train models. Today these are Microsoft Azure, running OpenAI's and Microsoft's models, and Google Cloud, running Google's Gemini models. By default, requests also go through OpenRouter's United States service, which handles them in the United States and passes them only to providers there. OpenRouter itself enforces these requirements, and the models we allow, on the access keys we issue for each workspace.
If a customer turns it off. A customer's owner may turn zero data retention off, for example to use cheaper or more models. OpenRouter may then send the workspace's requests to any provider of the models we allow, and that provider may keep the content for a time under its own terms, for example to monitor abuse. A customer may also allow its requests to be handled outside the United States. Either way, every request still requires that no provider use its content to train models.
The customer's own AI. A customer may instead connect its own AI account, or connect an AI tool such as Claude or Codex to its workspace with an access key. In that case the customer's agreement with that provider governs what the provider does with the content.
The web. When the assistant searches the web, the search terms pass through our central service to Brave Search, unless the customer uses a search service of its own. To read a web page, the workspace or our central service fetches it directly, and a page that cannot be read that way is read through Jina AI. Search terms and page addresses can reflect what a member asked about.
Quick decisions. The service also asks a separate AI model, TypeSafe AI's Jev, for quick decisions. While a member types a message to the assistant, Jev reads the words before they are sent, with the last few messages of the thread, to suggest a mode. For each message, it judges which parts of the workspace the request is about and which tools it needs. It also judges whether an automation should run, what kind of email arrived and what it concerns, whether a form submission is spam, which category a receipt belongs to, how pressing an alert is, and which record a new email, card or calendar event belongs to. Each request sends only what that decision needs, such as the words being typed, an email's sender, subject and text, a form's answers or an alert's title, with the names of the records it might belong to. Each workspace sends these requests to OpenRouter itself under the same zero data retention setting, with a separate access key that can reach only that model, and our central service never receives their content. TypeSafe AI is based in the United States but offers no United States-only service, so these requests may be handled in other countries. They are made only when a workspace uses our AI service, never when a customer connects its own AI account.
7. Gmail and other Google user data
The Gmail add-on. A member can install Senemora's add-on in Gmail and connect it to their workspace under Settings > Account > Gmail, by signing in with Google. Connecting records in the workspace which Google account the member linked and its email address. Our central service records only Google's identifier for that account and which workspaces it is linked to.
What it reads, and when. When the member opens an email in Gmail, Google sends our central service that email's Gmail identifier, the member's Google account identifier and email address, and their language, so the add-on can show where the email may be filed. It does not send the email itself. The add-on reads an email's content only when the member selects Analyze email on it. Their workspace then reads that one email (its sender, recipients, subject, text and attachments) with access that Gmail grants for that one request. The add-on never reads any other email, never reads in the background, and keeps no access to the member's Gmail afterwards.
What it does with it. The email is filed in the Mailbox the member chose and kept there as workspace content (section 3). Members whose roles reach that Mailbox can see it, and the Mailbox's own rules work on it as on any email it receives. This can include sending it to AI providers, as section 6 describes, to sort it, suggest what it belongs to, run the workspace's automations and, if the member selects Write reply, write a reply. When the member selects Open in Gmail, the add-on creates a draft of that reply in the email's conversation in their Gmail, with the Mailbox's address in Bcc, so the workspace records the reply when they send it. The add-on does not send, change, label or delete anything in Gmail. Our central service keeps Gmail's identifier for each email filed through the add-on for 180 days, so it can show where the email was filed, and never its content.
Disconnecting. Selecting Disconnect Gmail under Settings > Account removes the link in the workspace and at our central service, together with our central service's record of what was filed through it. Emails already filed stay in the workspace as its content until they are deleted there. You can also remove the add-on in Gmail, or remove its access at https://myaccount.google.com/permissions.
Other Google data. Signing in with Google gives us only your verified email address (section 4). When a member connects Gmail for sending, the workspace can send the emails the member sends from it as them, and cannot read their mail.
Limited Use. Senemora's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features described here, which the member sees and uses. We do not sell it, use it for advertising, or use it to train generalized AI or machine-learning models, and the AI providers that process it may not use it to train models either. People at Senemora read it only with the member's agreement for specific emails, when necessary for security, such as investigating abuse, or to comply with the law. Otherwise we use it for our internal operations only in aggregated and anonymized form.
8. Who we share information with
We share personal information only as this section describes:
- Service providers that run parts of the service for us, under contracts that limit them to that work (table below).
- Google, for bot protection. Google reCAPTCHA (section 4) receives information directly from a visitor's browser and handles it as a separate business under its own terms, not only on our instructions.
- Stripe, for payments to us. Stripe processes card payments for our plans and Mora Points. It receives the business's name and our reference for its account from us, and the card and contact details entered on Stripe's own payment page. Stripe also handles this information under its own Privacy Policy, for example to prevent fraud.
- Within a workspace. Members see workspace content according to the roles the customer sets. Visitors see what a customer publishes on its pages.
- Between a referrer and the business it referred. If a business joined with another customer's referral code, that customer sees the business's name, when the referral started and ends, and the Mora Points the business's payments earned it.
- At a customer's direction. Connected services receive what the customer sends them, such as an email through its mailbox, a payment request through its Stripe or Square account, or whatever an AI tool connected with the workspace's access key reads.
- Contractors who help us deliver a customer's project, only with that customer's approval and under written confidentiality.
- For legal reasons. To comply with law or valid legal process, or to protect the rights, safety or property of people or of Senemora. We tell the affected customer first where the law allows.
- In a business transfer. If Senemora is merged or sold, this policy continues to apply to the information transferred.
| Provider | Purpose | Location |
|---|---|---|
| Amazon Web Services | Hosting, storage and backups | United States (Oregon) |
| Amazon Web Services | Website delivery | United States (Virginia), delivered from locations worldwide |
| OpenRouter | Passing AI requests to the providers below | United States; other countries for quick decisions, or where a customer allows it |
| Microsoft Azure (OpenAI and Microsoft models) | AI assistant, reading aloud and transcription | United States, unless a customer allows otherwise |
| Google Cloud (Gemini models) | AI assistant and reading aloud | United States, unless a customer allows otherwise |
| TypeSafe AI (Jev model) | Quick AI decisions: suggesting, sorting, screening and routing | United States; requests may be handled elsewhere |
| Other AI providers on OpenRouter | AI requests, only when a customer turns off zero data retention (section 6) | Varies by provider |
| Sign-in with Google, Gmail when a member connects it or uses the Gmail add-on, push notifications | United States | |
| Microsoft | Sign-in with Microsoft, Outlook when a customer connects it, push notifications | United States |
| Mozilla, Apple | Push notifications | United States |
| Stripe | Card payments to us | United States |
| Resend | Sending and receiving email | United States |
| Twilio | Sending text messages | United States |
| Brave Search | Web search for the assistant | United States |
| Jina AI (part of Elastic) | Reading web pages for the assistant | Germany; its servers may be elsewhere |
| Hugging Face | Voices for reading aloud, which a member's browser downloads | United States |
| Anthropic | AI tool for the setup and support a customer asks for | United States |
| PostHog | Product and website analytics | United States |
| Sentry | Error reports | United States |
When a customer connects its own Stripe, Square or similar account to take payments from its own clients, that service is not our provider. The customer uses it under its own agreement.
9. International transfers and Japan
We store data in the United States (AWS, Oregon), and the providers in section 8 are in the United States, except Jina AI, which is based in Germany, an EU country that Japan's Personal Information Protection Commission recognizes as having an equivalent system. Two kinds of AI request may be handled in other countries: quick decisions (section 6), and requests from a workspace whose customer has allowed handling outside the United States. OpenRouter chooses the place for each such request, so we cannot say in advance which country it will be. If you are in Japan, your personal information is transferred to and handled in the United States. The United States has no comprehensive federal privacy law equivalent to Japan's Act on the Protection of Personal Information (APPI). Protection comes from sector-specific federal laws, state laws such as the Oregon Consumer Privacy Act and the California Consumer Privacy Act, and the Federal Trade Commission's enforcement against unfair or deceptive practices. The Personal Information Protection Commission publishes information on foreign privacy systems at https://www.ppc.go.jp/. We transfer personal information to providers in foreign countries either with your consent or where the provider has a system that meets APPI standards, through a contract requiring equivalent protection. We check each provider's handling from time to time, and you may ask us for details.
Security measures (APPI). Organizational: one person is responsible for personal information, and access is granted per person and revoked when no longer needed. Personnel: everyone with access is bound by confidentiality and follows written procedures. Physical: servers are in AWS data centers, and work devices are protected and kept up to date. Technical: see section 11. Knowledge of the foreign environment: we handle data in the United States after reviewing its privacy system, described above.
10. How long we keep information
- Workspace content: while the customer's service is active. When it ends, we offer the customer an export, then delete the workspace within 30 days. Backups containing it expire within a further 30 days. A workspace's change history is part of the workspace and is kept for as long as the workspace is.
- Account and contact details: while the account is active, then as for workspace content. The addresses our sign-in emails went to, which decide who may receive alerts, are kept while the customer's account is.
- Invoices, payment records and Mora Points records: as long as tax and accounting law requires, generally seven years. This includes Stripe's references and referral rewards.
- Diagnostic records: up to 90 days. Usage records are kept like invoices, because billing depends on them.
- Received email: our central service keeps an index of the emails it received for a workspace, without their content, for 30 days. Resend keeps the emails it receives under its own retention rules.
- Feedback: up to 1 year.
- Gmail add-on: the link to a Google account until the member disconnects it. Gmail identifiers of filed emails, at our central service, for 180 days. A filed email is workspace content.
- Server logs: up to 90 days.
- Product analytics: up to 1 year.
- Error reports: up to 90 days.
- Bot-protection scores: not kept. Each is used once, to accept or refuse a submission.
- Emails with us: as long as needed for the relationship they concern.
We keep information longer only when the law requires it or to resolve a dispute, and then only the information and period required.
11. Security
Each customer's workspace runs in its own containers, with its own data directory and network, on servers it may share with other workspaces. Connections are encrypted in transit, and disks and backups are encrypted at rest. Credentials that customers store with us are encrypted separately, and nothing in the service can read them back out. When a member connects Gmail or Outlook, our central service passes the account's tokens to the workspace without keeping them. Access keys are stored only in a form that cannot be turned back into the key. Changes to workspace data are recorded in a history showing who or what made them. Our own access is limited to named people and protected with multi-factor authentication. No system is perfectly secure. If a breach affects your personal information, we will notify the affected customers, and you where the law requires, without undue delay.
12. Your rights and choices
Depending on where you live, you may have the right to know what personal information we hold about you and ask for a copy, to correct it, to delete it, to receive it in a portable form, to ask us to stop using or sharing it, and to see the third parties we have provided it to. People in Japan may request disclosure, correction, addition or deletion, suspension of use or of provision to third parties, and disclosure of records of provision to third parties under the APPI. Residents of Oregon, California and other U.S. states with privacy laws have the rights those laws give. We do not sell personal information or use it for targeted advertising, so there is nothing to opt out of. We still treat a Global Privacy Control signal as an opt-out request. We will not treat you differently for using any of these rights.
How to make a request. Email privacy@senemora.com, in English or Japanese. We will confirm your identity, usually by replying to the email address we hold for you, and answer within 45 days (sooner where the law requires). An authorized agent may act for you with proof of your authorization. There is no fee unless a request is clearly unfounded or excessive. If we decline, we will explain why. In the United States you may appeal by replying to our decision with "appeal" in the subject, and we will respond within 60 days. If your request concerns customer data (section 3), we will pass it to the customer and help them answer it. Members can also change their name, language and notification settings in the workspace themselves.
Other choices. You can turn off push notifications in your browser or device settings, and ask us to stop any email that is not needed to run your account. Your browser downloads a voice only when you choose it. You can disconnect the Gmail add-on at any time (section 7). A workspace's owner decides whether diagnostic records are shared with our support and whether zero data retention stays on. If your browser blocks Google reCAPTCHA, a page that uses it can still be read but cannot accept what you send; contact the business that published it another way.
13. Children
The service is for businesses and is not directed to children under 16. We do not knowingly collect their personal information. If you believe we have, contact us and we will delete it.
14. Changes to this policy
We will post any change here and update the date at the top. If a change materially affects how we handle personal information, we will tell customers by email or in the service before it takes effect.
15. Contact
Senemora LLC · Attn: Privacy · 5441 S Macadam Ave #6681, Portland, OR 97239, USA · privacy@senemora.com. We accept questions and complaints in English and Japanese, and give the name of our representative on request. If the English and Japanese versions of this policy differ, the English version controls, to the extent the law allows.