Terms of Use

These Terms govern your use of this event website (https://inviteberry.com), operated by Elena Kravtsova (registered sole proprietor (עוסק) in Israel). You accept them at the specific moments the site asks you to: when you submit an RSVP, when you enter a photo gallery and accept its rules, when you give the uploader's undertaking before adding photos, when you place an order, and, if you are an event organiser, when you sign in to the organiser panel. Simply browsing the site does not, by itself, create an agreement. If we change these Terms in a way that matters, you will be asked to accept the new version at the next such moment; we do not treat continued use as agreement.

What the site is

A private, invitation-based platform to view event information, submit and update an RSVP, access an event photo gallery, and, where offered, make event-related payments. A gift to the hosts is not one of those payments (see Gifts to the hosts below). Some areas require an invitation link or access credentials.

Eligibility & accounts

You must be 18 or older to submit an RSVP or make a payment, and 16 or older to sign in to the photo gallery; guest accounts may not be created for anyone younger. Information about children is entered by an adult guest.
Photo-gallery access uses a username and access code. Unless the hosts explicitly issued it as a shared one (a vendor team, a venue screen), the credential is personal: do not pass it to anyone else, keep it confidential, and you are responsible for activity under your access.
Access can be suspended or revoked (including photo view and upload bans) for misuse, and the event’s hosts can close a guest’s gallery access or uploads for reasons of their own. A closure because a named rule was broken or the law requires it always comes with its ground and how to contest it; a closure for the hosts’ own reasons is explained to the person only where the hosts choose to (see "Gallery rules").

Acceptable use

Do not upload unlawful, infringing, harmful content or others’ private content without consent.
Do not access other events/guests’ data, probe security, scrape, or disrupt the site.
Do not misuse the messaging or contact-upload features.

Your content

You keep ownership of content you submit. You grant us a non-exclusive, royalty-free licence for exactly these purposes and no others: storing your content, showing it to the people given access to this event's gallery (its guests and those the hosts let in by name), creating thumbnails and technical derivatives, assembling a photo-album PDF, and passing files to our print partner to fulfil an order you placed. The licence ends for a photo when you delete it, subject only to backups clearing (at most 14 weeks) and to copies we must keep by law. It also ends, for every photo you uploaded at once, if you ask us to remove your data from an event: carrying out that request deletes your uploads from that gallery for everyone who could see them, not only from your own view. That is the one consequence of the request that is not obvious, so we say it here as well as in the gallery rules: download anything you want to keep before you ask. We do not sublicense your content to anyone except the technical subprocessors and the fulfilment partner named in our Privacy Policy, and we do not use it in marketing without your separate, explicit opt-in. You are solely responsible for any images and media you upload, including venue, event and personal photos, and you undertake to upload only content you are allowed to share: content that, as far as you know, nobody who can be recognised in it objects to, that breaks no agreement or restriction on publishing it, that infringes nobody else's rights, and that contains nothing unlawful. This undertaking is your promise to us; it is not permission given on behalf of anyone else, and it never overrides the right of a person in a photo to have it removed. If you use the service in the course of a business, for example as a planner, photographer or venue acting for a client, you also indemnify us against claims arising from a breach of this undertaking. A guest, and a host organising their own event privately, gives no such indemnity. The gallery is private to the event. Anyone who appears in a photo can ask us to remove it via [email protected], or through our report form at https://inviteberry.com/legal/report, which is open to anyone and does not require an account. We use automated tools to screen uploads for illegal and explicit material; anything they flag is hidden and reviewed by a person, and nothing is deleted automatically on their say-so. The one exception is a match against the fingerprint of material already removed, re-saved or resized copies included, which is refused or removed automatically rather than hidden for review. We close gallery access for anyone who repeatedly uploads material that infringes somebody else's rights.

Gallery rules

Entering an event gallery requires accepting its rules for the current version of this wording: a checkbox on the way in, once per guest, asked again whenever this wording changes; a code shared by several people is asked every time. The rules are:

Do not sell the photos or use them commercially.
Do not post them on social media or share them outside the people given access to the gallery.
Do not pass your access code to anyone else.
Do not mass-download or scrape the gallery.
Do not use the photos for AI training, biometrics or recognising people. The gallery's built-in "find photos of me" feature is the one exception; it runs only with your separate consent and only searches for you.
Do not edit photos in a misleading or demeaning way, and do not create deepfakes.
Do not upload a photo that could humiliate or degrade a person in it, that shows an intimate moment, or that shows a child in a situation that could embarrass them.
Do not remove authorship or credit information.
Do not upload photos you have no right to, or anything unlawful.
Upload photos taken by a photographer hired for the event only with the hosts' agreement: unless agreed otherwise, photos commissioned for a private event belong to whoever commissioned them, which is normally the hosts.
Do not try to get around access controls.

The gallery is not available to anyone under 16, and guest accounts may not be created for them. If you are under 18, you need the consent of a parent or guardian to use the gallery. When these rules are broken, the material concerned can be hidden or removed, and access to the gallery can be closed where a breach is serious or repeated. When a photo you uploaded is removed, whether on somebody's request or for breaking one of these rules, the gallery tells you what was removed, on which ground, and whether and how you can contest it, wherever telling you would not expose the person who asked. When the hosts close your access to the gallery or your uploads because a named rule was broken or the law requires it, you are told so, on which ground, that a person decided it, and how to contest it: at your next sign-in, or in the gallery itself while you can still see it. When they close it by the hosts' own decision, which is not a finding that you broke anything, you are told so only if the hosts choose to; otherwise a closed gallery tells you only that your access is closed, and closed uploads show no message. To contest a decision about your photos or your gallery access, write to [email protected]: a person reads it and replies. A breach can also expose you to claims from the people who own the photos or appear in them, which are theirs to bring, not ours.

Where the hosts have enabled it, you can also like a photo (the heart). A like is a public act: the gallery shows the other guests how many people liked that photo, though never who, and never at all until at least three guests have. Saving a photo (the bookmark) is a different thing and stays private to you. Un-liking withdraws the like and lowers the count.

Asking for a photo to be removed

If a photo in a gallery shows you or your child, you can ask for it to be removed from the gallery itself, at [email protected], or through our report form at https://inviteberry.com/legal/report, which is open to anyone and needs no account. This is how such a request is handled, and we hold ourselves to it:

The photos you name are hidden from the gallery as soon as you ask, before anyone has decided anything.
Ordinary requests go to the event's hosts, who have 7 days to answer. They are reminded partway through.
If they do not answer in time, the photos are removed and blocked from being uploaded again.
If they decline, they must give a reason, you are shown it, and you can ask us to review the decision. Our decision is then final.
A request about a child, about intimate images shared without consent, or about unlawful content does not go to the hosts at all: it comes straight to us.

You do not need to go through the hosts first: you can bring any request to us directly at [email protected], and we will act on it whatever the hosts think. Where we cannot establish the facts, we remove the photo, because a picture kept up over the objection of the person in it cannot be un-shown, while one removed in error can be uploaded again by whoever owns it. A complaint that a photo infringes your copyright, rather than one about appearing in it, goes through our copyright policy at https://inviteberry.com/legal/dmca. Nothing here limits any right you have under the Protection of Privacy Law, 5741-1981, the GDPR or any other law that applies to you.

What "removed" means: the photo stops being visible to anyone in the gallery immediately. We keep no copy of it. If a removal turns out to have been wrong we reverse the decision itself: the block on that image is lifted, and whoever uploaded it can upload it again from their own file. A request about a child, about intimate images shared without consent, or about unlawful content follows the separate procedure the law requires. We keep, for as long as a claim could be brought, a record of the removal itself (who asked, when, which category, who decided and on what ground) and a technical fingerprint of the image, which cannot be turned back into a photo and exists so the same file cannot be uploaded again while the removal stands. Our backups and our storage provider's own recovery windows hold the file a little longer: at most 14 weeks in a backup copy, and 7 days in the point-in-time and deleted-object recovery windows. Those copies are put beyond use: nobody searches them, and nothing is taken out of one to find or reinstate a particular person's data. After a serious failure we may put part of the database back from within that recovery window, and anything that returns which should already have gone is removed again. Otherwise the copies roll over on their own schedule.

And the folder of originals: where the hosts keep the photographer's full-quality files, they keep them in a folder of originals we host for the event on our own Google Drive, but the hosts hand a link to it only to a guest they have switched that access on for, one guest at a time and off until they do; it never goes to every guest with full access to the album, and it never goes to a guest signed in with a shared code or a guest the hosts let in by name. Removing a photo from the gallery does not empty that folder, so after every removal we look there for the same picture. Where Google allows it we move a certain match to the Drive trash ourselves, and it stays recoverable there for 30 days; where it does not, we move the file out of the folder into a separate "Removed" folder beside it, so it is out of every guest's reach. What we cannot do is destroy the file: whoever uploaded it owns it, and Google lets only the owner delete it, so emptying that folder for good is the hosts' own act rather than ours. The same limit holds at the end: when the event's data is deleted, on whichever date that falls, we delete the event, its photographs and everything of ours that points at that folder, but the folder of originals is not deleted with the event, and the letters we send the hosts about that deletion say so.

Payments (where offered)

Payments are processed by a third-party provider; we do not store full card details.
Prices are shown at checkout including taxes where applicable; we issue receipts/invoices as required under Israeli law.
Before any payment is made, we display the disclosures required for distance selling under Section 14C of the Israeli Consumer Protection Law, 5741-1981: the seller’s name and address, the essential characteristics of the service, the price and payment terms, and the right of cancellation.

Cancellation

You can cancel a distance transaction under Section 14C of the Israeli Consumer Protection Law, 5741-1981, within 14 days.
On cancellation, you pay only for what has actually been used by then (messages sent, other than undelivered ones; an album already ordered), and we refund the rest.
A cancellation fee, where one applies, never exceeds the statutory cap: 5% of the price or ₪100, whichever is lower.
An album order is sent to the print partner at the moment it is placed: nothing is held back, and there is no window in which it can be recalled.
From that moment, a personalised photo book is goods made specially for you and is excluded from cancellation under regulation 6(2) of the Consumer Protection (Cancellation of a Transaction) Regulations, 5771-2010 (goods made specially for the consumer to their measurements or special requirements).
Where the law grants an extended cancellation period (up to four months for a person with a disability, a senior citizen or a new immigrant, where the transaction was preceded by a conversation), that period applies instead.

Gifts to the hosts

An event site may show you ways to give the hosts a gift: a link to a payment app such as Bit or PayBox, bank account details, or a gift list. Those details are the hosts’ own, and the event’s organiser puts them there. A gift is not a payment to us, and the Payments section above does not apply to it.

We do not accept, hold or transfer money given as a gift. A gift goes from you straight to the hosts, and we are not a party to it.
The payment itself is a service of the provider you send it through (the payment app, your bank or your card issuer), under that provider’s own terms. We do not see it.
A refund, a gift sent to the wrong account, or any other question about a gift is for you and the hosts to settle, with the provider that carried it. We cannot return a gift or stop a transfer already made.
As an organiser, you make sure the details shown belong to the hosts and are correct. A gift you note in the organiser panel is your own record of it and moves no money.

Marketing materials and plans

The pages of inviteberry.com that describe the platform, its features and its plans are there to inform you. They are not an offer to contract, and nothing on them by itself binds you or us. An agreement for a paid service is made only when you place an order, on the terms and for the plan shown to you at that moment. Payments are not currently offered, so for now no such agreement can be made.

The screens, invitations, messages and other pictures on those pages are illustrations. Your event site and your messages may look different from them in their design: fonts, layout, colours and the order of elements. A picture or a description never changes what a plan includes.
Every feature listed in the plan you buy, as the plan stood at the moment of purchase, is provided for the whole period you paid for, within the limits that plan states, such as a number of messages, and the usage limits described under “AI-assisted features”. For the features of a paid plan, this promise takes precedence over the “as is” wording and the right to change or withdraw the service in “Availability & liability” and “AI-assisted features”. A promise that a feature is provided is not a promise about its outcome: whether a message is delivered is described under “Messages to guests”.
The promise does not cover access suspended under these Terms, or a feature that a law, a court or a regulator stops us providing. If we can no longer provide a listed feature for a reason that is not yours, we refund the unused part of the period, as “Organiser accounts: suspension and termination” describes.

Availability & liability

The site is provided “as is” without warranties and may change or be discontinued (it is a single, time-limited event platform). To the extent permitted by law, we are not liable for indirect or consequential losses. Nothing in these Terms limits or excludes our liability for wilful misconduct, for gross negligence, for breach of your mandatory consumer rights, or for breach of our obligations regarding personal data to the extent the law does not allow that liability to be limited, nor any other liability that cannot be limited by law. For the features of a paid plan, “Marketing materials and plans” above takes precedence over this paragraph.

Organiser accounts: suspension and termination

This section is about an organiser account: the sign-in to the panel where an event is run. It is separate from the gallery access a guest holds, which is covered above.

We may suspend access to a single event, or to the account as a whole, where:

these Terms or our Data Processing Addendum are breached, including the confirmations you give us about your guest list;
unlawful material, or material somebody else holds the rights to, is uploaded to an event you run, or an event is used for something other than the event it describes;
a guest’s request to remove a photograph of themselves, or an instruction from us or from an authority, is left unanswered past its deadline;
the account or its credentials appear to be compromised, or sign-in details have been shared with somebody else;
a payment for the service is not made when it falls due;
a law, a court or a regulator requires it.

How it happens. Where we can, we tell you first and give you a chance to put it right. Where the reason is unlawful material, a credible risk to somebody’s safety or privacy, or a legal requirement, we may suspend access immediately and tell you straight afterwards. Either way you are told which access was closed, on which of the grounds above, and how to contest it.

What happens to the event. Suspending an organiser’s access does not delete the event or the data in it: that is kept to the ordinary retention schedule described in our Privacy Policy, although the guest site and the gallery may be closed while the suspension lasts. You can ask us to export your event data for as long as it is still kept. If a suspension becomes permanent, the event is archived and deleted as described in the next paragraph, and since the panel is then closed to you, we export the event for you on request until the day it is deleted.

Archiving and deleting an event. An event is not destroyed at the moment somebody decides to delete it, whether that is your request, approved by us, or our own decision under these Terms: it is archived first. From the day it is archived the guest site and the gallery are closed, so guests can no longer open the invitation, answer an RSVP, sign in to the gallery or open a photo link, although anyone can still ask for a photograph to be removed and a guest can still unsubscribe from messages. You keep access to the organiser panel, so you can export the event and download its photographs. Six months after the day it was archived, the event, its photographs, its guest data and the guests' gallery accounts are deleted, unless it has been taken out of the archive before then; to take it out, write to us at [email protected] before that date. Every admin of the event is emailed a month before the deletion, again three days before, and once afterwards. The 24-month limit in our Privacy Policy still applies, and whichever of the two dates comes first is the one that counts. If you want the event deleted sooner, write to [email protected] and we will delete it without waiting. What deletion removes and what it keeps is the same on either date, and our Privacy Policy names both; the folder of originals described above is not deleted with the event.

Money. Where payments apply and access is suspended or ended because these Terms were breached, fees already paid for the current period are not refunded. Where we suspend or end the service for our own reasons, and not because of anything you did, we refund the unused part of the period you paid for. This does not affect your mandatory rights under the Israeli Consumer Protection Law, 5741-1981, or the cancellation rules above.

Contesting a decision, and closing your account. Write to [email protected]: a person reads it and replies, and we will lift a suspension we got wrong. You can also close your own organiser account at any time by asking us. Closing it does not delete an event another admin still runs; an event you ask us to delete with it is archived and deleted as described above, and the retention limits in our Privacy Policy apply to every event in the same way.

Governing law

These Terms are governed by the laws of the State of Israel, with Israeli courts having jurisdiction, without prejudice to mandatory consumer-protection rights in your country of residence.

Roles and responsibilities

Which of us is responsible for personal data depends on what is being done with it. Our Privacy Policy sets out the division in plain terms ("Who is responsible for what"), and our Data Processing Addendum (/legal/dpa) sets it out in full.

Where we act on your instructions. For the guest contacts you give us as an event host (by single entry, file import, or WhatsApp) and the event messages we send from them, you are responsible for the data and we process it for you.

You undertake to give us only the details of guests you may lawfully share with us and who, as far as you know, have agreed to receive messages about this event.
You will notify us in writing without delay of any change, a guest’s opt-out or withdrawal of consent, a wrong or changed number, or a guest to remove.
You will not edit the message text so that it becomes advertising material (דבר פרסומת) under Section 30A of the Communications Law (no promotions, sponsor logos, discounts, or commercial links); messages must remain personal event invitations.
Every message we send on your behalf, other than the service messages named in our Privacy Policy (https://inviteberry.com/legal/privacy#service-messages), identifies the event/sender and offers guests a way to opt out of further messages; we honour opt-outs immediately and inform you of them. Those service messages are sent whatever a guest has chosen.
Contacts are used only for this event and are not reused for other marketing. If you organise events in the course of a business (see below), you indemnify us for claims arising from breach of these undertakings (including statutory spam-law and privacy claims); a host organising their own event privately gives no such indemnity.
Any terms of your own that you show on your event site carry the same notice about Google Maps and the same link to Google’s terms (https://maps.google.com/help/terms_maps/) that ours does.

Attendance counted at the reception desk

If your event uses the reception desk, the people meeting your guests mark them in at the door, which gives a count of how many of each invitation came. It is a count taken during the event by whoever holds the link, not a record you made. Wherever you have not recorded attendance for a guest yourself, an event can use that door count as the attendance: in the statistics, in the finances (including what a gift is compared against), in the event report and in the thank-you lists, where it is marked as the door's count. For a new event this is on from the start; for an event created before the setting existed it is off until you switch it on. You can switch it on or off at any time, in the project settings or in the reception link dialog. Nothing is written into your records either way, and attendance you record yourself always takes precedence. Check these numbers before you rely on them, for example before settling a bill with the venue or sending thank-you messages.

Messages to guests

Invitations and other messages to guests go out through WhatsApp (Meta) and SMS (ActiveTrail, Israeli numbers only). These providers are the ones that deliver them, and we do not guarantee that every message arrives: a number may not exist, may not be on WhatsApp, or the provider may not deliver a message under its own rules.

A message the provider reports as undelivered is not charged against the event’s package, and neither is a number our check rejects before sending. So resending to a corrected number costs you nothing.
Where reserve SMS is included in your plan and turned on, a WhatsApp message the provider has not delivered within an hour automatically goes out as SMS to the guest’s Israeli number. That SMS is charged against the event’s SMS package. Guests with numbers outside Israel do not receive a reserve SMS.
The carrier tells us about an undelivered SMS only at the moment it is sent, so an SMS the carrier has accepted counts as sent.

Passing a guest’s accessible-drop-off flag to the venue running the event is your responsibility as organiser, not ours: only to that venue, only for this event, and only so it can prepare access. We keep the flag if it has been set, but we do not send it anywhere ourselves.

Where we act in our own right. Security, screening, decisions on requests to remove a photograph, the outside limits on retention, and the platform features described in our Privacy Policy are ours to decide. An instruction from you cannot require us to keep a photograph up, to skip screening, to extend retention beyond our limits, or to disregard a request from a person who appears in a photograph. If an instruction would breach data-protection law, we will tell you and will not carry it out.

If you are organising events professionally, as a planner, photographer, venue, agency or any other business, additional terms apply to you and our Data Processing Addendum forms part of your agreement with us. You tell us this when you first sign in as an organiser, and you must keep that answer accurate.

The event address is permanent. Each event has one public address, chosen when the event is created, and it cannot be changed afterwards: it is printed on invitations, it is carried inside every personal link and gallery sign-in already sent, and it is the folder the event’s photographs are stored in. Whoever creates the event confirms the address at that moment, and each organiser given access to it confirms, at their first sign-in, that they may act for that event’s organisers and that the address is agreed with them. We keep a record of both confirmations. A different address means a new event, set up from the beginning.

How content is moderated

Uploads to event galleries are screened automatically: images and videos pass Google’s automated content screening, images are also compared against a fingerprint list of previously removed material, and invitation-site text is checked by an automated classifier. Automated screening hides content; before anything is treated as a violation a person reviews it, except for fingerprint matches of already-removed material, re-saved or resized copies included, which are refused or removed automatically. A photo or video hidden this way stays hidden only while it waits for that review, and a person reviews it within 7 days of it being hidden. Organisers additionally review guest uploads where that review is enabled, and anyone, with or without an account, can report content at /legal/report. When a photo is removed, whether on somebody’s request or for breaking a rule, the uploader is told what was removed, on which ground (law, or these Terms), whether the decision was automated, and how to contest it, wherever telling them would not expose the person who asked; repeated infringement closes the uploader’s access. When a person’s gallery access or uploads are closed because a named rule was broken or the law requires it, they are told on which ground (law, or these Terms), that a person decided it, and how to contest it, and that statement never exposes anyone who asked for it either. When the hosts close them for reasons of their own, that is the hosts’ own decision, which is not a finding of a breach, and the person is told so only where the hosts choose to; otherwise a closed gallery says only that access is closed. Anyone can contest a decision about their photos or their gallery access by writing to [email protected], where a person reads it and replies; doing so does not stop you going to court, or to an out-of-court dispute settlement body where one is open to you.

AI-assisted features

Some features offered to event organisers are performed by a machine-learning model running on our account: translating the invitation site’s text between its languages, suggesting spellings of guest names in English, Russian and Hebrew, and reading an uploaded floor plan to propose a room and table layout. Each of these is enabled per event by us, can be withdrawn per event, and carries a fair-use limit: a capped number of runs within a time window and per day. When a limit is reached the feature pauses and tells you when it will be available again; the limits protect the shared service and are not a fault. Text you submit to an AI feature is passed to Google Cloud (Vertex AI), the processor named for this in the subprocessor list in our Privacy Policy, to produce the result, and the same content rules apply to it as to anything else you write here: source text is screened before it reaches the model, and a refusal to process it is not a malfunction. The gallery’s "find photos of me" search is a separate matter: it is governed by the Biometric Information Policy and runs only with the guest’s own consent.

A model’s output is a draft, not a fact. It can be wrong in ways that look right: a mistranslated name, a shifted date or address, a phrase whose meaning or tone does not survive translation. Wherever the site inserts AI-written text it marks that text for your review, and nothing AI-written reaches your guests until you have saved it yourself. By using an AI feature you confirm that you understand this, and you accept that checking every AI-written text before publishing or otherwise relying on it is your responsibility alone. Once you have reviewed and published it, it is your content in the full sense of the "Your content" section, exactly as if you had typed it yourself: you, not the model and not we, answer for it to your guests and to anyone it concerns.

Use the AI features only for their stated purpose and only for your own event’s content; they are not a general-purpose translation or text-generation service.
Do not submit text that these Terms would not let you publish, and do not use the features to produce such text.
Do not attempt to get around the per-event limits, to automate calls to the features, or to extract the underlying model or its instructions.

AI features are provided "as is" and may be changed, suspended or withdrawn at any time. To the extent permitted by law, we are not liable for the content a model produces or for the consequences of your publishing or relying on it without the review described above; our responsibility is limited to operating the feature as described here. The same exceptions apply here as in "Availability & liability": nothing in this section limits or excludes our liability for wilful misconduct, for gross negligence, for breach of your mandatory consumer rights, or for breach of our obligations regarding personal data to the extent the law does not allow that liability to be limited, nor any other liability that cannot be limited by law.

Maps and directions

Event pages include Google Maps features and content: the map of the venue and the link that opens it in Google Maps. Those are Google’s, not ours, and your use of them is subject to the then-current Google Maps/Google Earth Additional Terms of Service at https://maps.google.com/help/terms_maps/, which include the Google Privacy Policy at https://policies.google.com/privacy. We do not control what the map shows or what Google collects while it is displayed; the address itself is the one the event organiser entered.

Contact point

The single point of contact for users and for authorities and regulators alike is [email protected]. It is read by a person and replies are not purely automated. You can write in English, Hebrew or Russian. Letters go to P.O. Box 7918, Ramat Gan 5217802, Israel.

Questions: [email protected]