ovbq Terms of Service

1. Who we are

ovbq is a service run by Othex Corp, a corporation formed in Florida ("Othex", "we", "us"). Our mailing address of record is 5645 Coral Ridge Drive STE 137, Coral Springs, FL 33076, United States. In these terms, "ovbq" and "the service" mean the website at ovbq.com, the short links and QR codes it produces, the dashboard, and anything else we offer under the ovbq name.

Back to contents

2. Agreeing to these terms, and who may use ovbq

By making an account, requesting a sign-in link, creating a code, or paying for a plan, you agree to these terms and to our Privacy Policy. If you use ovbq for a business or another organization, you agree on its behalf and confirm you are allowed to do that.

You may use ovbq only if:

• you are at least 18 years old, and also old enough to make a binding contract where you live if that age is higher; and
• you are using it for your business, work, project or organization, or for your own lawful purposes.

In these terms, "business use" means using ovbq for a business, trade, profession or organization (paid or not), rather than only for your own personal or household purposes.

To make an account, sign in or use the dashboard, you must be at least 18 and old enough to make a binding contract where you live if that age is higher.

No one under 13 may make an account, sign in or use the dashboard. Anyone may scan an ovbq code; scanning needs no account. If we confirm that an account holder is below the age required in this section, we will close the account. We give the notice and export opportunity described in section 17 unless child-protection law requires earlier action. For an account held by someone under 13, we act promptly to close it and delete its personal data, except records we must keep by law. Other retained records and backups follow section 8 of our Privacy Policy.

Back to contents

3. Your account and sign-in

You do not use a password to sign in to ovbq. To sign in, you enter your email address and we email you a link. The link works once and expires after 15 minutes. Whoever controls your email inbox can sign in to your ovbq account, so keep that inbox secure. Tell us at once if you think someone else has used your account.

You are responsible for what happens under your account, including codes made by anyone you let sign in. Use a real email address that you check, because that is where we send billing notices, warnings about your codes, and other important messages.

To limit abuse, we cap how many sign-in links one address or one network address can request in an hour.

Shared account access. Where Team is available, the account that owns the codes is the workspace. The owner chooses existing codes to share, invites each person to sign in with their own account, and chooses Viewer or Editor. You must be allowed to act for the owner when using shared access. An invitation is a private, one-time link for the invited email address; the owner sends it, not ovbq. Accepting it does not transfer either account, its billing or its content. All members must meet section 2's account-age rules. Keep your own sign-in and the invitation link secure.

Back to contents

4. What the service does

The codes you make in your account are editable codes (also called dynamic). An editable code is a QR code that encodes a short link on ovbq.com, for example ovbq.com/BCD234. When someone scans it, we send them on to the destination you set. You can change, pause or resume that destination from your dashboard. The QR image itself never changes, so you can print it once and keep using it.

A few rules are built in:

• Destinations must start with http:// or https://. Other kinds of links are refused. On Pro and Business a code can instead start a phone call, a text message or an email to the number or address you type, or open a page we host with what you type: a text page, a Wi-Fi info page, a contact card page, an app download page (whose store links must be on apps.apple.com and play.google.com), a menu page, a link-in-bio page, a coupon page, a form page, or a file you upload (a PDF, JPEG or PNG). Each counts toward the same code limit. A PDF, JPEG or PNG file can be up to 10 MB. Pro includes 200 MB of storage for the files you host and Business includes 1 GB. Free does not include hosted files. Every hosted file counts at the size we store it, including a file attached to a menu page. Independent redrawn-logo copies kept by saved looks also count toward file storage. If you replace a file, the old one is deleted. What you put on a hosted page or file is your content (section 5) and follows section 6. You choose what a code opens when you make it: what it opens can change any time, but a link code stays a link code.
• Destinations may not point at private or local network addresses, at ovbq.com itself, or include a username and password.
• Short codes are six characters long and are matched without regard to case.
• When you delete a code, its short link is retired for good. It will never be given to anyone else and will never point anywhere again. Deleting is permanent, so download your QR image and your settings first if you want them.
• Each plan has a limit on how many codes you can have. Paused codes count toward that limit; deleted codes do not.

We also offer a free generator of fixed codes that needs no account. A fixed code encodes your content directly and does not go through our short link, so we cannot change it, track it, pause it or turn it off after you download it. Section 5 of the Privacy Policy explains that we keep nothing you type into it, except when you choose "Make it editable": then we keep the web address and the error-correction level only while you sign in, so we can make the editable code for you.

Labels and filters. Labels help you organize your codes. They are private to your account and do not give another person access. Removing a label removes it from the codes using it; it does not delete those codes, change their links or change what they open. Search and filters change which codes the list shows, not their destinations or restrictions.

Dates you choose. On a plan that includes start and end dates, you can choose when a code opens its destination, in the time zone shown in the editor. The start time is included; an exact end time is not. If you enter an end date without a time, that whole local day is included. Leaving either boundary empty leaves that boundary unrestricted. A local time that is skipped or repeated when clocks change must be replaced with an unambiguous time. Before the start and from the end onward, the link shows the notice described in section 13. A coupon's offer dates are separate from its code's opening dates.

Passwords on codes. On a plan that includes it, you can protect a code with a shared password. Anyone who opens the code's short link is asked for the password first. You can replace or remove the password, but we cannot show it to you again; if you forget it, set a new one. A password is not encryption. It does not stop someone from sharing the password, the address of an unprotected destination or a downloaded copy. Entering it opens only what the visitor asked for at that moment; opening protected content again, or downloading a separate file or contact card, asks for the password again. We do not remember the unlock or sign anyone in to an account.

Rules for website links. On Business, a website-link code can send people to different destinations depending on their device, browser language or the time of day, in the time zone you choose. All conditions in a rule must match. The first rule that matches is used; if none matches, the main destination is used. Browser hints can be missing or wrong, so rules do not verify who someone is or where they are. If your plan or the feature becomes unavailable, your saved rules stay in your account, the main destination is used, and any dates or password you set still apply.

Event invitations and pages. A fixed event invitation holds the event details in the QR code itself and follows the fixed-code rules above. On a plan that includes it, an editable event code opens a page we host with your event title, description, dates, times, place and links, and offers a calendar file (.ics). An event's dates describe the event, not the code's access window: the event ending does not by itself switch off its page. Any saved pause, code dates or password still applies. A calendar download is a separate request and asks for the code's password again if one is set. A downloaded calendar entry is a separate copy; changing or deleting the event here does not update or recall it. The feature provides no invitation-sending, RSVP or attendee-list tool.

Payment links. A payment-link code opens the HTTPS payment page you choose at another service. You are responsible for the link, the recipient details and what you offer. We do not verify the recipient, take or process that payment, or receive its status. The payer deals with the recipient and payment service under their terms; questions about the payment, purchase or refund go to them. A provider name shown with a link does not verify the recipient or imply an endorsement. This is separate from Stripe billing for your ovbq plan. Saved pauses, code dates and passwords still apply.

