The short answer: your timesheet data stays in your own Google or Microsoft 365 account. WeekClose runs inside your spreadsheet. We have no servers that receive your punches, names, hours or pay rates, and no database to hold them.

Where does WeekClose run?

Google Sheets: inside Google Apps Script, attached to the one spreadsheet you open it in. The calculation happens in your Google account.

Excel: inside Excel's add-in pane. The pane's program files load from weekclose.com, like any web page, along with Microsoft's own Office.js library that every Excel add-in uses. Your workbook data is read and calculated inside Excel and is not sent to our website or anyone else; an automated test fails the build if our Excel code ever makes a network call.

What can WeekClose see in a Google account?

Only the spreadsheet you open it in. It asks Google for three permissions:

It cannot open your Drive, Gmail inbox, Calendar, contacts or other files.

Does WeekClose change our punches?

No. It never edits or deletes your rows. Results go to tabs WeekClose creates and marks as its own; it will not write over a tab you made, even one with the same name.

Does anything get sent anywhere?

Only the supervisor emails you choose to send, from your own account, to the supervisor addresses on your Departments tab. WeekClose shows you the list first, sends nothing until you press Send, and refuses to send if the Departments tab changed after you looked at the list. In Excel, emails go out through a Power Automate flow in your own Microsoft 365, which you set up and control.

Where are supervisor approvals stored?

In a form you create in your own Google Forms or Microsoft Forms, linked to your own spreadsheet. WeekClose reads those responses inside your spreadsheet and writes an Approvals tab. We never see them.

Who can approve a timesheet? Can it be faked?

Set the approval form to require sign-in (organization accounts only) so the approver's account and the form's own timestamp are recorded. Each timesheet carries a short check code of its numbers; if a punch changes after approval, WeekClose marks it "Changed after approval". If someone other than the listed supervisor approves, it is marked as approved by someone else.

Phone clock-in: where do punches go?

Into your own Google Form or Microsoft Form, which writes to your own spreadsheet. The WeekClose Punch page is a plain web page that opens your form. Its setup travels after the # in the link you give employees, a part of the address browsers do not send to our web host. On the employee's phone, the browser keeps their name, department, last tap and the setup link, and nothing else; "Forget me on this phone" clears it.

How does the license work? Does it phone home?

No. A license key is checked offline, inside the add-in; there is no license server. Your purchase is handled by the payment service we send you to, which sees the buyer's name, email and payment as any store does. It never sees your timesheets.

Analytics, tracking or AI?

No tracking code, no analytics, no AI calls on your data. Google and Microsoft show us install counts for our store listings; that is all we see. This website sets no cookies and loads nothing from other companies.

What if we stop using WeekClose?

Remove the add-in. Your punches and every tab WeekClose made stay in your spreadsheet as ordinary cells. Nothing to export, nothing held by us.

Audits and paperwork

WeekClose has not had a SOC 2 audit or a penetration test; we hold no customer data, so most of a SOC 2 would not apply. For a security questionnaire, W-9 or vendor forms, email support@weekclose.com.