• Communities
  • Software teams
  • Company
  • Contact

Legal

Privacy

The privacy notice for each UrboLogik product, in its own section below.

  • UrboVote
  • UrboPulse

UrboVote

Privacy Policy

Effective: September 11, 2026  ·  previously May 14, 2026  ·  UrboLogik LLC

This policy describes how UrboLogik LLC ("UrboVote," "we," "us") collects, uses, and protects information when you use the UrboVote platform. Please read it carefully. By using UrboVote you agree to the practices described here.

Contents

  1. 1. Who We Are
  2. 2. Information We Collect
  3. 3. How We Use Information
  4. 4. Ballot Secrecy
  5. 5. How We Share Information
  6. 6. Data Retention
  7. 7. Security
  8. 8. Your Rights
  9. 9. Children
  10. 10. Changes to This Policy
  11. 11. Contact

1. Who We Are

UrboVote is an electronic ballot platform operated by UrboLogik LLC, a Texas limited liability company. References to "UrboVote," "we," "us," or "our" mean UrboLogik LLC. If you have questions about this policy, contact us at hello@urbovote.com.

2. Information We Collect

Account and administrator information. When a board administrator creates an account, we collect their name, email address, association name, and billing information. Billing data is processed and stored by our payment processor (Stripe); we do not store full credit card numbers.

Voter roster data. Administrators upload a list of eligible voters — typically owner names, email addresses, and unit or lot identifiers. This data is provided by the administrator and is used solely to send ballot invitations and record participation.

Participation records. When a voter casts a ballot, we record that they participated — the timestamp and a unique token identifier — as part of the cryptographic audit log. We deliberately do not attach the voter's IP address or device details to any vote record. We do not link vote choices to voter identity. Vote selections are stored encrypted and disassociated from the voter's name or email before the tally runs.

Usage data. We collect standard server logs including IP addresses, browser type, and pages visited when you use the platform. This data is used for security monitoring, debugging, and service improvement.

Communications. If you contact us by email or through our contact form, we retain that correspondence to respond to your inquiry and improve our support.

3. How We Use Information

We use the information we collect to:

  • Create and manage your account and send ballot invitations to eligible voters
  • Generate and maintain the cryptographic audit log for each election
  • Process subscription payments and send billing receipts
  • Respond to support requests and communicate service updates
  • Detect and prevent fraud, abuse, and unauthorized access
  • Improve the platform through aggregated, anonymized analytics

We do not use voter roster data or election records for marketing, advertising, or any purpose other than operating the election for which it was uploaded.

4. Ballot Secrecy

Secret ballots. Every ballot is secret unless the organization running it deliberately chooses otherwise. On a secret ballot, UrboVote is designed so that no one — including UrboVote staff — can determine how any individual voter voted. Vote choices are encrypted at rest using AES-256 and are stored in a data structure that is separated from voter identity. The audit log proves that someone voted (participation) but not how they voted (choice). This separation is enforced at the application and storage layers and is a core architectural property of the platform, not a policy commitment alone.

Recorded (roll-call) ballots. Some organizations have governing documents that require a recorded vote, in which each member's position is part of the record. For those cases UrboVote offers a recorded mode, and on a recorded ballot the protection described above does not apply: your name, your selections and the time you voted are recorded together and are visible to your organization's administrators and included in its legal export. Recorded mode is never the default and cannot be switched on quietly. Your organization must first enable it in its settings, and whoever creates the ballot must then turn secrecy off for that specific ballot and confirm a warning that voters' names and selections will be visible. The choice is fixed before voting opens and cannot be changed once any vote has been cast, in either direction. You will be told a ballot is recorded before you cast your vote, and again on your receipt — if you do not see that disclosure, your ballot is secret.

UrboVote does not decide which mode your organization uses; that choice belongs to the organization administering the vote, under its own governing documents. Questions about why a particular ballot was run as a recorded vote should go to that organization.

5. How We Share Information

We do not sell personal information. We share data only in the following circumstances:

Service providers. We use Amazon Web Services (AWS) for cloud hosting and key management, and Stripe for payment processing. These providers process data on our behalf under data processing agreements and may not use your data for their own purposes.

The association's administrators. Board administrators can see the voter participation list — who voted and who did not — but not how anyone voted. This is consistent with standard election administration practice and your association's right to confirm quorum and voter eligibility.

Public results pages. When an election closes, UrboVote generates a public results page showing the tally, total participation count, and a cryptographic checksum of the audit log. No personal information appears on the public results page.

Legal requirements. We may disclose information when required by law, court order, or valid legal process, or to protect the rights, property, or safety of UrboLogik LLC, our users, or the public.

6. Data Retention

Election audit logs are retained for a minimum of seven (7) years from the date an election closes, consistent with HOA record retention requirements in most U.S. states. Audit log records are stored in write-once, immutable storage and cannot be deleted even at administrator request — this immutability is what gives the records their legal value. Account data and voter roster data that is not part of a sealed audit log may be deleted upon account closure.

7. Security

