How Rivetway and Rivetway Driver Hours handle personal information.

Who is responsible and how to contact us

Dave Langstead, trading as Rivetway, operates the standalone Rivetway Driver Hours app and is responsible for its account and service data. For privacy questions, access, correction or deletion requests, email davidlangstead@rivetway.com or use the Rivetway contact form. For information entered into an employer's Rivetway fleet workspace, the employer or customer organisation decides how that operational information is used.

Information we may process

The service may contain information needed to run fleet operations.

• Account details such as name, email address and role.
• Driver, staff, vehicle, job, customer, workshop and compliance records entered by authorised users.
• Operational evidence such as uploaded documents, images, dates, notes and audit history.
• Technical information needed for authentication, security, reliability and support.
• Contact-form information when somebody asks a question or requests free-trial access.

Rivetway Driver Hours: information you provide

Rivetway Driver Hours is a separate driver-hours companion with its own account system. The current Android app processes:

• Your email address, account identifier and authentication information when you register, sign in or recover access. Your password is handled by the authentication service; never send it in a support request.
• Your driving-rules profile: ruleset, home country, timezone, vehicle or combination type, typical operation, working-time reference period, night-work setting and acknowledgement of the legal-record notice.
• The activities you record, including driving, other work, breaks, periods of availability and rest, their start and end times, shift history and related record identifiers.
• Calculated hours summaries, warnings and remaining-time guidance based on the activities and settings you provide, plus acknowledgement of warnings on your device.
• Beta or service-access status, synchronisation identifiers, timestamps and errors, and technical request information processed by our authentication and hosting providers, including IP addresses, browser/device information, response timings and approximate city or country inferred from IP addresses, for security and service diagnostics.
• Information you choose to provide when contacting us. Please avoid unnecessary sensitive information in free-text fields.

Rivetway Driver Hours: why we use this information

Account and profile information lets us provide your requested account, authenticate access and apply the rules you select. Activity records let us display your timer, history and hours guidance and synchronise records between the device and your account. We use necessary technical information to prevent abuse, investigate faults and answer support requests. Account information is required to use the connected service; vehicle type and typical-operation text are optional. Calculations are guidance based on your entries, not an approved tachograph record or an automated employment decision.

Rivetway Driver Hours: storage on your device

The app keeps your sign-in session, cached profile and activity history, pending offline activity commands, synchronisation status and warning acknowledgements in local app storage. Pending activity commands are sent to the Rivetway Driver Hours service when connectivity and authentication permit. Successfully acknowledged commands are removed from the pending queue; the resulting activity history remains in your account and may be cached. Signing out does not erase all cached or pending records. Clearing Android app storage or uninstalling may permanently remove unsynchronised entries, so check synchronisation first if you need to keep them. Removing the app does not delete your server account.

Rivetway Driver Hours: permissions and optional features

The standalone Android app records activities that you select manually. It does not request access to GPS location, contacts, camera, microphone or SMS for this workflow. PDF Save uses Android's system document picker; Share opens your chosen app with a temporary grant for that PDF, rather than broad file access. Google Play handles optional subscriptions. When advertising is enabled, the Google Mobile Ads SDK may process device identifiers and network information, including approximate location inferred from IP. This does not require precise GPS permission. The public-website analytics described below are separate from the app's activity recorder.

Rivetway Driver Hours: games, Coach and planning records

Four optional games and Coach & Academy lessons store scores, completed levels, achievements, lessons marked read and a bounded learning history on your device, separately for each signed-in app account. Learning history contains the lesson, time answered and whether an answer was correct. Reference-period work and leave entries and explicit rest-compensation allocations are also stored locally for your account. These features do not upload their local practice or planning records as fleet or employment records and do not change recorded activities. Learning scores are not a compliance score, qualification or training certificate. These local records are not currently backed up to your account; clearing app storage removes them.

Rivetway Driver Hours: weekly reports

