Privacy Policy

Skedo Technologies Incorporated dba Mulstra (“Mulstra”, “we”) provides a workspace platform for running business operations — records, workflows, dashboards, and communications. This policy covers mulstra.com, workspaces hosted at *.mulstra.app, and the Mulstra application.

Questions, requests, or complaints: privacy@mulstra.com.

This distinction matters for everything below. When you use Mulstra we are a controller of your account data (your email, name, billing, how you use the product). For the records you put into your workspace — your contacts, leads, deals, files — we are a processor. That data is yours. We act on your instructions, we don't mine it, and we hand it back or delete it when you ask.

• Account — email address, display name, optional avatar URL, and a hashed password (bcrypt; we never store the password itself).
• Workspace content — the objects, records, files, documents, and workflows you create. Whatever you choose to put in.
• Integration credentials — API keys and OAuth tokens for services you connect. Encrypted at rest with AES-256-GCM under a key held outside the database.
• Operational logs — workflow runs, email delivery events, API requests, and audit entries, used to make the product work and to debug it.
• Enquiries — if you request a demo we collect the work email you submit and may enrich it from public and third-party business sources.

We do not run advertising trackers, we do not sell personal data, and we do not use behavioural profiling.

Connecting Google is optional. There are two separate connections: a Google Calendar, per person, used only for bookings; and Google Analytics and Search Console, per workspace, used only to show your site's traffic and search numbers. If you connect a Google Calendar:

• Scopes requested: calendar.freebusy and calendar.events.owned. The second covers only calendars you own, not calendars others share with you. No others: we don't request Gmail, Drive, or Contacts.
• What we read: when you are busy or free. When a booking is rescheduled, we also read the start and end times of events on your primary calendar, and whether you declined them, so the booking being moved isn't counted against you. We do not request or store the titles, descriptions, locations, or attendees of your events.
• What we write: when someone books time with you, we add that meeting to your primary calendar, with the guest's name and email and, if the booking type uses Google Meet, a Meet link. When the guest reschedules or cancels, we move or delete that same event. We don't change or delete any other event.
• Why: so a booking page offers only times you can make, work goes to people who are actually available, and booked meetings land on your calendar.
• What we store: a Google refresh token, encrypted at rest; a flag recording that your calendar is connected; and, for each booking, the ID and Meet link of the event we created. Busy/free times are read when they're needed and are not stored.

Limited Use. Mulstra's 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 do not transfer Google user data to third parties except as necessary to provide or improve this feature, to comply with applicable law, or as part of a merger or acquisition; we do not use it for advertising; we do not allow humans to read it except with your explicit consent, to resolve a specific support issue you have raised, for security purposes, or where required by law; and we do not use it to develop, improve, or train generalised AI or machine-learning models.

Revoking access. Remove Mulstra at any time at myaccount.google.com/permissions. From then on Mulstra can't read or write your calendar: your availability shows as unknown and new bookings aren't added to it. Nothing else in your workspace changes. To have the stored token deleted as well, email privacy@mulstra.com.

A workspace owner or admin can connect a Google account so the workspace can show how its sites are doing. This is read-only. If you connect one:

• Scopes requested: analytics.readonly and webmasters.readonly, plus openid and email so we can show which Google account is connected. We cannot change anything in your Analytics or Search Console accounts, and we don't request Gmail, Drive, Ads or Contacts.
• What we read: the list of Analytics properties and Search Console sites your account can see, so you can choose which ones to connect; then, for the ones you choose, daily totals: visitors, sessions, page views, conversions, traffic sources, top pages and countries from Analytics, and top search queries, pages, clicks, impressions and positions from Search Console. We do not read individual visitors.
• Why: so these numbers appear in your workspace dashboards and reports beside the rest of your business data.
• What we store: a Google refresh token, encrypted at rest; the email of the connected account and which permissions you granted; and the daily totals above, in your workspace.

The Limited Use commitments above apply to this data too. To disconnect, use Disconnect on the integration, which deletes the token we hold, and remove Mulstra at myaccount.google.com/permissions. Daily totals already synced stay in your workspace until you delete them.

Some features send workspace content to a large language model to generate text, build schema, or answer questions. This happens only when you invoke such a feature. We use providers under agreements that prohibit training on our customers' data, and we do not use your workspace content or your Google data to train models— ours or anyone else's.

These sub-processors are part of running Mulstra itself:

• Vercel — application hosting and edge delivery
• Supabase — the primary Postgres database
• Resend — transactional email
• Anthropic — the model behind AI features
• Google reCAPTCHA — abuse prevention on public forms

Separately, you may connect optional integrations — Slack, Stripe, SendGrid, Apollo, a CalDAV server, your own database, and others. Those are your choices and your agreements with those providers; we pass data to them only as your configuration directs. You can disconnect any of them at any time.

Workspace content is kept while your workspace is active. Delete a record and it is soft-deleted first so it can be recovered from mistakes, then removed. Close your account and we delete your workspace content within 30 days, except where we must keep something to meet a legal or accounting obligation. Operational logs are kept for a limited period for security and debugging. Encrypted integration credentials are deleted as soon as you disconnect the integration.

Want everything gone sooner, or want an export first? Email privacy@mulstra.com and we'll do it.

Depending on where you live, you may have the right to access, correct, export, or delete your personal data, to object to or restrict processing, and to complain to a data protection authority. Exercise any of these by emailing privacy@mulstra.com. We'll respond within 30 days. We won't charge you or treat you differently for asking.

If your personal data sits inside someone else's Mulstra workspace — because they are our customer and you are their contact — direct your request to them; we'll assist them in fulfilling it.

Data is encrypted in transit (TLS) and at rest. Integration credentials get an additional layer of application-level AES-256-GCM encryption. Access to production systems is limited to people who need it. No system is perfectly secure, and we don't claim otherwise — but if a breach affects your data we will tell you promptly and tell you what we know.

Our infrastructure providers operate globally, so your data may be processed outside your country, including in the United States. Where required, transfers rely on appropriate safeguards such as the EU Standard Contractual Clauses.

Mulstra is a business tool and is not directed at anyone under 16. We don't knowingly collect their data; if we learn we have, we delete it.

We'll update this page when our practices change and move the “last updated” date. If a change materially reduces your rights, we'll tell account holders by email before it takes effect.