Privacy Policy
Effective date: · IMPACT Harvest Church
1. 本服務與聯絡方式
IMPACT Facilities 是 IMPACT Harvest Church 的場地申請與預約管理服務。本政策說明本服務處理的資料及其用途。問題或資料請求請寄至 admin@loveimpact.net。
2. 我們處理哪些資料
帳號資料:電子郵件、使用者識別碼、登入方式與驗證狀態;使用 Google 登入時,驗證服務也可能收到 Google 提供的姓名與個人資料照片。
申請資料:聯絡人姓名、Email、電話、填寫的郵寄地址、個人或機構名稱、與教會的關係、活動名稱與目的、預估人數與年齡層、房間、日期、時段及設備需求。
管理紀錄:審核與回覆、報價、合約內容及版本、電子簽署姓名、時間與同意紀錄、管理員手動登記的付款或奉獻金額、保險文件收件狀態,以及申請與管理權限變更的操作紀錄。
技術資料:提供主機與驗證的服務可能處理 IP 位址、瀏覽器資訊、請求時間及安全或錯誤紀錄,以提供及保護服務。
請勿在活動說明中填寫不必要的身分證件、醫療資料或其他人的敏感個資。
3. 資料用途與存取
資料用於登入驗證、聯絡申請人、審核活動、協調場地與設備、準備合約、記錄簽署及行政需求、防止濫用與排查問題。授權管理人員可依其權限查看及處理申請。
公開房間行事曆僅顯示房間及保留時段,不顯示申請人的姓名、聯絡方式或合約。
我們不出售個人資料,也不將 Google 登入資料用於廣告或訓練 AI 模型。
4. Google 登入
Google 登入只用於基本身分驗證,取得帳號識別、Email 與基本個人資料。本服務不要求讀取 Gmail、Google Drive 或 Google Calendar;也不會取得你的 Google 密碼。
我們使用從 Google 取得的資料時,將遵守 Google API Services User Data Policy,包括適用的 Limited Use 要求。
你可以在 Google 帳號設定中撤銷本服務的存取權;撤銷權限不會自動刪除已提交的場地申請或合約紀錄。
5. 服務供應商與必要揭露
本服務使用 Vercel 提供網站主機、Supabase 提供驗證及資料庫,並在你選用 Google 登入時使用 Google 的驗證服務。這些供應商會依服務功能處理必要資料,其自身的資料處理亦受其隱私政策及服務條款約束。
資料可能在你所在地以外處理。我們也可能在法律要求、處理爭議或保護帳號與服務安全所必要的範圍內揭露資料。
6. 瀏覽器儲存與安全
本服務使用瀏覽器儲存維持登入狀態與語言選擇。跳轉至 Google 登入前,申請表可能暫存在該分頁的 sessionStorage,以便回來繼續填寫;成功提交或登出時清除,超過一小時的草稿會在下次讀取時失效並清除。此暫存不包含登入密碼。
目前本 App 程式未加入廣告追蹤或第三方使用分析工具。主機與驗證供應商仍可能保留服務所需的技術紀錄。
本服務使用 HTTPS、登入驗證與資料存取權限,但沒有任何網路服務能保證絕對安全。使用共用裝置後請登出。
7. 保留、更正與刪除
我們會在處理申請、履行合約、管理財務、維護稽核紀錄或處理爭議及適用法律要求所必要的期間保留資料。
你可寄信至 admin@loveimpact.net 申請存取、更正或刪除資料;處理前可能需要確認身分。刪除由管理人員處理,不是目前 App 內的自動功能。部分合約、財務、法律或安全紀錄可能仍需保留,備份中的資料亦不一定立即移除。
8. 更新
若資料用途或功能有重要變更,我們會更新本政策及生效日期,並視需要在網站提供通知。新增整合若需額外資料存取,會另行說明並取得所需授權。目前本服務尚未與 Planning Center Calendar 同步。
1. Service and contact
IMPACT Facilities is the facility-request and reservation-management service of IMPACT Harvest Church. This policy describes the information handled by this service and why. Contact admin@loveimpact.net with questions or data requests.
2. Information we handle
Account information includes email address, user identifier, sign-in method and verification status. For Google sign-in, the authentication service may also receive the name and profile picture supplied by Google.
Request information includes contact name, email, phone, any mailing address provided, individual or organization name, church relationship, event name and purpose, expected attendance and age group, rooms, dates, time windows and equipment needs.
Administrative records include reviews and responses, quotes, agreement text and version, electronic-signature name, time and consent, payment or donation amounts manually recorded by staff, insurance-document receipt status, and logs of request actions and staff-permission changes.
Hosting and authentication providers may process technical information such as IP addresses, browser details, request times and security or error logs to deliver and protect the service.
Do not include unnecessary identity documents, medical information or other people's sensitive personal information in event descriptions.
3. Use and access
We use information to authenticate users, contact applicants, review events, coordinate rooms and equipment, prepare agreements, record signatures and administrative requirements, prevent abuse and troubleshoot problems. Authorized staff can access and process requests according to their permissions.
The public room calendar displays rooms and reserved time windows, not applicants' names, contact details or agreements.
We do not sell personal information or use Google sign-in information for advertising or training AI models.
4. Google sign-in
Google sign-in is used only for basic identity verification, including account identification, email and basic profile information. This service does not request access to Gmail, Google Drive or Google Calendar and does not receive your Google password.
Our use of information received from Google will adhere to the Google API Services User Data Policy, including applicable Limited Use requirements.
You may revoke the service's access through your Google Account settings. Revocation does not automatically delete previously submitted requests or agreement records.
5. Providers and necessary disclosure
The service uses Vercel for website hosting, Supabase for authentication and database services, and Google for authentication when you choose Google sign-in. These providers process information needed for their functions. Their own data handling is also governed by their privacy policies and terms.
Information may be processed outside your location. We may also disclose information as necessary to meet legal requirements, resolve disputes or protect accounts and service security.
6. Browser storage and security
Browser storage maintains sign-in sessions and language preferences. Before redirecting to Google sign-in, the request form may be saved temporarily in the tab's sessionStorage so you can resume it. The draft is cleared after successful submission or sign-out; drafts older than one hour expire and are cleared when next read. This draft does not include sign-in passwords.
The current app code does not include advertising trackers or third-party usage analytics. Hosting and authentication providers may still retain technical records needed for their services.
We use HTTPS, authentication and data-access permissions, but no online service can guarantee absolute security. Sign out after using a shared device.
7. Retention, correction and deletion
We retain information for as long as needed to administer requests, perform agreements, manage finances, maintain audit records, resolve disputes and meet applicable legal requirements.
Email admin@loveimpact.net to request access, correction or deletion. Identity verification may be required. Staff handle deletion requests; the current app does not provide automatic deletion. Certain agreement, financial, legal or security records may need to be retained, and information in backups may not be removed immediately.
8. Updates
For material changes to information use or functionality, we will update this policy and its effective date and provide website notice when appropriate. Integrations requiring additional data access will be explained separately and receive the necessary authorization. This service is not currently synchronized with Planning Center Calendar.