Privacy Policy

Last updated: June 13, 2026

This is how Roman Roads ("Roman Roads," "we," "us," or "our") handles your information when you use SkillBridge, our scheduling and team-coordination app (the "Service"). We've written it in plain language on purpose — your data is your business, and you shouldn't need a lawyer to understand what we do with it. This policy covers the SkillBridge app and the part where you can connect a calendar to keep your availability accurate.

1. Who this is for

This policy is for the people who actually use SkillBridge — the operators who run a business and the team members ("workers") they coordinate. If you're just shopping on the Roman Roads online store, that's a different thing, and the separate store Privacy Policy covers it.

2. What we collect

• Account information — your name, email, and the organization you're part of, so we can set up and run your account.
• Availability and scheduling data — the working hours, locations, and booking details you put into the Service.
• Google account data — only if you choose to connect a Google Calendar. We get into exactly what that means in Section 3.
• Technical data — the standard log and device information we need to keep the Service running, secure, and working the way it should.

3. Google Calendar data and Google API Services

Connecting a Google Calendar is completely optional. There are two separate ways it can connect, each authorized on its own, and we only ask for the access each one genuinely needs:

• Availability calendar (team members) — a worker can connect their own Google Calendar so the Service can read their busy times and keep availability accurate, which is what stops the double-bookings. This connection is read-only.
• Meeting-host calendar (organizations) — an organization admin can connect a single organization calendar (think of a shared "bookings" account) that the Service uses to create the calendar events and video-meeting links for sessions booked through SkillBridge. This one needs write access, and we only use it to create and manage those booking events.

3.1 The scopes we ask for, and why

• .../auth/calendar.readonly and .../auth/calendar.events.readonly — for an availability-calendar connection, so we can read the events on the calendars you pick and work out when you're busy.
• .../auth/calendar.events — for a meeting-host connection only, so we can create and manage the calendar events and video-meeting links for sessions booked through SkillBridge on the connected organization calendar. We don't use this access to read or touch unrelated events.
• .../auth/userinfo.email and openid — so we know which Google account you connected and can show it back to you.

3.2 What we actually store

We keep as little as possible. From an availability calendar we store only the start and end times of when you're busy. We do not store event titles, descriptions, attendees, locations, video links, attachments, or any other event content. For a meeting-host connection we store only the identifiers of the booking events SkillBridge itself created, so we can update or cancel them later — we don't read or store unrelated events from that calendar.

3.3 What we do with it

Busy times from an availability calendar are used for exactly one thing: working out your availability inside SkillBridge, so you don't get booked over something you're already committed to. Write access to a meeting-host calendar is used for exactly one thing too: creating, updating, and canceling the calendar events and video-meeting links for sessions booked through SkillBridge. We do not use Google data for advertising, and we do not use it to build profiles for anything unrelated to scheduling.

3.4 How we protect it

OAuth credentials are encrypted at rest. Calendar data travels over encrypted connections (HTTPS), and access stays limited to running the Service.

3.5 Who we share it with

Nobody. We do not sell, rent, or hand Google user data to third parties, and we don't share it for advertising. Google data is only ever used to power the scheduling features you see in SkillBridge.

3.6 Keeping it and deleting it

You can disconnect a Google account any time from inside SkillBridge. The moment you do, we stop syncing, remove the stored busy times for that account, and deactivate the stored credentials. You can also revoke SkillBridge's access straight from your Google Account at myaccount.google.com/permissions.

3.7 Limited Use disclosure

SkillBridge'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.

4. How we use information generally

Beyond the Google specifics above, we use the information we collect to run, maintain, secure, and improve the Service, to verify it's really you, to talk with you about the Service, and to meet our legal obligations.

5. How long we keep it

We hold onto account and scheduling data for as long as your account is active, or as long as we need it to provide the Service. Busy times pulled from Google stick around only while that calendar connection is active, and they're removed the moment you disconnect.

6. Your choices and rights

You can look at or update your account information, disconnect any connected calendar, or ask us to delete your account — just reach out at the address below. Depending on where you live, you may have extra rights under the privacy laws that apply to you, and we'll honor them.

7. Children

SkillBridge isn't built for or aimed at children under 13, and we don't knowingly collect personal information from them.

8. Changes to this policy

We may update this policy now and then. When we change something that matters, we'll update the "Last updated" date above and, where it makes sense, let you know inside the app.

9. Get in touch

If anything here raises a question — about this policy or how we handle your data — we'd genuinely like to hear it. Email us at nick.stacy@romanroads.com.