Privacy Policy
This is a draft for engineering, product, and legal review only, and is not legal advice. A privacy lawyer must review it and close every [TO CONFIRM] item before publication.
Last updated: [TO CONFIRM: day] November 2026. Version 2026-11-20.1.
Who we are
Home Community (the “Service”), at h-community.co.il, is operated by Yuval.B Development (“we”, “us”). We are responsible for the personal information described here. Privacy questions and requests: yovalban@gmail.com [TO CONFIRM: privacy contact address].
What this Service does
The Service helps house committees and residents manage a building. It covers apartments and building membership, monthly debts and special collections, expenses, budgets, receipts, and notices to residents. Payments are recorded in the Service by the committee or the resident, for example cash or check. The Service does not process card charges or online payments, and we do not collect card details. A volunteer committee house committee manager can issue a receipt through the Service.
In short
We collect three kinds of information:
Information you give us, such as name, email, phone, password, and files you upload. Information others give about you. Mostly the building committee, when it sets up the building or adds residents. Google also shares some information if you sign in with Google. Information collected automatically while you use the Service, such as cookies, IP address, device type, and security logs. We use the information to run the Service for your building. We do not sell personal information, and we do not use advertising or analytics cookies. The sections below cover each topic.
Information you give us
Account: name, email address, and password if you register with email. We store only a secure hash of the password, never the password itself. Mobile phone: stored encrypted. We also keep a one-way encoded form of it (keyed hash) for exact matching. Matching is used to prevent duplicate accounts, to link you to records the committee already created for you, and to honor SMS stop requests. We also store the phone country so the phone field can show the right default. Preferences: interface language, avatar color, notification and email choices. Profile photo, if you uploaded one or accepted your Google photo. New building setup: email, name, building address, apartment count, chosen plan, phone, and password. These are kept in a draft until the building is created. An unfinished draft expires automatically after 3 days. Content you add in the Service: payment records and notes, receipt images or PDFs, expense and refund documents, check details, budget notes and approvals, and budget chat messages. Your choices: that you accepted the privacy policy (version, date, and a hashed form of the IP address), and whether you opted in to marketing messages (optional).
Information we receive from others
The building committee may enter or import resident details before those people join: apartment number, names, phone numbers, email addresses, move-in date, monthly amounts, prior debts, and notes. The committee may also send you an invitation by SMS, email, or WhatsApp. Those details create a temporary profile for you in the building. When you register and verify the same phone number, the temporary profile and its debt history join your account. The committee is responsible for having a right to give us that information [TO CONFIRM with counsel: lawful basis and notice duties for committee-supplied data]. Other building members may record a payment you made, approve or decline a payment, or mention you in a budget discussion. Google, if you choose “Continue with Google”. See “Google Sign-In” below. Apple, if you choose “Sign in with Apple” and the option is enabled [TO CONFIRM: live in production]. Apple may share a name and email address, or a Hide My Email relay. We use that only to create or sign in to the account, under the same limits as Google Sign-In. See https://www.apple.com/legal/privacy/.
Phone and email verification
To confirm a phone number or email address, we send a 6-digit code. We store only a hashed form of the code. It expires after 10 minutes, and attempts are limited. Expired codes are deleted every day. When you change email or phone in Settings, the new value is stored as “pending” and does not enter the profile until you enter the code. On a building’s quick-pay page, we may send a one-time email code to confirm it is you.
SMS messages
The Service may send these SMS messages: a phone verification code, a welcome message after registration, and reminders about open building debt. Reminders may be sent automatically, up to twice a month, or by the committee, up to once a week. The sender name in code today is “ועד בית אפליקציה” [TO CONFIRM: update the sender name to “Home Community”]. We keep a log of every SMS we attempt to send: the phone in encoded form, the building, the message type, the full text, status, and time. For verification messages the text includes the one-time code, which expires after 10 minutes [TO CONFIRM: plan to stop storing codes in the log]. You can stop SMS to your number through the unsubscribe link when it appears in a message (currently in resident invitations), or by contacting us [TO CONFIRM: unsubscribe link in every SMS template]. After a stop, we keep the encoded number on a block list so we do not send to it again. SMS provider: [TO CONFIRM: no SMS provider connected yet; name it here when chosen].
Marketing messages
At signup you may tick an optional box to receive marketing information from Home Community. The box is not pre-checked. We store whether you consented, the exact wording shown, where it was shown, the version, and the date. A continuation message to someone who started buying a building plan and did not finish is sent only to someone who checked consent to advertising. The message is labeled פרסומת and includes an unsubscribe link. You may withdraw consent at any time by contacting us, or through the unsubscribe link. There is no in-app setting to withdraw today. Service messages such as receipts, codes, and debt reminders are not marketing.
Google Sign-In
If you choose “Continue with Google”, Google authenticates you. With your consent, Google shares the Google account email address, display name, and profile photo URL. We request only the basic sign-in scopes: identity, email, and public profile. We do not request access to Gmail, Drive, contacts, Calendar, or other Google content.
We use this information only to create or sign you in to your Home Community account, to show your name and email in the Service, and — if you accept on the next screen — to copy your Google photo as your avatar. If you skip the photo, we delete the temporary photo link and do not keep it. Our sign-in library also stores the link between the Google account and the Home Community account, together with the sign-in tokens Google returns [TO CONFIRM: plan to stop storing those tokens].
We do not sell Google user data. We do not use it for advertising, remarketing, credit scoring, or sale to data brokers. We do not share it with third parties except processors needed to run the Service. You may revoke the Service’s access at any time at https://myaccount.google.com/permissions. Revoking access does not delete your Home Community account. Google’s processing is described at https://policies.google.com/privacy.
Building, membership, and money
We store your role in each building, such as resident, committee, or budget-group member. We also store the apartment, move-in and move-out months, join and residency checks, and join codes that were used. Join codes are stored encrypted and hashed.
For money we store monthly debt, special collections, recorded payments (amount, date, method such as cash or check, check numbers, notes, payer, approval status), expenses, budgets, refunds, and opening balances. These are the records the committee needs to manage the building accounts.
Receipts and signatures
When a house committee manager signs a receipt, a refund, or a budget approval, the drawn signature image is stored encrypted. A PIN lets the signer reuse the saved signature. We store only a hash of the PIN. PIN reset uses a one-time email link; we store only a hash of the link and a hashed form of the IP that requested it. A receipt the Service issues shows the payer name, apartment, amount, receipt number, and the house committee manager’s signature.
Files you upload
Files you upload may contain personal information. They include receipt images or PDFs, expense, refund, and check attachments, profile photos, and import spreadsheets. Before a file is stored, it is checked for viruses and inappropriate content (see “Security scanning” below). It is then converted (images to WebP; PDFs are cleaned) and stored privately in the building’s folder. Each building has a storage limit. Storage is on a server in Oracle Cloud in Jerusalem, and the data stays in Israel. Files are stored in the storage/uploads folder. When a building is closed, we create an export ZIP. It includes a budget summary, expenses, resident balances with names and emails, and action history (including IP address and user agent in history_actions.csv). The file is emailed to the committee with a download link valid for 7 days.
Security scanning (Cloudmersive)
The following files are sent in full to Cloudmersive, which checks them for viruses and malicious code: receipt images and PDFs (payments, expenses, refunds, and checks), profile photos you uploaded or accepted, and spreadsheets you uploaded for import. This happens even when the AI option is off. Receipt images and profile photos are also sent as a JPEG copy for a separate inappropriate-image check. A receipt PDF is sent for that check after our PDF processing. Spreadsheets are not sent for the image check. The scan is for security only; Cloudmersive does not read the data for import. Signatures drawn in the Service, receipts and budgets the Service generates, and building-close export files are not sent to Cloudmersive. Support request text is sent to Cloudmersive for an offensive-content check. A screenshot attached by a signed-in user is sent for a virus check and an inappropriate-image check. Cloudmersive processing country and deletion timing: [TO CONFIRM].
Support requests
A support request stores the subject, the message, and the page it was sent from. A guest also provides an email address. A signed-in user also has their name, account email, building, apartment, and role stored with the request, and a screenshot when they attach one. The message text is checked by Cloudmersive for offensive content. A screenshot is checked by Cloudmersive for viruses and inappropriate content. The request is stored in our database. Platform operators can read it on the support requests page. An email notice is sent to the support address. How long we keep a support request: [TO CONFIRM]. You can ask to view, correct, or delete it.
AI spreadsheet mapping (Groq)
When AI mapping is enabled for a resident or expense spreadsheet, and a committee member has consented, we may send Groq a JSON request. We record who consented and when. The only text from the file in the request is tab names and column headers. The request also includes tab ids, column positions, the import type, and the allowed target fields. We never send the file itself, data rows, cell values, formulas, or examples, including on a retry. Labels that look like an email address or phone number are hidden before sending.
Groq returns a proposed structure for each tab: use, ignore, or clarify, a role, which column maps to which field, and proposed links between tabs. It does not return code. Our servers then read the rows you approved, check them against the building, and create the records. If the AI request fails, mapping falls back to the local or manual path, and we do not send a wider request. Tab names and headers may still include personal information, so general labels are recommended. This section needs review by a privacy lawyer.
We send email about events such as receipts, pending approvals, fee changes, shared expenses, debt reminders, refunds, apartment changes, residency checks, building close or disconnect, verification codes, and password or PIN resets. You can turn most email and notification types on or off in Settings. Security and account messages may still be sent. Email is sent through an SMTP email provider [TO CONFIRM: provider name]. Group email may go through a queue service, Upstash QStash. It receives the message type, internal building and user ids, and the values that fill the message.
Cookies and browser storage
We use only cookies the Service needs to work. There are no advertising cookies and no third-party analytics. The cookies are:
the signed-in session (about seven days) and sign-in security cookies; interface language; the building you are currently working in (180 days); short cookies that remember a join, signup, or building-setup flow in progress; a short signature-PIN session for signers; a short quick-pay session; a rate-limit cookie against abuse. Platform operators also have a few internal cookies for admin tools. The browser may also store display preferences and dismissed notices in local or session storage. On a first visit, we may use the country the hosting provider detects from the IP address to choose a default language.
Security logs, IP address, and device
Sign-in attempts are logged with the email, outcome, sign-in method, and a hashed IP address. Repeated failures may temporarily block the hashed IP. Visits by signed-out users may be counted by hashed IP and device type to limit abuse. Building action history records who did what, before and after values, and the full IP address and browser type. The committee can see it for accountability. If signup checking (Cloudflare Turnstile) is enabled, Cloudflare receives the IP address and a check token to confirm you are not a bot [TO CONFIRM: live in production]. The hosting provider keeps technical request and error logs. They may include IP addresses, and in error messages also names of uploaded files [TO CONFIRM: log retention period]. You can sign out of all devices in Settings.
Who receives the information
Building members see what their role allows. The committee may see resident names, apartments, payment status, and phone numbers when using contact or debt tools. Platform operators (our team) may access information needed to run, support, and secure the Service. Processors that handle information for us: Oracle Cloud, Jerusalem region: the server, the database, and uploaded files. The data stays in Israel. After deletion, copies may remain in backups for up to 28 days, until they are deleted automatically. Backups are used only to restore the system after a failure, and a deleted building cannot be restored from them. Email delivery provider [TO CONFIRM]. Upstash QStash: email queue. Cloudmersive: file security scanning. Groq: AI mapping of spreadsheet headers, only when the option is on. Google: sign-in, when used. SMS provider [TO CONFIRM: not chosen yet]. Apple and Cloudflare, if those options are enabled. Other services we use: When you type a building address, we look it up in Israeli government address datasets (data.gov.il / GovMap). We send only the address text. Phone-field flag icons load from flagcdn.com, which sees the browser IP address. Some processors handle information outside Israel, including in the United States [TO CONFIRM with counsel: transfer basis]. We do not sell personal information.
How long we keep information
Verification codes: 10 minutes, and deleted daily after they expire. Someone who started buying a building plan and did not finish: the details are kept so they can continue. Unverified details are deleted within 3 days. Building-close download links: 7 days. Residents left without an apartment may move to a former-resident list after 30 days. Building records, including the ledger and receipts, are not kept for 7 years. They are deleted when the building deletion described below runs. Access logs and action logs are kept for 24 months from the day they were created. In those logs the personal name and email are replaced with an identifier. Login records are kept for 24 months. When an account is deleted, the password and sign-in methods are deleted immediately. Phone and email are kept while the user owns an apartment or has an open debt.
When a building subscription ends
When a subscription ends, the building is read-only for 12 months. Every registered committee member is notified 90 days and 30 days before deletion, by email and in the app. The notice is sent even if that email type is turned off. Before deletion the committee receives a full ZIP (ledger as CSV, and receipt files as stored) by a secure link that requires sign-in and expires. The ZIP is not an email attachment. Deletion runs only after that notice was delivered and the ZIP is on the link. If there is no committee, we record the failure and do not delete. The committee can also request immediate deletion: the same ZIP, then the same deletion. If a receipt file is missing, the ZIP includes missing_files.txt and the notice names it. A committee member who joined after the 30-day notice receives the link that is still valid, and deletion does not wait for that member. Data is stored in Oracle Cloud in Jerusalem and stays in Israel. We delete the building data we store. After deletion, copies may remain in backups for up to 28 days, until they are deleted automatically. Backups are used only to restore the system after a failure, and a deleted building cannot be restored from them. Security logs are kept for 24 months. When the link expires, the ZIP, the export row, and the deletion-notice records are deleted. The in-app notice that stayed with the user is not deleted. After delivery, the committee (the data controller) is responsible for keeping the records as required by law. What remains: every access log and action log for 24 months from the day it was created, with an identifier and no name or email, and a record of what was sent, when, to whom, and that the deletion ran. An immediate-deletion notice stays with the committee member, without the building name and with no automatic deletion date. After the link expires the file no longer opens. An unnamed building row, without a name or address, stays. Plan purchase records are kept for 7 years: the payer name, the amount, the date, the plan, the document number, and the payment method (type only, no card details), without resident data. The leaving question is optional. We keep only the selected reason, the month, and the plan type, stored separately, without a name, address, building ID, or user ID, for up to 36 months.
Access and correction
You can ask to see the information we hold about you, or to correct it, through Request to access or correct personal information or by email at yovalban@gmail.com. We reply within 21 days, at no charge. Information entered by the building committee, such as a debt, an apartment assignment, and whether someone is an owner or a tenant, is the committee's responsibility. We will pass the request to the committee and update you.
Account deletion and your rights
Account deletion has its own support subject. There is no self-serve deletion in the app today.
When we delete an account, we first email you copies of your receipts. The password and sign-in methods are deleted immediately. In records that are kept, the personal name is replaced with an identifier. Phone and email are kept while the user owns an apartment or has an open debt. Login records are kept for 24 months. Action records and financial records are kept. A sole building admin must transfer the role first. We may also keep information the law requires us to keep.
How we protect the information
Information is sent over HTTPS. Phone numbers, signatures, and join codes are stored encrypted. Passwords, PINs, one-time codes, and reset links are stored only as hashes. IP addresses in login and security records are stored in encoded form, except in building action history. Sign-in cookies are secured, and page scripts cannot read them. No system is completely secure.
Children
The Service is intended for adult residents and house committees, not for children.
Changes
We may update this policy. When we make a material change, we will post it here with a new date and version, and we may ask you to accept it again.