Contact-card photos. You can add a photo to a hosted contact card on a plan that includes it. Use a photo you have the right and permission to publish. We keep a resized copy redrawn from its pixels, without the uploaded file's camera or location metadata. The stored copy counts toward your file storage. A password-protected card shows initials instead of loading the photo; the photo is not included in its downloadable contact file. Removing or replacing the photo cannot take back a copy someone already kept. File-removal and legal-hold rules still apply.

Saved looks. You can save a named copy of a code's appearance and apply it to another code when your plan allows. A saved look has its own copy of any uploaded logo, and each saved logo copy counts toward your file storage. Applying a look changes the code's appearance settings, not its destination, content or access restrictions. It does not change copies already printed. Deleting the source code does not delete the saved look, and deleting a saved look does not remove appearances or logos already copied to codes. Retained looks can be renamed or deleted after a downgrade.

JPG downloads. Where offered, JPG is another image format for your code. It has no transparency, and its compression loses some image detail. Check a downloaded or printed copy before relying on it; the format does not guarantee that every device will scan it.

Round appearance. The round option makes the area around the square QR grid round, while preserving the grid and its clear border. It changes the image you download, not copies you already printed or the link or content they encode. Test the finished print; a round appearance is not a guarantee of scanner compatibility.

Weekly scan email. You can choose a weekly summary at your account email address. You receive it only if you turn it on. The summary covers recorded scans for the previous Monday through Sunday in New York time, for codes whose statistics your current plan can show. Recording limits still apply; a scan is not a person or a payment. We aim to send it on Monday mornings. You can turn off this summary in your account or through its unsubscribe link. That choice does not stop sign-in, billing, security or legal messages. Turning it off stops new sending attempts. A summary whose sending attempt has already started may still arrive.

Picture galleries. On a plan that includes galleries, a code can open a page we host with a title, intro, optional back link and ordered photos with descriptions and captions. Use images you have the right and permission to publish. We keep a display image and a smaller thumbnail for each photo, redrawn from its pixels without the uploaded file's camera or location metadata. We do not retain the original upload as part of the gallery. Both stored copies count toward your shared file storage, including copies temporarily kept for an unsaved draft. Replacing a photo can require room for both the old and new copies before you save. A failed save does not replace the gallery already saved. A lower photo-count limit does not delete existing photos, but can restrict new uploads.

Gallery pages and their images follow the code's pause, dates, password and report restrictions. Images included in a response that passed a password check can be shown in that response; a separate protected image view asks for the password again. We do not remember an unlock. Removing or replacing a photo cannot recall a copy someone already kept. As a limited exception to the editing restriction in section 13, a gallery that loses its plan entitlement or new-gallery availability can still have photos removed, without adding, replacing or editing the others, while at least one photo remains. To remove the last photo, delete the code. A report hold can prevent those changes; the existing file-preservation rules still apply.

Video and audio pages. On Pro and Business, a code can open a page we host with buttons opening supported recordings on YouTube, Vimeo or SoundCloud. When the editor offers video or audio uploads, you can add a recording, either on its own or with outside links. Free does not include these pages. An ordinary website-link code can still point to an outside recording under its usual rules.

Where the editor offers uploads, an uploaded video must be an MP4 with H.264 video and, if it has sound, supported AAC audio, prepared for web playback. Uploaded audio must be supported MP3. The editor lists the format requirements; we do not convert recordings for you. On Pro, each video can be up to 32 MB and 2 minutes, and each audio recording up to 16 MB and 10 minutes. On Business, each video can be up to 64 MB and 5 minutes, and each audio recording up to 32 MB and 20 minutes. Both size and length limits apply. Recordings, captions, transcripts and poster images use your account's existing file storage. A replacement can require room for both the old and new files before it is saved. A recording rejected during checking does not replace the saved recording.

We do not remove details stored inside video or audio files. They can include names, artwork or location details that someone receiving the file may be able to read. Remove private information you do not want to share before uploading. Provide accurate captions for speech and important sounds in uploaded video, unless it has no speech or important sounds. Every video or audio page, including a page with only an outside recording link, needs a readable transcript and description of the recording, including important sounds and significant visual information. A transcript does not replace captions or needed spoken descriptions in video. We do not generate these for you. A poster image does not replace the needed captions, transcript or descriptions. Playback depends on the visitor's browser and device.

The page, recording and supporting files follow the code's account, safety, pause, date and password checks. Opening the page does not grant later unrestricted file access or a remembered unlock. For a password-protected recording, a separate download asks for the password again. In-page playback through that protected action requires the whole recording to download first; without JavaScript, the action downloads it for local playback. A password is not encryption and cannot recall a copy someone already saved.

Outside buttons show the service's actual host and open that service, rather than embedding its player. We do not automatically fetch its recording, preview or artwork. That service controls its own access, playback and privacy practices. Your ovbq page's restrictions do not protect the recording there. Changing or deleting content here does not update or remove outside recordings or copies kept by visitors. Hosted-content deletion and preservation follow sections 7 and 8 and our Privacy Policy; plan changes follow section 13.

Business pages. On a plan that includes it, a code can open a page we host with your public business name, about text, physical address or online-service description, contact details, links and optional weekly opening hours and time zone. Your private code name is separate from the public business name. You are responsible for keeping the information and links accurate. Open or closed status is calculated from the hours and time zone you supply, not verified by us; missing hours do not mean the business is closed. Changing the time zone reinterprets the same clock times in that zone rather than converting them. A Book action opens the booking service you choose; ovbq does not take or confirm bookings. Contact and other actions open the number, address or link you supply. Code access restrictions still apply.

Page languages. Where offered, you can choose a language for a hosted page's supplied labels and messages. That choice does not translate or verify the content you write, or change the dashboard's language. We offer only reviewed choices for that page type. If a saved choice is unavailable, system labels and messages fall back to English and the page explains the fallback; your saved choice is kept. Some notices and the Terms and Privacy Policy remain in English and are identified as such. A language choice does not weaken the code's access restrictions or the rules for forms.

Product barcode links. The free fixed-code maker can encode a supported GTIN-based GS1 Digital Link URI directly in a code. This is a limited URI format, not an ovbq editable short link or a product-hosting or resolver service. You must have the right to use the identifier and be responsible for the product information and destination. Validation checks the supported syntax and check digit; it does not verify identifier ownership, product authenticity, retailer acceptance or that a destination works. We do not issue GTINs or claim GS1 approval. The URI, including any supported batch, serial or variant values, is readable from the printed code. Check the displayed URI and identifier before printing. Once printed, that fixed payload cannot be changed through ovbq; the fixed-code rules above apply.

