Privacy Policy

Effective: November 1, 2026 · Version: 1.1

1. Who is responsible for your information

Signet is operated by Pulse Pedagogies, LLC (“Pulse Pedagogies”, “we”) and licensed to the institution that runs it — your employer or the organization that gave you access (the “Institution”).

The Institution decides what is collected and why; we process it on the Institution’s behalf. Requests to access, correct, or delete your information should go to the Institution first. Where we receive such a request directly, we will refer it to the Institution rather than act on it unilaterally.

2. Information we collect

Information you provide

• Identity: your name and work email address, received from your institutional Google account when you sign in or register.
• Professional context: the role and work site you select when registering for a session, and any job title recorded by an administrator.
• Registration details: which sessions you requested, the confirmations you ticked, and whether you later released your place.

Information generated by your use

• Attendance: whether you attended, how the attendance was captured, and the payable hours calculated from it.
• Credentials: badges issued to you, including a signed record naming you as the holder, and any subsequent revocation.
• Evidence: for self-paced offerings, work you submit for review.
• Session recordings: some sessions are recorded. A recording follows the presenter, the shared screen and whoever is speaking, so it captures your image and voice if you choose to speak; an attendee who does not speak is not in the recording. Sessions that will be recorded say so on the registration form, and you are asked to confirm you understand before you can request a place. A recording may be kept for colleagues who could not attend, may be posted publicly on a channel the Institution owns, such as its website or video channel, where anyone can watch it, or may not be published at all — that decision is made by the Institution afterwards and is not settled in advance. Recordings are made and stored in Google Meet under the Institution’s Workspace, not in Signet; where a finished recording exists, Signet may hold a link to it, visible only to administrators. Signet requires your confirmation before it will accept your request, but does not keep a record of the confirmation itself.

Information collected automatically

• An essential session cookie — see Section 5.
• Hosting logs. Our hosting provider records ordinary web-server information — request paths, timing, response codes, and the network address the request arrived from — and retains it only briefly. We do not store network addresses in the database or use them to build a profile.
• Application logs. When a registration completes we log the session, the outcome, how long it took, and whether the acknowledgement email sent. That line contains no name or email address.
  However, certain error paths do write an email address to the log — for example when a message fails to send, or when two simultaneous submissions collide — so the failure can be traced to the person it affected. These logs are short-lived, are visible only to the operator, and are not used for any purpose other than diagnosing the failure.

What we do not collect

• No student records of any kind. Signet is a staff system and is not designed to hold information about students or minors.
• No passwords. Sign-in is handled entirely by your institutional Google account; we never receive, store, or verify a password.
• No payment or financial information.
• No advertising or marketing trackers, and no analytics inside the Service — no page-view tracking on any signed-in page or on any organization’s site, no behavioural profiling, and no third-party advertising code. One Google-hosted script is loaded to operate the sign-in button, and our public product page counts visits with a cookieless tool; both are described in Section 5.
• No sale of personal information. We do not sell or rent it, and we do not use it to train machine learning models. The one optional AI feature and its limits are described in Section 7.

3. How we use information

• To register you for professional learning and to let an administrator approve, waitlist, or decline that request.
• To send you transactional messages about sessions you registered for — acknowledgements, confirmations, changes, and credential notices.
• To place a calendar invitation for a session on your calendar, and to remove it if you release your place.
• To record attendance and produce the attendance and payable-hours record the Institution uses.
• To issue, display, and where necessary revoke digital credentials.
• To secure, operate, debug, and improve the Service.

4. Credentials are public by design

A digital credential is only useful if someone outside your institution can check it. When a credential is issued to you, it receives a public verification page reachable by anyone holding its link, showing the credential, the issuing organization, the date, and your name as its holder. The credential image itself carries the same signed information inside it.

Nothing else about you appears there — not your email address, work site, attendance record, or any other credential. Verification pages are not listed in a public directory and are not designed to be browsed, but they are not secret. If a credential is revoked, the verification page reports the revocation rather than disappearing.

5. Cookies and browser storage

In normal operation Signet sets one cookie, and only after you sign in: an encrypted session cookie named signet_session. It identifies your signed-in session, is restricted to this site, is not readable by JavaScript, and expires after eight hours. Signing out deletes it.

Signet also includes an optional concealment mode an operator can enable while an instance is being prepared. While it is enabled — it is not enabled on a normally operating instance — two additional short-lived cookies (_ok and _pg) record that a visitor has passed the holding page. They contain no identity, are not linked to any account, and are deleted when you sign out.

None of these are analytics, advertising, or cross-site tracking cookies. Because each is strictly necessary to provide a service you asked for, no consent banner is presented.

One third-party script. On pages offering Google sign-in, your browser loads Google’s Identity Services script directly from accounts.google.com. This is what renders the Google button and returns a verified identity to us. Because the request goes to Google, Google receives it and may set or read its own cookies for that domain under Google’s Privacy Policy, which we do not control. Inside the Service we load no other third-party scripts. Typefaces are served from this site rather than fetched from a font provider.

