Privacy policy

Who runs this site

ngsolve4you.com is the work site of the NationsGuard dealer services team, and "NG Dealer Services" is its Jira app. Only people on the team's staff list can sign in.

What the site keeps

• Staff list: your work email, your name and your role, which decide whether you can sign in.
• Sign-in codes: a scrambled copy of each six digit code, erased when it is used, after five wrong tries, or when it expires 10 minutes after it was sent.
• Sign-in attempts: the time of each code request and each wrong code, with the email and network address involved, kept for one day to stop guessing.
• Sessions: a scrambled copy of your session key, when it started and ends, your browser type and how you signed in. A session ends after 7 days, after 12 hours when "Keep me signed in" is unticked, or when you sign out.
• Passkeys: the public half of each passkey you add, a device label, when it was added and last used, and the network address and browser it was added from. The private half never leaves your device, and a removed passkey stops working at once while a record that it existed stays.
• Jira connection: your Atlassian account ID, Jira display name and Jira email, plus the access keys Atlassian issues, stored encrypted.
• Board order: the order cards are dragged into on the board, with the email of the last person who moved one.
• One-time checks used to finish a sign-in or a Jira connection, erased within minutes.

What the site does not keep

Your Jira requests, comments and emails stay in Jira. The site reads them when you open a page, using your own Jira login, and every change you make is saved in Jira under your name.

There is no advertising, analytics or tracking on the site, and no data is sold or shared for marketing.

Cookies and browser storage

• __Host-ngds_session keeps you signed in.
• ngds_pk remembers for 180 days that this browser was already offered a passkey. It holds no personal data.
• The width you drag the side panel to is saved in your own browser.

There are no other cookies.

Who else handles the data

• Cloudflare runs the site and its database, sends the sign-in code emails, and keeps request logs for troubleshooting for up to 7 days.
• Atlassian runs Jira, where the team's work lives. Atlassian's own privacy policy covers Jira.

How Jira access works

Each person connects their own Jira login once. The site asks Atlassian for permission to read and update the team's Jira work, to read Jira user names, and to stay connected without asking every hour.

The site acts on Jira only when you use it. Disconnect Jira from the account menu at any time and the site deletes your stored connection at once.

Weekly check with Atlassian

Once a week the site tells Atlassian which Atlassian accounts it holds, as Atlassian requires. If an account was closed the site deletes that connection, and if its details changed the site refreshes them.

How long data stays

Staff list entries stay while you are on the team. Removing someone from the list locks them out at once, and the weekly upkeep deletes their Jira connection, passkeys and sessions.

Everything else follows the times above, and the weekly upkeep clears anything past its time.

Security

The site runs on HTTPS only. Codes and session keys are stored scrambled, Jira keys are encrypted, and the staff list is checked on every request.

Your choices

You can sign out, remove passkeys and disconnect Jira from the account menu.

To see or delete anything else the site holds about you, contact Matthew Jackson at matthew.jackson2@hendrickauto.com.

Changes

When this page changes, the date at the top changes with it.