All data is transmitted over TLS 1.2 or higher. Data at rest is encrypted with AES-256. Ballot signing keys are generated per-ballot, stored KMS-encrypted in AWS Systems Manager, and permanently deleted when each ballot closes. We conduct regular security reviews and maintain access controls limiting who can access production systems. No security measure is perfect; if you become aware of a potential vulnerability, please contact us at hello@urbovote.com.

8. Your Rights

Access and correction. Account administrators may access and update their account information at any time through the platform settings.

Deletion. You may request deletion of your account and non-audit-log data at any time by contacting us. Sealed election audit records cannot be deleted because they are stored in immutable storage — their permanence is a core feature that protects your association and its members.

California residents (CCPA). California residents have the right to know what personal information we collect, request deletion of personal information (subject to the audit log exception above), and opt out of the sale of personal information. We do not sell personal information. To exercise your rights, contact us at hello@urbovote.com.

Voter rights. Homeowners whose email addresses were uploaded to UrboVote by their association's administrator may contact us to request that their information be corrected or removed from future elections. Participation records in sealed audit logs are retained per the retention policy above.

9. Children

UrboVote is intended for use by adults in their capacity as HOA members, board administrators, and property managers. We do not knowingly collect personal information from anyone under the age of 18. If you believe we have inadvertently collected such information, please contact us and we will delete it promptly.

10. Changes to This Policy

We may update this policy from time to time. When we make material changes, we will update the effective date at the top of this page and, where appropriate, notify account administrators by email. Continued use of the platform after a policy change constitutes acceptance of the updated policy.

11. Contact

Questions, requests, or concerns about this policy:
UrboLogik LLC
Email: hello@urbovote.com

UrboPulse

UrboPulse Privacy Notice

Version: 1.0 · Effective: 2026-10-20 · Published at https://urbopulse.com/#/privacy

This notice explains what personal information UrboLogik LLC, a Texas limited liability company ("UrboPulse", "we"), collects through urbopulse.com, Stripe Checkout and the UrboPulse license service, why, and what you can do about it. It does not cover the UrboPulse Team Host that a customer runs on its own servers: we do not receive the data that Host holds.

Contact: legal@urbologik.com.

Contents

  1. 1. What we collect, and why
  2. 2. What we do not collect
  3. 3. Who receives it
  4. 4. How long we keep it
  5. 5. Where it is processed
  6. 6. Your rights
  7. 7. Security
  8. 8. Children
  9. 9. Changes

1. What we collect, and why

WhatWhere it comes fromWhyBasis
Name, email address, organization, billing address, tax id, and the card brand, last four digits and countryYou, at Stripe Checkout, and StripeTo sell and bill a subscription, send receipts, and handle taxOur contract with you
Your license key (stored only as a hash), a random Host id, the number of Seats in use, the Host's version, the IP address and time of each request, and the organization name on an Enterprise licenseThe Host, each time it checks its licenseTo run, bill and secure the license and prevent misuseOur contract with you; our legitimate interest in security
The event type and issue or merge-request number of GitLab or GitHub eventsThe optional webhook relay, if you turn it onTo pass the event to your HostOur contract with you
Your email address and what you writeYou, if you email us (for example to ask for a demo)To answer youYour request

Card numbers go to Stripe, not to us.

The website urbopulse.com sets no cookies and runs no analytics at the time of writing. Our web host keeps ordinary server logs. The ROI calculator runs in your browser and sends us nothing.

2. What we do not collect

The UrboPulse Factory and the Team Host run on your own machines and network. We do not receive your code, prompts, traces, file paths, user names or the data your engineers stream to your Host. The license check carries only what is listed in section 1.

3. Who receives it

  • Stripe, Inc. processes payments and holds billing details.
  • Amazon Web Services hosts the license service, in the United States (us-east-1).
  • Professional advisers and authorities where the law requires it.

We do not sell personal information and do not use it for advertising.

4. How long we keep it

  • License records and their audit history: while the account exists, and for 3 years after it ends.
  • Server and application logs, including IP addresses: 90 days.
  • Billing and tax records: as long as the law requires.
  • Emails: as long as needed to answer you, and then up to 3 years.

5. Where it is processed

In the United States. If you are in the European Economic Area, the United Kingdom or Switzerland, we transfer your data under the mechanisms the law provides, described in the data processing agreement that we give Enterprise customers on request.

6. Your rights

Depending on where you live, you may ask us to give you a copy of your personal information, correct it, delete it, or restrict or object to how we use it, and you may complain to your data protection authority. Texas residents have the rights set out in the Texas Data Privacy and Security Act, where it applies to us. Email legal@urbologik.com; we answer within 45 days.

7. Security

License tokens are signed with keys that never leave our key-management service; license keys are stored as hashes; traffic to the license service uses HTTPS. No system is perfectly secure, and we tell affected customers when the law requires it.

8. Children

The Team Host is for businesses. We do not knowingly collect information from children.

9. Changes

We will post changes here with a new effective date, and tell customers by email of a change that materially affects them.

  • Home
  • Communities
  • Software teams
  • Company
  • Contact
  • UrboVote
  • UrboSentry
  • UrboPulse
  • Terms
  • Privacy