Weekly PDFs are generated on your device from available activity records, including offline. Enhanced reports may include detailed entries and comparisons. Reports show incomplete or unverified history and are not approved tachograph records. You choose whether to save a PDF and where, or which app or recipient to share it with. We do not automatically upload PDFs. Android may retain a temporary sharing copy in private app cache; older sharing copies are cleaned when another report is shared, and Android can clear its cache. Copies you save or share outside the app are controlled by your chosen destination and are not removed by deleting your account.

Rivetway Driver Hours: Google Play subscriptions

If you choose a Pro subscription, Google Play processes your purchase and payment information. We receive purchase evidence, product, subscription state and expiry needed to verify and restore access. We associate the purchase with your app account using a pseudonymous identifier and verify it with Google. Verification records include an encrypted purchase token, token hash, account association and verification time. We do not receive your payment-card or bank details through this purchase flow. Necessary verification records support access, restoration and fraud prevention, subject to the retention and deletion principles below. Manage or cancel renewal in Google Play; deleting the app or requesting account deletion does not itself cancel a subscription.

Rivetway Driver Hours: advertising and your choices

When advertising is enabled, eligible Free users may see Google AdMob banners in designated non-driving areas. The app requests Google's consent information before eligible display and uses consent choices where required. Advertising privacy choices are available in Settings when safely parked. Essential timers, warnings, games and basic lessons remain available when advertising is unavailable. Pro and eligible company access remove advertising. Advertising SDKs may process IP-derived approximate location, device or advertising identifiers, interactions and diagnostics for advertising, measurement and fraud prevention according to applicable choices and rules. The app does not send your recorded activities, game scores or Coach answers to AdMob as advertising data. Google's privacy information is at https://policies.google.com/privacy. Withdrawing consent stops consent-based future processing; it does not remove records already processed lawfully.

Rivetway Driver Hours: service providers and access

Rivetway Driver Hours uses Supabase for its separate authentication and account-data services, with its primary database in London, United Kingdom, and Vercel-hosted Rivetway API infrastructure to process activity records and calculate guidance. Hosting, authentication, database and transactional-email providers process information needed to perform these services. Vercel processes personal service-generated request metadata as an independent controller for operating, securing and improving its services, as explained at https://vercel.com/legal/privacy-notice; customer account and activity content is processed on Rivetway's instructions under the applicable data-processing terms. Authorised support personnel may access information where necessary to resolve a request, maintain the service or meet a legal obligation. The standalone app does not automatically add its records to an employer's FleetOS workspace. Public-website analytics is a separate, optional activity described below.

Rivetway Driver Hours: retention and account deletion

To request deletion of your Rivetway Driver Hours account and associated data, email davidlangstead@rivetway.com with the subject 'Rivetway Driver Hours account deletion', preferably from your registered email address. You can also use the Rivetway contact form and state that you want your Rivetway Driver Hours account deleted. No app installation is needed to make a request. We may need to verify that you own the account; do not send your password. Existing requests headed 'Tacho Mate account deletion' are also recognised.

• The request covers your Rivetway Driver Hours sign-in account, driving-rules profile, activity and shift history, access and subscription-verification records and associated service data. You can also request access, correction or deletion of particular information without asking to close the account.
• Account and activity information is retained while needed to provide your account and history, handle your requests or meet applicable legal obligations. A beta or trial ending does not automatically erase your records.
• Where information must be retained for a specific legal obligation, security investigation or legal claim, we will explain the reason and applicable retention period or criteria when handling the request. Rivetway Driver Hours uses daily Supabase database backups with a rolling seven-day recovery window. Deleted information can remain in these restricted recovery copies until they expire from that window; it is not used for normal service operation. If a backup is restored, completed deletion requests must be reapplied before normal service resumes.
• Local copies on your devices are separate from server records. After preserving any records you need and completing your request, clear the app's Android storage on each device to remove remaining local copies. Uninstalling alone is not an account-deletion request.
• Local game and learning history, reference-period and compensation planners, and saved or shared PDFs are separate copies. Preserve records you need before clearing local data. Google's transaction records are controlled separately; cancel any subscription renewal in Google Play.