Team permissions. A member can read the selected code's private name and content, download its available source files and QR images, and export that code's list entry. This is private access authorized by the owner, separate from a visitor's password, dates or paused notice. Sharing a Wi-Fi page can disclose its network password; sharing a file or gallery can disclose the file or images. An Editor can also change supported code names and content, but cannot create or delete the owner's codes, edit forms or their answer settings, manage uploads, change page language, layout, theme, colors, access controls, artwork settings or labels, or administer the owner's account, members, billing or credentials. The owner separately permits scan-count access, answer viewing and answer CSV export; all start off, and answer export also requires answer viewing. Members cannot delete answers. A viewer can still copy what they can read even without a CSV export grant.

Pending unexpired invitations and accepted members each use a seat; the owner does not. If the account exceeds its allowance, every member's access stops until the owner resolves it. Feature or plan loss also stops member access without taking away the owner's existing account and export rights. The owner can remove invitations or memberships even when new Team access is unavailable. Removal stops new authorized access but does not delete the owner's content or the member's own account. A response or file stream already authorized may finish, and copies already obtained cannot be recalled. Team access does not transfer account ownership.

Bulk CSV creation. Where offered, you can check a UTF-8 CSV against the supplied template, review its stored preview and errors, and explicitly confirm creation. Supported fixed rows encode their content directly; supported editable rows use your account's existing validation, features and code allowance. File uploads, galleries and form management use their dedicated editors. The batch creates new codes; it does not update existing codes. Repeated source rows are separate creations. No code is created by checking the file. Confirmation commits the complete valid batch together or creates none.

Review the recorded result before retrying after an interruption. Repeating confirmation of the same completed, unexpired receipt returns its recorded result; a new upload, new receipt or expired receipt has no duplicate-free promise. Previews are available for 1 hour from checking and results for 1 day from successful creation, unless you remove them or the account closes or is deleted sooner. Result CSV and PNG/SVG ZIP files are generated when requested. Removing or expiring the batch does not delete codes it created. Saved result references can outlive a deleted code until batch expiry, but cannot produce a new QR image for that deleted code. The CSV content and any encoded personal or private information remain your responsibility under sections 5 and 6.

Owner API access. Where offered, the account owner can create a key with separate code-read, code-write, code-delete and scan-count scopes for the documented API. Authorized API use within those scopes is allowed; it does not permit scraping, resale, bypassing limits or another account's data. Read access can disclose private code names, destinations and hosted content, including a saved Wi-Fi password. Create and edit operations support the documented code types; uploads and form management keep their dedicated editors. A delete scope can permanently delete a code and its content under the existing deletion rules. The API supplies no answer bodies, individual scan records, visitor addresses or address hashes. Its scan endpoint gives recorded daily counts for the last 30 UTC days and the lifetime recorded total.

Keep keys in the authorized client and its authorization header, not in URLs, printed codes, public examples or logs. The full key is shown once; we keep a verifier, not a recoverable copy. Revoke and create another if it is lost or exposed. A key has no automatic expiry, but access still needs the feature, plan, scopes and an open owning account. Revocation stops new authorized requests after accepted work finishes. A feature or plan pause stops API use without revoking the key, so it can work again if access returns. Revoke it to end that access permanently. Revoking a key does not disable an independent webhook or feed. Creation retry protection applies only to the same key, unexpired request receipt and exact request body; the receipt lasts 24 hours. A different or expired receipt or a new key can create another code. Request limits, stale-version refusals and availability limits apply. No permanent API-version lifetime or continuous availability is promised. Existing owner exports under section 16 are not replaced by the API.

Webhook notifications. Where offered, the owner can save a public HTTPS destination and explicitly enable notifications about recorded scans. A new webhook starts turned off; a deliberate test can queue a synthetic event even while that webhook is turned off. If the queue is full, the test reports that nothing was queued. That test is not retried; request a new test after there is room. Messages contain an event identifier, type, UTC time, code and response references where applicable, and a test indicator. They contain no answer text, question text, code names or destinations, visitor addresses or hashes, individual scan details or account email. References and times can still be information about people. You are responsible for the destination, its authority to receive the selected information, and the notices and lawful use required for your workflow. Verify the signature and a recent timestamp, and recognize repeated event IDs before acting on a message. A successful HTTP acknowledgment does not prove that its workflow completed.

Delivery is best effort, with bounded retries and possible delays, duplicates, missing events or changed order. Notifications are queued after the source record is saved. A notification failure does not undo that record, and a failure or interruption between saving and queueing can omit its notification. Delivery is attempted during an hourly run, within a limit on rows and time. A failed notification may be retried at or after its scheduled time during an hourly run; a busy queue may need later runs. Check event identifiers for duplicates.

Repeated failures or a full queue can automatically turn off delivery with a notice in your account. Waiting notifications are paused and kept until their existing expiry under Privacy Policy section 8; choose Enable to resume those still available. When you choose Disable, waiting, paused or claimed work is canceled but settings and completed delivery history are kept; choosing Delete removes that configuration and its history. A request already authorized to send may still arrive. Source deletion cancels matching references; an expired source answer is not sent. Plan loss cancels work when checked for delivery. Turning off webhook availability sends nothing but can retain unexpired queued work, which may resume if availability returns. Removing a member or revoking an API key does not disable an owner's webhook. No replay tool, exactly-once or lossless delivery is promised. Keep the one-time signing secret safe; replace it by deleting the configuration and creating another. We retain the signing material in encrypted, recoverable form so we can sign messages.

Private scan-count feeds. Where offered, the owner can make a private CSV address for Google Sheets or another consumer. It returns the code key, private code name and recorded scan count for the last 30 UTC days for every current nondeleted, nonlapsed code in that account, including zero counts. It contains no form answers, individual scan records or visitor identifiers. This is a read-only feed, not an OAuth account connection, spreadsheet editor or guaranteed real-time sync. Giving the address to a service gives it the token and data needed for these reads; anyone with the address can read the feed while access remains available. The address is shown once, has no automatic expiry, and may appear in formulas, collaborators' copies, browser history and standard hosting access logs. Keep it private and revoke it if exposed. We store only a verifier for the token, not a recoverable copy. New reads check the token, owning account, feature, plan and request limit. A feature or plan pause does not revoke a retained token, so access can resume if availability returns. Revoke it to stop that access permanently. Revocation stops new authorized reads; a response already authorized may finish. Revoking a feed cannot erase data or formulas already kept elsewhere and does not revoke other access.

Artwork for Canva and other design tools. Where offered, the owner can use an additional PNG or SVG artwork download for manual upload to a design tool. We draw the export for your request; this feature does not connect a Canva account, upload a design or keep it synchronized. The chosen tool's terms, features and plan apply to your later use. Share only artwork and logos you have the right to use, and handle any information encoded in the QR image appropriately. The existing QR downloads in section 16 remain available under their existing rules when this additional download is unavailable.

For a form, the owner may also enable a reference-only notification that an answer was submitted. This follows the instructions and limits in section 26; it does not send the answer body or allow a recipient to retrieve it through this API.