Our public product page. The page at signetsystems.net that describes Signet to prospective customers (not the Service itself, and not any organization’s site) loads Cloudflare Web Analytics to count visits. It sets no cookies and uses no browser storage, does not fingerprint your browser or follow you across sites, and reports only aggregate figures such as pages viewed, the referring site, browser type and country. It is never loaded on a signed-in page or on an organization’s own address.

6. Google Workspace integration

Signet works inside your institution’s existing Google Workspace rather than duplicating it. Signing in uses Google Identity Services: Google confirms your identity to us and we receive your name, email address, and whether the address is verified. We never see your Google password.

Separately, an administrator connects the Institution’s Google account so the Service can act on the Institution’s behalf. That connection is granted these permissions and no others:

• Send mail — to send transactional session messages. Messages are sent from the connecting administrator’s account, so they arrive from a colleague rather than a no-reply address. This permission allows sending only; it does not permit reading any mailbox.
• Manage calendar events — to mirror sessions onto the Institution’s calendar and to add or remove you as a guest when your place is confirmed or released.
• Read spreadsheets (read-only) — when an administrator points a session at the responses sheet of a Google Form used to collect reflections, to see who has submitted. Only the respondent’s email address and the submission time are read; the answers themselves are never read, stored, or shown.
• Basic profile and email — to identify the connected account.

The credential authorizing this access is stored encrypted and can be revoked by the Institution at any time from its Google account settings.

Limited use of Google data. Signet’s use and transfer to any other application of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data obtained through these permissions is used only to provide the features described above; it is not used for advertising, is not sold, is not used to train artificial intelligence or machine learning models, and is not read by any person except where the Institution asks us to for support, where needed for security, or where required by law.

7. Service providers

We keep this list short deliberately. Signet uses the following providers, each only for the stated purpose:

• Fly.io — application hosting and short-lived server logs.
• Cloudflare — DNS for our domains, and cookieless visit counting on the public product page only, as described in Section 5. It receives no records held in the Service.
• Neon — managed PostgreSQL database hosting, where records are stored encrypted at rest.
• Google LLC — identity verification, mail delivery, and calendar, as described in Section 6, within your institution’s own Workspace, plus the sign-in script described in Section 5.
• Google Gemini API — optional badge-design assistance used by administrators in the badge Studio, and by no one else. A request is sent only when an administrator types a design instruction; nothing a registrant does ever reaches it.
  Each request carries exactly two things: the seal’s current design settings (shape, colour, icon, and similar) and the plain-language instruction typed, such as “make it rounder”. No personal information of any kind is sent — no names, no email addresses, no staff records, no registration or attendance data, no credential data, and no uploaded artwork. Because no personal information reaches this service, none can be retained by it, disclosed from it, or used to train any model.

We do not sell personal information or share it with advertisers, data brokers, or analytics companies. We may disclose information where required by law, or to protect the security or rights of users and the Service.

8. Retention

Registration, attendance, and credential records are retained for as long as the Institution operates its instance, because they are the record of professional learning the Institution relies on. Retention and deletion schedules are set by the Institution under its own records policy; we delete records on the Institution’s instruction.

Server logs are short-lived and are not used to build a profile of any individual. Issued credentials are designed to remain verifiable indefinitely; revoking a credential marks it revoked rather than erasing it, so the history stays honest.

9. Security

• All traffic is encrypted in transit, and records are encrypted at rest by our database provider.
• Each institution’s records are isolated inside the database itself, enforced by the database rather than only by application code.
• Session cookies and stored third-party credentials are encrypted with authenticated encryption.
• Administrative functions require both an appropriate role and membership of the institution being administered; a revoked role takes effect immediately.
• There are no passwords to steal, because none exist.

No system is perfectly secure. If a breach affecting personal information occurs, we will notify the affected Institution promptly so it can meet its own notification obligations.

10. Children’s privacy

Signet is a workforce tool for adult staff. It is not directed to children, and it is not designed or authorized to hold student education records. Accounts are provisioned through institutional staff directories.

11. Your choices

• Take your credentials with you. Signed in, you can download every credential you hold as a single standard Open Badges 3.0 file from your Backpack. It verifies anywhere that reads the standard and does not depend on us.
• You may release a place you hold at any time, from the session page or from the link in your confirmation email.
• You may ask the Institution to correct your name, role, or work site.
• You may ask the Institution about access, correction, deletion, or a copy of your records. Requests for records beyond your own credential export are fulfilled by the Institution, with our support — there is no self-service deletion, because these are the Institution’s employment records rather than a personal account.
• Some records — attendance findings and issued credentials in particular — may be retained by the Institution as employment or professional-learning records even at your request. That decision belongs to the Institution.

12. Changes to this policy

We may update this policy. When a change is material, we will make reasonable efforts to notify Institution administrators in advance. The effective date at the top of this page always reflects the current version, and superseded versions are available on request.

13. Contact

For questions about your own records, contact your Institution first — it decides what is collected and retained, and it is the only party that can correct or delete them. That is your organization’s Signet administrator.

For questions about the Service itself, or about this policy:

Pulse Pedagogies, LLC
[email protected]