Why it is used

Information is used to provide and secure the service, operate customer workspaces, keep accountable records, answer support requests, improve service reliability and meet legal obligations that apply to the operator.

Lawful bases for processing

We use information necessary to provide the account and service you request to perform our agreement with you. Necessary security, fraud prevention, fault investigation and support processing serves our legitimate interests in running a secure and reliable service. Where a legal obligation requires processing or retention, that obligation is the basis. Optional website analytics relies on your consent. Customer organisations are responsible for identifying the basis for operational information they control in their fleet workspace. Where consent is required for optional app advertising, we request it through the advertising consent controls. You can review those choices in the app.

Company responsibility

A customer organisation decides what operational information its authorised users enter into its workspace. Organisations should only record information they are entitled to use and should apply their own employment, fleet and privacy procedures where required.

Storage and service providers

Rivetway uses specialist hosting, database, authentication and email providers to operate its services. The fleet service and standalone Rivetway Driver Hours have separate account/data boundaries. Providers may process information outside the UK as part of hosting, support or service delivery. Supabase and Vercel's data-processing terms include Standard Contractual Clauses and the UK international-transfer addendum for relevant restricted transfers. Their terms and subprocessor details are available at https://supabase.com/legal/dpa and https://vercel.com/legal/dpa. Contact davidlangstead@rivetway.com for further information or a copy of the applicable safeguards. A UK database region does not mean every supporting operation is UK-only.

Retention and deletion

Operational records are not silently deleted merely because a free trial ends. Retention, export and deliberate offboarding are handled separately so important business records are not unexpectedly lost. Personal information should not be kept longer than needed for its purpose or applicable legal requirements.

Security

Rivetway uses authenticated access, role-based permissions, workspace separation, audit mechanisms and automated engineering checks. No internet service can promise absolute security, and sensitive implementation details are intentionally not published.

Your rights

Depending on the circumstances, UK data-protection law provides rights of access, correction, erasure, restriction and data portability. You may object to processing based on legitimate interests and withdraw consent to optional analytics at any time. Contact davidlangstead@rivetway.com or use the Rivetway contact form. You can also complain to the Information Commissioner's Office at https://ico.org.uk/make-a-complaint/.

Cookies and local device storage

Rivetway may use browser storage needed for authentication, selected workspace, accessibility preferences, offline/PWA behaviour and trial setup. Marketing or advertising cookies are not required for core service operation. Our consent choice is stored on this device for up to 180 days.

Optional website analytics

Only after you accept analytics, Google Analytics (provided by Google) measures visits and interactions on public pages using the _ga and _ga_S7LJ06M095 cookies, each set to expire after 180 days and renewed on use. It receives public page paths, referral origin, device/browser information and network information such as your IP address to process the request. We do not send account IDs, job details, form contents, query strings or URL fragments. Advertising storage, Google signals and advertising personalisation are disabled. Google may process analytics data outside the UK; its privacy information explains its processing and international safeguards. The current Analytics settings retain event-level data for 2 months and user data for 14 months, with the user-data period renewed on activity. Aggregated reports are governed separately and may remain available longer.

Analytics choices and signup attribution

Choose Accept analytics or Reject analytics in the cookie banner. Cookie settings on public pages lets you withdraw or change your choice; withdrawal stops future website analytics and removes its cookies from this browser. Rejection does not affect access to Rivetway. With analytics consent, our existing random signup-attribution ID may be stored locally and linked to signup and operational activation milestones; this ID is not sent to Google. Historical reports and previously recorded business activity are retained separately. Contact us about access or deletion of personal data. Google's privacy notice is at https://policies.google.com/privacy.

Updates

We will update this notice when our services or data practices change and show the revision date on this page. Material changes to Rivetway Driver Hours's collection or use of data will be explained before the changed processing begins.