Gather · Privacy notice
Gather, also called Accounting Team Upload, helps invited Brentwood and KHOC team members send accounting paperwork for review. This is a team-run intake tool, not the JW Hub website.
Information collected
Google sign-in supplies a verified email address to check whether an account is invited. Submissions include the selected account, document type, document date or “date not known,” any required amount, vendor or person, purpose, accounting month, optional notes and related submission number, and the chosen files. The service also records the upload time, submission number, file names, file checksums, review status and action history.
Google's basic profile permission also lets the site obtain the account's profile photo. For invited users, a small copy is saved in the private database and shown beside their submissions in the private dashboard. Profile photos are included in encrypted app backups. Google may also supply a name with this permission, but the app does not save it. Google passwords are not received or stored.
How the information is used
The information is used to deliver paperwork to the right accounting inbox, confirm receipt, link related paperwork and support accounting review. Receipt of a file is not purchase approval, reconciliation or audit signoff.
Profile photos help identify submitters during private review. Photos are not added to accounting documents, Drive submission summaries or Telegram alerts. A missing or unavailable photo uses an avatar placeholder and does not prevent sign-in. The saved photo is refreshed at sign-in; if no usable photo is available then, the previous saved copy is cleared. Contact the account servant through the team's usual channel to request removal. Earlier encrypted backups may retain a previous copy.
Where information goes
The site runs on a Hostinger server. Uploaded files pass through server memory and are saved in the controlled Google Drive intake folders, together with a submission summary. The site does not keep a separate permanent copy of uploaded file contents on its server. Submission details and action history are kept in its private database.
Google provides sign-in and Drive storage. The upload connection uses limited per-file Drive access, rather than full Drive access. Telegram receives a short alert containing the submission number, selected account and number of files. The alert does not include documents, file names, amounts, vendor names, submitter names or notes. These providers process information under their own policies.
Who can see submissions
The site limits submission records by the signed-in account. The administrator can review submissions across both accounts. Google Drive folder access is managed separately for authorized accounting document holders. Files are not made public by uploading them.
Cookies and device storage
The site uses temporary cookies for Google sign-in and the signed-in session. File previews are created in the browser before sending. No advertising or analytics tools are installed in this version.
Keeping and removing records
No automatic deletion schedule is currently configured. Accounting paperwork and related records may need to be kept for accounting and audit requirements. Contact the administrator to ask about access, corrections or removal. Removing the app's Google authorization does not automatically remove files already submitted.
Protect private details
Do not upload passwords, authentication tokens or unrelated private information. Redact bank-account and routing numbers before uploading statements; only the last four account digits should remain visible. Keep originals until filing is confirmed.
Questions
For questions about this tool or its records, contact the account servant through the team's usual communication channel.