Back to contents

5. Your content and the license you give us

You keep ownership of everything you put into ovbq: your code names, your destinations, and anything at those destinations. We claim no rights in it.

You give us a limited license to store, copy, display and transmit that content only as needed to run, secure, back up and improve the service, and to comply with the law. The license ends when the content is deleted from our systems, except for copies in backups until those are overwritten (within 30 days, as the Privacy Policy explains) and the retired short codes described in section 4. When you delete a code, its name and destination are blanked within 30 days; only the retired short code and its dates are kept, so it can never be reused.

You promise that you have the right to use every destination you set, and that scanning it will not break the law or anyone else's rights. This includes menus you write and files you upload: you promise you made them or have the right to share them with everyone who scans the code.

For video or audio pages, you must have the rights and permissions needed to share the recording and its music, images and voices, as well as the captions, transcript, poster and outside links you provide. Check for private information and keep your own original copies. Uploading or linking a recording does not mean we have verified those rights or permissions.

Back to contents

6. Acceptable use

You may not use ovbq to point a code at, host, send or promote:

• phishing, fake login pages, or anything meant to trick people into giving up passwords, money or personal details;
• malware, spyware, unwanted downloads, or pages that exploit a visitor's device;
• files built to harm or trick: a PDF or image that runs code, opens other files, collects information, or is meant to deceive;
• scams, fraud, pyramid schemes, counterfeit goods, or deceptive offers;
• content that is illegal where you are, where we are, or where the people scanning are;
• harassment, threats, hate, or content that sexualizes minors;
• photos or video of a person shared without their consent, including intimate images;
• menus that state prices, ingredients or allergen information you know are wrong;
• a coupon that is a gift card, gift certificate, prepaid card, balance or other stored value, or anything that is sold or paid for through a page we host;
• a coupon, discount, gift or other reward offered in exchange for a review or rating, or conditioned on what a review says;
• a coupon for an offer you will not honor as written, or that misstates its price, its dates or its conditions;
• a form that asks for passwords, PINs or sign-in codes, card numbers or card security codes, bank account or routing numbers, government ID numbers (such as Social Security, passport, driver's license or tax ID numbers), or wallet recovery phrases or keys;
• spam or bulk unsolicited messages, or codes placed on other people's property without permission;
• anything that pretends to be another person, business or government body;
• content that infringes copyright, trademark or another person's rights;
• tracking of people in a way the law forbids, or any attempt to identify, follow or profile the people who scan a code beyond the statistics we provide.

You also may not:

• interfere with the service, probe or overload it, or try to get around a limit, block or security measure;
• scrape, mirror or resell the service without our written permission;
• use ovbq to send people to a destination that then forwards them somewhere that would break these rules.

If a code breaks these rules, we may block it, pause it, point it at a warning page, remove it, or close the account, with or without telling you first. We also may do this when a destination is reported or flagged as unsafe by an automated check and we cannot confirm it is safe. Our promise about printed codes in section 13 never protects a code whose destination is abusive or unlawful.

Using the documented API as section 4 allows does not by itself breach the scraping restriction above. That permission stays within your scopes, resources and limits; it gives no general permission to mirror or resell the service.

Back to contents

7. Abuse reports and takedowns

Anyone can report a code from the "Report abuse" page, or by emailing abuse@ovbq.com. A report asks for the code or link, a reason, optional details, and an optional email address for a reply. We review reports and act on them as described in section 6.

If we disable your code because of a report, we will tell you by email where we can, and you may reply with an explanation. We decide in good faith but we do not have to restore a code we believe is harmful. Repeated or serious violations end your account. If a report is about a file we host, we may disable it while we look. Material showing the sexual abuse of children is removed, reported as the law requires, and not restored.

The same report and takedown rules cover video and audio pages and their recordings, captions, transcripts, posters and outside links. We may disable content or links we provide while reviewing a report. Disabling a link here does not remove the recording from the outside service or recall copies already downloaded. Copyright complaints follow section 8.

Back to contents

8. Copyright complaints (DMCA)

We respect copyright and expect you to do the same. If you believe a page or file we host, or a destination behind an ovbq code, infringes your copyright, send a notice to our designated agent with:

1. your physical or electronic signature;
2. the copyrighted work you say is infringed;
3. the ovbq short link (for example ovbq.com/BCD234) and the destination, hosted page or file you say infringes, with enough detail for us to find it;
4. your address, telephone number and email address;
5. a statement that you believe in good faith that the use is not authorized by the copyright owner, its agent or the law;
6. a statement, under penalty of perjury, that the notice is accurate and that you are the owner or authorized to act for the owner.

Designated agent: Copyright Agent, Othex Corp, 5645 Coral Ridge Drive, STE 137, Coral Springs, FL 33076, United States. Phone: 866-310-6011. Email: info@othexcorp.com.

When we receive a valid notice we may disable the code and tell the account holder. For a file or page we host, we disable it and keep it until the dispute is closed. The account holder may send a counter-notice to the same agent with their signature, the short link that was disabled, a statement under penalty of perjury that they believe in good faith the code was disabled by mistake or misidentification, their name, address and phone number, and a statement that they consent to the jurisdiction of the federal court for their address (or, outside the US, for Broward County, Florida) and will accept service from the person who sent the notice. If we get a valid counter-notice, we forward it to the complaining party and may restore the code in 10 to 14 business days unless we are told that a court action has been filed.

We close the accounts of repeat infringers. Knowingly false notices or counter-notices can make you liable for damages under US law.

Back to contents

9. Plans, prices and payment

ovbq has a Free plan and two paid plans. The paid plans can be billed monthly or yearly:

• Free: $0, 2 editable codes.
• Pro: $9 a month or $90 a year, 50 editable codes.
• Business: $29 a month or $290 a year, 500 editable codes.

Prices are in US dollars. The pricing page lists the features of each plan and is part of these terms. Features marked “Coming soon” are not included in any plan until we release them. We have not promised a release date or which plans will include them. A yearly plan is paid once a year, in advance, at the yearly price listed above.

Payments are handled by Stripe. When you choose a paid plan, we send you to a Stripe checkout page. Stripe collects your card details; we never see your full card number. You agree to Stripe's terms for the payment itself. We receive your plan, the status of your subscription, the renewal date, and Stripe's identifiers for your customer record and subscription. Promotion codes may be entered at checkout for monthly plans. Yearly checkout does not offer promotion codes. Each promotion code may be used once per customer, has no cash value, and expires as stated in the offer.

The Free plan counts up to 1,000 scans a month in its statistics. Scans beyond 1,000 still redirect; only counting stops, until the next month.

Back to contents

10. Automatic renewal, in plain words

Paid plans are subscriptions. They renew automatically, every month on a monthly plan or every year on a yearly plan, and your card is charged again, until you cancel. Here is exactly what that means:

• Billing period. A monthly plan renews every month on the day of the month you first paid (in a month without that day, such as the 31st in a 30-day month, on that month's last day). A yearly plan renews every year on the date you first paid for it (a plan started on February 29 renews on February 28 in a non-leap year). Each time, you are charged the price of your plan at that time. In these terms, a "billing period" is one of these months or years. If we raise the price, section 12 says how we tell you first.
• Before a yearly plan renews. At least 15 and not more than 45 days before a yearly plan renews, we email you that it will renew unless you cancel, how long it renews for, the amount, how to cancel, with a link, and how to reach us.
• How to cancel. Sign in, open Account, and choose Cancel plan, or choose Manage billing and Cancel. That is the whole process. You can do it online at any time, with no phone call and no need to talk to anyone. You can also email hello@ovbq.com from your account address and we will cancel for you; your plan then works until the end of the billing period you paid for, with no refund for the rest of it, as with any cancellation.
• When cancellation takes effect. At the end of the billing period you have already paid for. Your plan keeps working until then.
• Changing plans. You can switch between Pro and Business, and between monthly and yearly billing, under Manage billing. Moving from monthly to yearly takes effect at once, with a credit for the unused part of your current billing period, and starts a new yearly billing period that day. Moving from yearly to monthly billing takes effect at the end of the year you paid for, with no credit or refund. You can still cancel on your Account page while that change is scheduled. Other plan changes take effect at once. Moving to a higher price, you are charged right away, with a credit for unused time. Moving to a lower price, the unused difference is credited to your next charges, not refunded. If you then have more codes than the smaller plan has room for, they all keep working for 30 days, with the emails in section 13; after that, your oldest codes stay live, as many as the plan has room for, and the others are paused as section 13 describes.
• Knowing when the next charge is. Your Account page shows your plan, its price and the next renewal date at all times.
• Confirmation. After you subscribe, Stripe emails you a receipt, and your Account page shows your plan, price and renewal date. When you cancel, we email you a confirmation with the date your plan ends; if none arrives within a day, write to hello@ovbq.com. Keep these terms, which include the cancellation steps above, for your records.
• Failed payments. If a renewal charge fails, Stripe retries it and we email you. If payment keeps failing, your subscription ends and your account returns to Free, with the protections in section 13.

By starting a paid plan you consent to these recurring charges, monthly or yearly as you chose.

Back to contents

11. Canceling and refunds

You can cancel any time as described in section 10. Cancellation is effective at the end of the current billing period, and you keep your paid features until then.

When you cancel or delete your account, however you do it (online, by email, or under section 17), we do not refund unused time in a billing period. We will refund where the law requires it, and we may choose to refund in other cases, for example if we charged you by mistake.

If we end your paid plan for a reason other than your breach of these terms, fraud, a chargeback or a failed payment, we refund the unused part of the billing period you paid for, in proportion to the days left.

Back to contents

12. Price changes and taxes

We may change prices or plan limits. If a change raises the price of a plan you already pay for, we email you first, and you keep your current price for at least 90 days after the notice; the new price applies from your first renewal after that. If you do not agree, cancel before that renewal and you will not be charged the new price.

Prices do not include taxes. If we are required to collect sales tax, VAT or a similar tax on your plan, we add it at checkout or on your invoice, and you pay it.

Back to contents

13. Our promise about printed codes

This section is our promise about printed codes, with the limits set out below. We make it because printed codes are expensive to replace.

The promise. While ovbq runs, your printed codes never go to a dead page, an ad or our sales page. Every editable code you created keeps resolving to something useful. The exceptions below (such as abuse, fraud, a chargeback or a code you delete) and the access restrictions you set yourself (dates or a password), which are explained at the end of this section, and an outage or other event outside our control (sections 15 and 24), are the only ones, and if ovbq ever shuts down we give you 90 days' notice first (section 14).

If you stop paying. When a paid subscription ends, whether you canceled it or a payment failed for good:

1. For a grace period of 30 days from the day it ends, every code keeps working exactly as before. We email you when the grace period starts, and send reminders on about day 7 and day 25, each with a list of the codes that will pause. If a reminder is delayed (for example by an outage), we send the latest one that is due rather than every one missed. When the grace period ends, we email you the list of codes that paused, unless none of them is still paused by the time the email goes out. None of these emails is sent once you have asked us to delete your account.
2. After the grace period, your 2 oldest website-link codes (codes that open a web page) stay on the Free plan just as they were: live, or paused if you paused them yourself (a code you paused still takes one of the 2 places, and stays paused). Only website-link codes take these places, whatever their age: a code that starts a phone call, a text message or an email, or opens a page or file we host, needs Pro or Business, so it does not count toward the 2, even if it is older.
3. All your other codes are paused, including every code that starts a phone call, a text message or an email, or opens a page or file we host; what such a code opens is kept. A paused code shows a short notice headed "This code is paused". A form is the exception: its notice says "This form is not taking answers". If a form submission is refused because the form is paused, the heading says "Your answer was not sent." instead. A paused form's only button is the business's own saved link, if the business gave one and the code has no access restriction; it never continues to the form. A form without that eligible link has no continue button. For another code without an access restriction, the notice keeps its continue action. For a website link without saved rules, the button is labeled with the destination's domain and the notice shows the full destination address. A website link with saved rules shows a generic Continue button, then follows the available rules or the main destination. For a call, text message or email, the button is labeled with the number or address. For another page or file we host, it continues to that page or file. Continuing through the notice still checks any restriction you set before opening or revealing a protected destination or content. In particular, it cannot bypass a code's start or end. The notice carries a small text link to make your own QR code, left off on Business; it never redirects to our sales page. There is no advertisement or timed wait.
4. While a code is paused this way, until your plan has room for it again, you cannot edit, pause or resume it, view its statistics or download its scan CSV, and its scans are not recorded. You can still download its QR image as PNG, SVG or JPG, and you can delete it. You can also remove an existing date restriction; removing it may allow the code to open outside its previous dates. Other restrictions still apply. Nothing is deleted because the plan ended: your codes, destinations and statistics stay in your account. Form answers still follow their own keep time under sections 25 and 26; ending a paid plan does not reset or stop that clock. As for every code, scan records older than 24 months are removed on a rolling basis (section 8 of the Privacy Policy); a code's lifetime scan total and last-scan time are kept with the code.
5. If you subscribe again, a code paused this way comes back as soon as your plan has room for it, oldest codes first, with no further step. For example, with 60 codes on a plan that has room for 50, your 50 oldest work normally and the other 10 stay paused until you delete codes or choose a bigger plan; then they come back the same way. A code you paused yourself stays paused until you resume it.
6. Where we run safety checks on destinations, they continue for paused codes just as for live ones.

Exceptions. The promise does not apply, and we may point a code at a warning page, disable it, or retire it, when:

• the destination or the code breaks section 6, or we reasonably believe it is harmful, unlawful or being used to deceive;
• a court, regulator or law requires us to disable it;
• the account holder deletes the code or the account;
• the account was created by fraud, or a payment is disputed through a chargeback (see below);
• we close the account because these terms were broken (sections 2, 17 and 24), including by someone under 13 or on a sanctions list;
• the destination itself is gone, broken or hijacked. We are responsible for our short link, not for the page you chose to send people to.

Chargebacks. If you dispute a payment with your bank (a chargeback), we close the account at once, when the dispute is opened: sign-in stops and your codes stop opening their pages. To sort out a billing problem, write to hello@ovbq.com first; we answer within 2 business days. Every code of a closed account shows a neutral page that says the code is no longer active; there is no grace period, and the 2 oldest codes do not stay live. We keep a closed account as it is until you ask us to delete it. We then delete everything except the billing and dispute records, which we keep for 7 years (section 8 of the Privacy Policy). If the dispute is settled, write to us and we may reopen the account.

A code you pause yourself from the dashboard shows a paused notice until you resume it. That is your choice, not because a plan ended, and it does not freeze editing. Its continue path follows the same date and other restrictions as its ordinary link.

A form paused by you or by your plan takes no new answers and uses the form notice described above. Answers already stored stay until their time is up under section 26. You can still read, download and delete them on any plan while you can sign in, including while the form's code is paused and while new form answers are switched off. If your account is closed, write to privacy@ovbq.com to request the answers or their deletion.
Dates and passwords after a plan change. The dates and password you set do not disappear because your plan becomes smaller or ends, or because we turn off new creation of those settings. The short link and a paused notice's continue path still follow them. When your plan or the feature's availability prevents changes, the saved settings are shown read-only, but you can remove them deliberately. Removing dates may allow the code to open outside its previous window, and removing a password lets anyone who opens the code reach it; other restrictions still apply.

Saved rules stay in your account, but the main destination is used while rules are unavailable.

Outside the dates you chose. Before the start, the short link shows that the code is not active yet. From the end onward, it shows that the scheduled period has ended. The notice is generic unless you choose your own public message; you may also supply a separate contact or back link. There is no button that bypasses the date restriction to open the restricted destination. The short link is kept and is not reassigned. These are restrictions you choose, not an expiry imposed on an otherwise unrestricted code by ending your plan.

A code with a password. A code you protected asks for the password before it opens. The prompt page has no advertisement, no timed wait and no button that skips the password. It does not show the destination. If you remove the password, the code opens as before. The password is your restriction, not an expiry we impose when your plan ends.

If we break this promise. If a code stops working as this section promises, and none of the exceptions above applies, we will reimburse your documented costs of reprinting the materials that carry the affected codes, up to $250 in total per account. This remedy applies on top of the cap in section 19, and the exclusion of reprinting costs in section 19 does not apply to it. To claim, email hello@ovbq.com within 90 days after the code stopped working, with receipts and the short codes. We pay valid claims within 30 days after we receive them.

Back to contents

14. If ovbq ever shuts down

If we ever decide to stop running the service, we will email every account holder at least 90 days before the shutdown date. Through that whole notice period, every code keeps working and the link export in section 16 stays available, so you can move your codes and destinations to another service or your own domain. We will never sell or transfer your codes to another company without telling you first and giving you a chance to export them. If ovbq is taken over by a company that keeps running it, these terms continue to apply until that company changes them under section 22.

Back to contents

15. Service changes and availability

We may change, add or remove features, including the way the dashboard works and the look of the paused notice, as long as we keep the promise in section 13. We may limit or suspend the service for maintenance, security, or events outside our control.

We work to keep redirects online and fast, but we do not guarantee any level of uptime unless we say so in writing for your plan. Scans that happen while we are down are not redirected and are not counted.

Back to contents

16. Exporting your data

You can download your QR codes as PNG, SVG or JPG files at any time, on every plan including Free, and also while a code is paused under section 13.

You can download a CSV file of all your codes and their destinations from your dashboard at any time while your account is open, on every plan including Free, so you always hold the list you would need to move elsewhere. If we closed your account because of a payment dispute, email hello@ovbq.com from your account address and ask for the file. We check that the request comes from the account holder and send you the file as long as the account has not been deleted.
Destination fields are empty for hosted pages and files; the CSV does not include their content or their files.

Paid plans can also download the scan statistics of each code as a CSV file; that file never contains IP addresses or hashes.

You can download the answers to each of your forms as a CSV file on any plan while you can sign in, including after a paid plan ends, while the form's code is paused and while new form answers are switched off. If your account is closed, write to privacy@ovbq.com and we will send or delete the remaining answers. Cells that a spreadsheet could read as a formula start with an apostrophe in the file to prevent those cells from being treated as formulas.

Back to contents

17. Ending the agreement

You can stop using ovbq at any time, and delete your account yourself from your Account page. If you cancel or delete your account, we do not refund unused time in a billing period. If a paid plan is running, you choose: we cancel it at the end of the billing period you paid for, your plan keeps working until then, and the account is deleted when that period ends; or you delete at once and give up the rest of the period, with no refund. On a yearly plan, that can be most of a year, so we ask you to confirm. You can take the request back with Keep my account on your Account page, and it is dropped if the plan renews. We ask you to confirm first, because deleting an account retires all its codes permanently and removes your codes, scan statistics and account data. Billing records are kept for 7 years, as tax and accounting law requires (section 8 of the Privacy Policy).

You can also email hello@ovbq.com from your account address and we will delete the account for you within 30 days; if a paid plan is running, we cancel it at the end of the billing period you paid for and delete the account when that period ends, unless you ask us to delete it at once and give up the rest of the period. Either way, no unused days are refunded.

If you started a checkout, finish it or wait until it expires (about a day) before you delete the account, or email us at hello@ovbq.com. If our payment provider cannot be reached to check, try again a little later.

We can suspend or close your account if you break these terms or if the law requires it. Not paying for a plan does not close your account; it moves to Free as section 13 describes. If you dispute a payment with your bank (a chargeback), we close the account at once, when the dispute is opened: sign-in stops and your codes stop opening their pages. To sort out a billing problem, write to hello@ovbq.com first; we answer within 2 business days. After a closure for a payment dispute you can still ask for your code-list CSV by email (section 16). We never close an account just because it has been inactive. Where the reason is not abuse, fraud, a chargeback or a legal order, we give you 30 days' notice by email and a chance to export your data first.

Sections 5 and 8, section 11 for refunds already owed, the remedy at the end of section 13 for a problem that happened before the end, and sections 18 to 21 and 23 to 26 survive the end of this agreement. Section 26 continues for as long as we still hold form answers.

Ending a membership or deleting a member's own account removes that person's shared access; it does not delete another owner's workspace or records. Closing or deleting the owning account ends its shared access. An administrative reopening does not restore old memberships or invitations; they must be set up again.

Closing the owning account revokes its API keys and clears API code-creation retry receipts. Reopening does not restore old keys. Account deletion removes the API records under the Privacy Policy; existing closed-account content and export rules still apply.

Closing or deleting the owning account removes its webhook configurations, signing material and delivery records. Already authorized outgoing requests or recipient-held copies cannot be recalled. Reopening requires deliberate new setup.

Closing the owning account revokes its feed tokens; reopening does not restore them. Account deletion removes its feed records. This does not erase copies already received by another service.

Closing or deleting the owning account clears its retained batch previews and results. Codes already created follow the existing account/code rules, not the batch expiry.

Back to contents

18. Disclaimers

ovbq is provided "as is" and "as available". To the extent the law allows, we make no warranties of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, title and non-infringement. We do not promise that the service will be error-free, that scans will always be counted, that statistics will be exact (bots and privacy settings make them estimates), or that a destination you choose will stay online. Nothing in the service is legal, tax or security advice. Some places do not allow some of these disclaimers, so some may not apply to you.

Back to contents

19. Limitation of liability

To the extent the law allows:

• We are not liable to you for any indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost data, lost business, or the cost of reprinting materials (except under the remedy in section 13), even if we were told it might happen.
• Our total liability to you for everything arising out of these terms or the service is capped at the greater of (a) the fees you paid us in the 12 months before the event that gave rise to the claim, or (b) $100. The reprinting remedy in section 13 is paid in addition to this cap.

These limits do not apply to liability that cannot be limited by law, including liability for our fraud or gross negligence, or for death or personal injury caused by our negligence.

Back to contents

20. Indemnity

If your use of ovbq is business use (section 2), you agree to defend us and pay what we owe if a third party makes a claim against Othex Corp, its officers, employees or agents because of your content, your destinations, your breach of these terms, or your violation of the law or of someone else's rights. We will tell you about the claim promptly, let you run the defense with a lawyer we approve, and help you at your cost. You may not settle a claim in a way that admits fault for us or binds us without our written consent.

Back to contents

21. Governing law and where disputes are heard

The laws of the State of Florida govern these terms, without regard to its conflict-of-law rules.

Any dispute goes to the state courts in Broward County, Florida, or the United States District Court for the Southern District of Florida, and you and we agree to those courts' jurisdiction. Either side may instead bring a claim that qualifies in small-claims court where that party lives or does business, as long as it stays in small-claims court. Consumers may also have rights under the laws of the place they live that these terms cannot take away.

These terms contain no arbitration clause and no class-action waiver.

Back to contents

22. Changes to these terms

We may change these terms. If a change is material, we email every account holder at least 30 days before it takes effect, and we post the new effective date at the top. If you do not agree, cancel before that date; using the service after the date means you accept the change. Changes that the law requires, or that only add features or are otherwise in your favor, may take effect sooner. A change that weakens the promise in section 13 for codes that already exist always takes effect no sooner than 30 days after we email you about it.

Back to contents

23. Notices

We send notices to the email address on your account. Keep it current. A notice is treated as received when we send it, unless it bounces. You may send notices to us at hello@ovbq.com or legal@ovbq.com, or by mail to the address in section 27.

Back to contents

24. Other terms

• These terms, the pricing page and the Privacy Policy are the whole agreement between you and us about ovbq.
• You may not transfer your account or these terms to anyone else without our consent. We may transfer them to a company that takes over ovbq, subject to section 14.
• If a court finds any part of these terms unenforceable, the rest still applies.
• If we do not enforce a term at some point, we can still enforce it later.
• Neither side is liable for delays caused by events beyond its reasonable control.
• You may not use ovbq if you are on a US government sanctions list or in a country under comprehensive US sanctions.
• Nothing in these terms creates a partnership, agency or employment relationship between you and us.
• QR Code is a registered trademark of DENSO WAVE INCORPORATED. ovbq is not connected with DENSO WAVE.
• WhatsApp is a trademark of WhatsApp LLC. ovbq is not affiliated with, endorsed or sponsored by WhatsApp.
• ovbq uses open-source software and fonts under their own licenses, listed at ovbq.com/credits.

Back to contents

25. Forms, link pages and coupons

These rules cover the link-in-bio pages, coupon pages and forms you make on Pro or Business. What you put on them is your content (section 5) and follows section 6.

Link pages. A link-in-bio page shows links you choose. You are responsible for every link and every label on it, as if each link were a code's destination (section 6). A label may not hide where a link goes or say a link comes from someone it does not. If a link earns you money, a free product or another benefit, tell people as the law requires. If one link breaks section 6, we may act on the whole page as section 6 says.

Coupons. A coupon page shows an offer you make. The offer is yours, not ours. We are not a party to it. We do not sell, redeem, check or honor coupons, and we do not promise that anyone can use one. ovbq takes no payment for a coupon, and a coupon page may not be used to sell anything or to hold a balance. You must honor each coupon as it is written on the page, show its real dates and conditions, and follow the laws that apply to your offers, including those on advertising, prices, taxes and age-restricted goods. You may not offer a coupon or any other reward in exchange for a review or rating. Coupon pages are separate from the promotion codes at checkout in section 9, which are ours.

Forms.

1. Your form, your responsibility. You decide what your form asks and what you do with the answers. You are responsible for having the right to collect them, for telling the people who answer how you use their answers, for example in your own privacy policy, and for answering their requests to see, fix or delete them. The form page names your business, so people know who to ask.
2. What a form may not collect. Do not use a form to collect anything section 6 lists for forms. A form may not ask for health information, except dietary or accessibility needs that you ask about only so you can serve the person. Health information means information about a person's health, such as diagnoses, conditions, treatment, medication, insurance or patient details. ovbq is not built for medical or patient records. We are not a business associate under HIPAA and do not sign business associate agreements. If you aim a form at children under 13, or knowingly collect answers from a child under 13, you are breaking these terms.
3. Emails about answers. For each form you choose how we tell you about new answers: a daily summary of the previous day (UTC), with counts only, unless you choose otherwise; an email with the answers themselves; or no email. The daily summary is sent only when answers came that day. Several submissions close together may come in one email, at most one every 5 minutes. An email includes up to 5 submissions, with each response to a question cut at 500 characters. Web addresses containing a scheme followed by ://, or beginning with www., are broken in the email. Your mail app may still turn other text, such as bare domains or email addresses, into links. If you choose emails with answers, keep them as safe as the rest of your records and delete them when you no longer need them. Deleting an answer on our site does not delete an email already sent.
4. Our checks. We check a form's wording when it is saved, and again when answers are taken. We may refuse wording that asks for anything section 6 forbids for forms, or that reads like phishing; a form saved before a new check was added stops taking answers until you fix it. These checks are automatic and can be wrong in either direction. If one refuses wording you think is fine, reword it or write to hello@ovbq.com. Passing them does not mean we approve a form. If a form breaks these terms, we may disable it, delete it, or act under section 6.
5. Limits. Each form takes a limited number of answers a day, and we limit how often one network address can attempt to send a form, to keep spam out. Attempts still count if an answer needs correcting. Some real answers may not be stored because of these limits.
6. Keeping and deleting answers. You choose how long each form's answers are kept, from 1 to 365 days, with 365 days unless you choose otherwise. 365 days is the most on every plan. We delete each answer within an hour after its time is up, counted from when it was sent. If you change the keep time, the new time counts from when each answer was sent; shortening it can delete older answers immediately after you confirm the change. Deleting an answer, the form's code or your account deletes the affected answers from our database at once. Backup copies are overwritten within 30 days. Deleted answers cannot be brought back, so download what you need first.
7. Plans and paused forms. Forms are part of Pro and Business. If your plan no longer includes forms, you pause the code, we disable it, or we pause forms for everyone, the form takes no answers. A paused form does not have a button that continues to the form. Its notice can offer the business's own saved link only when the code has no access restriction (section 13). Answers already stored follow their keep time, and are not deleted just because your paid plan ends. You can still read, download and delete them while you can sign in, on any plan, while the code is paused and while new form answers are switched off (section 26).
8. Contacting people. ovbq does not email or text people because they answered your form. If you use what they send to contact them, you do it, and you follow the law, including the rules on marketing email and texts and getting consent where required. If form answers are affected by a breach, we tell you and you tell the people who answered as the law requires (section 26).
9. Your privacy-policy link. The editor has an optional field for a link to your own privacy policy. If you fill it in, the form page shows the link. It must lead to your own policy. We check that the address uses https and passes our link rules; we do not check what the policy says, and we are not responsible for it.

Back to contents

26. Handling form answers for you

This section applies to the answers people send to your forms ("form answers"), and to nothing else. For everything else we hold, the Privacy Policy applies and we decide how it is used.

1. Roles. For form answers, you are the controller or business and we are your processor or service provider. We handle them to store them, show them to you, email them to you as you choose, let you export and delete them, and keep the service secure (the purposes). The people are those who answer your forms. The data is what they type or choose, the questions as they read, and the time sent. This lasts as long as the answers are stored.
2. Your instructions. We handle form answers only as these terms and your settings tell us to, including the form's email choice and keep time, and what you do in your account. We do not use them for any other purpose, we do not sell them or disclose them except on the specific access and notification instructions in this section, and we do not combine them with other information. We may look at an answer only to run or secure the service, to handle an abuse report about the form, or when the law requires it. We may also delete answers, or stop a form, when the law requires it or when the form breaks section 25 or section 6, for example answers from a child under 13. If the law makes us do anything else, we tell you first unless the law forbids it. If we think one of your instructions breaks the law, we tell you.
3. Confidentiality. The people at Othex and its providers who can see form answers are bound to keep them confidential, and only those who need access have it.
4. Security. We protect form answers with the measures in section 16 of the Privacy Policy and on our security page, and keep them in our database on our hosting provider's servers. No system is perfectly secure.
5. Providers (subprocessors). You allow us to use our web hosting provider in the United States, which runs the servers, the database and the mail server (section 9 of the Privacy Policy). We use only providers whose terms require them to protect the data and keep it confidential, and we stay responsible to you for them. We email you at least 30 days before we add or replace a provider that handles form answers. You may object in that time by writing to privacy@ovbq.com or by deleting the form's code or your account. If we cannot agree, you may stop using forms and delete the form's code or your account. We then delete its answers at once.
6. If something goes wrong. If we confirm that form answers were accessed or lost without authorization, we email you without undue delay and within 72 hours after we confirm it, with what we know and what we are doing, and we keep you informed. You tell the people who answered and any regulator as the law requires.
7. Requests from people. The answers page lets you view, delete and export answers yourself. If a person asks us about their answers, we tell them which business runs the form, or pass the request to you; we do not answer for you. We give you reasonable help with a regulator or an assessment about form answers when you ask.
8. Deleting and returning. You can download your form answers and delete them at any time while you can sign in, on any plan. This includes after a paid plan ends, while the form's code is paused and while new form answers are switched off. If your account is closed, write to privacy@ovbq.com and we will send or delete them. Answers whose keep time has passed are deleted within an hour. When you delete the form's code or your account, we delete its answers from our database at once, and our backups overwrite them within 30 days. When this agreement ends, the form answers that are left are deleted when their keep time is up, or sooner if you ask at privacy@ovbq.com. Unless the law requires us to keep a copy, we keep none. Copies in emails you chose to receive stay in your mailbox, which is yours to clear.
9. Showing we comply. We give you the information needed to show that we follow this section, in these terms, the Privacy Policy and the security page, and we answer reasonable written questions. We do not give on-site audits. If you reasonably believe we are handling form answers in a way that this section does not allow, tell us at privacy@ovbq.com. We look into it and, if you are right, we stop it. We tell you if we can no longer meet our duties under this section.
10. Where they are kept. Form answers are kept on servers in the United States. We do not offer a transfer contract for them by default. If you collect answers from people in the EU, the UK or Switzerland and the law requires a transfer contract, write to privacy@ovbq.com before you start; we will tell you if we can sign one.
11. Your duties. You decide the purposes and have a lawful basis for them, you give the notices the law requires, and your instructions to us are lawful.
12. Liability and order. Sections 19 and 20 apply to this section. If this section and the Privacy Policy disagree about form answers, this section controls.

Authorized members and form answers. The purposes and instructions in items 1 and 2 also include showing answers to members you explicitly allow to view them and providing their CSV export only when you also grant answer export. You control these permissions and remain responsible for authorizing access and handling people's requests. Members use their own sign-ins; they cannot delete answers or change your form's questions, keep time or notifications. Member access still needs Team availability and allowance; losing it does not take away your own answer access, export or deletion rights. Removing a grant cannot recall a response already authorized or a copy already kept by the member. Our own answer-deletion and backup duties remain unchanged.

Notifications about answers. The purposes and instructions in items 1 and 2 also include sending the reference-only form event described in section 4 to the destination you select and enable. The message has an event ID, type and time, code/answer references and a test indicator, not answer or question text. These references may still relate to people. You are responsible for the selected recipient, required notices, lawful instructions and its onward use; choosing it does not excuse our duty to follow the limited instructions, protect our stored copies and remove matching queued references when the answer, form or account is deleted. Our queue is not a second answer archive. Customer-chosen recipients can keep delivered copies outside our control and outside the United States. No new provider is appointed by us through this feature, and item 5 still applies if we appoint one. No answer-body API or webhook access is granted.

Back to contents

27. Contact

Othex Corp, 5645 Coral Ridge Drive STE 137, Coral Springs, FL 33076, United States.
General and billing: hello@ovbq.com
Legal notices: legal@ovbq.com
Copyright notices: info@othexcorp.com (see section 8)
Report a harmful code: ovbq.com/report or abuse@ovbq.com

Back to contents