Privacy Policy

Simitar LLC · Last updated: July 23, 2026

1. Who we are

Simitar LLC ("Simitar," "we," "us") operates a rent-reminder communications platform used by property managers and landlords to send their tenants courtesy reminders about upcoming or past-due rent by phone and text message, and to deliver secure payment links. You can reach us at abartels@simitar.info or at Simitar LLC, 105 Troutbeck Court, Timonium, MD 21093.

2. Information we process

• Contact & account data for our business customers (property managers): name, email, login credentials, billing details.
• Tenant contact data that our customers upload to reach their tenants: name, phone number, unit/property, amount due, due date, and consent/do-not-call flags. We process this on behalf of our customers.
• Call & message records: outcomes, timestamps, recordings where disclosed, and delivery status.
• Payment data: handled by our payment processor (Stripe); we do not store full card numbers.

3. How we use it

To place reminder calls and send reminder text messages our customers request, deliver secure payment links, provide the platform and support, prevent fraud and abuse, and meet legal obligations. We do not sell personal information, and we do not use tenant contact data for our own marketing.

4. SMS / text messaging

Text messages are sent only where the sender (our customer) represents that the recipient has consented to be contacted. Message frequency varies. Message and data rates may apply. Reply STOP to opt out at any time; reply HELP for help. Mobile opt-in data and consent are not shared with third parties for their marketing. See our Terms of Service for the SMS program details.

5. Sharing

We share data only with service providers that help us run the platform (e.g., telephony, voice AI, payment processing, hosting), each under contract, and when required by law. Our business customers control their own tenant data.

6. Salesforce data (customers who connect Salesforce)

Some customers connect their own Salesforce organization so that our voice assistant can look up and update their Salesforce records during a call. If you are such a customer, this section describes exactly how that works.

• On whose instruction & how access is granted. Access happens only after a person on your team signs in to Salesforce through Salesforce's own OAuth screen and authorizes our Connected App. Each individual user connects their own seat — we do not use a single shared credential. Your company is pinned to the specific Salesforce organization first connected, and later connections that present a different Salesforce org are refused.
• What is accessed. Acting as the signed-in, phone-verified user (and therefore limited to what that user can already see in Salesforce), the assistant can read records to find them, summarize them, and list them (for example accounts, contacts, leads, opportunities, tasks and notes), and can write record updates, new records, notes and tasks. Every write is confirmed with the caller before it is made, and each kind of read and write can be turned on or off per organization by an administrator.
• What we do NOT store. We do not keep copies of your Salesforce record values. Our activity log records only what the assistant touched — a record identifier, the names of the fields changed, action types, counts and timestamps — and never the field values themselves; your own Salesforce Field History remains the record of value-level changes. Data needed to carry a single call is held in memory only and discarded when the call ends. Salesforce access tokens are encrypted at rest.
• Who it transits. To run a voice call, what is spoken — which may include Salesforce details read aloud — passes momentarily through our voice-infrastructure provider (Vapi) and our AI model provider (Anthropic), which process it to operate the call. Call recordings and logs may be retained by our voice infrastructure provider according to its configuration. We do not sell this data or use it to build cross-customer profiles.
• Revoking access & deletion. An administrator on your team can suspend or revoke a user's seat at any time, which deletes that seat's stored Salesforce token; the pinned-org binding can also be cleared. You can additionally revoke our Connected App from within your own Salesforce organization at any time. To have stored tokens and enrollment records deleted, email abartels@simitar.info. Because we hold no Salesforce record values, there are no CRM field values on our side to delete.

Dependency on Salesforce. This feature depends on Salesforce's API. If Salesforce suspends, limits, or terminates that access, the Salesforce features of the assistant may stop working. See our Terms of Service.

7. Retention, security, your choices

We keep data as long as needed to provide the service and meet legal requirements, then delete or de-identify it. We use reasonable technical and organizational safeguards, including encryption of sensitive credentials at rest. Tenants may opt out of texts (STOP) or ask the calling office to stop contact; customers and individuals may request access or deletion of their data by emailing abartels@simitar.info.

8. Changes

We may update this policy; material changes will be posted here with a new "Last updated" date.