Privacy Policy

1. Scope

This Privacy Policy applies to the Relden public website, Relden application, controlled public Voice Lab, and related support and communications (collectively, the “Service”). It does not govern third-party services under their own privacy policies.

Relden is built for contractors and other business users. If you use Relden for an organization, that organization may control the business records its members enter and may manage member access to its workspace.

2. Information we collect

Account and identity information

We collect the information needed to create, secure, and administer an account, such as your email address, display name, password hash when password sign-in is used, account status, and organization membership. We never store your plaintext password.

If you continue with Google, Google returns a stable account identifier, verified email address, and basic profile information such as your name. Relden uses and stores the stable Google subject identifier, normalized email address, and display name to verify your identity, link repeat sign-ins to the same Relden account, and prevent account impersonation. Relden does not request access to Google Drive, Gmail, contacts, calendars, or advertising data. Google sign-in does not enroll you in marketing email.

Organization and customer records

Workspace members may provide organization names, member roles, time zone and currency, customer and service-location details, contact information, addresses, notes, project records, and related business context. Relden currently provides customer, location, project, plan, Draw, and Takeoff records. If users place estimates, invoices, job details, or other CRM material in notes or uploaded files, we process that material as user content; those labels do not imply that every corresponding native workflow is currently available.

Plans, files, Draw, and Takeoff data

We process files and images you upload, including PDF plans, along with file names, types, sizes, storage keys, processing status, and project associations. Draw and Takeoff data may include drawing geometry, text and layers, page calibration, routes, count points, symbol references, detection candidates, review decisions, quantities, and processing diagnostics.

Voice Lab data

The public Voice Lab generates speech from the greeting you enter. Your greeting and selected voice and style are sent to OpenAI for speech generation under the applicable provider terms. Relden does not persist the greeting or generated audio. Audio is held temporarily in your browser for playback and replay. To enforce usage limits, Relden stores account identifiers, a keyed hash of the IP address, character counts, and request timestamps. Authentication uses separate short-lived grants and browser sessions.

Payment and subscription information

When paid billing is enabled, Stripe collects and processes payment credentials through its hosted checkout and customer portal. Relden receives and stores provider identifiers, subscription status, product or price identifiers, paid-period dates, cancellation state, and verified webhook event metadata. Relden does not receive or store complete payment card numbers.

Device, session, and security information

We collect information generated when the Service is used, including IP address, browser user-agent information, authentication and session timestamps, request and error logs, and security or rate-limit events. Public Voice abuse controls use a keyed hash of the IP address rather than storing its raw value in the Voice session record. Ordinary account session records may contain the IP address and user-agent used to sign in.

3. How we use information

We use information to:

• provide, maintain, and support the Service and its workspace features;
• authenticate users, maintain sessions, and administer organization access;
• store and process project files, drawings, plans, and reviewed quantities;
• provide controlled AI and Voice Lab functionality;
• operate trials, subscriptions, and billing when those features are enabled;
• send transactional account and service messages;
• detect abuse, enforce usage limits, troubleshoot failures, and protect the Service;
• respond to support, privacy, and legal requests; and
• comply with law and enforce our Terms of Service.

Google identity information is used only to provide account authentication, account linking, security, and the features a user requests. Relden does not use Google user data for advertising. Relden's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

4. Cookies and similar technologies

Relden uses necessary cookies for account sessions, OAuth security, cross-host Voice Lab authorization, and related security controls. Production session cookies are configured with protections such as Secure and HttpOnly where appropriate. The current Service does not use third-party advertising cookies or third-party behavioral analytics.

5. How we disclose information

We may disclose information in the following limited circumstances:

• Workspace users. Information in an organization workspace is available to authorized members according to their roles and the Service's access controls.
• Service providers. Providers process information for hosting, networking, private object storage, authentication, email delivery, payment processing, security, and AI features. Current or planned production integrations include Google for authentication, Cloudflare R2 for private file storage, OpenAI for the Voice Lab, Stripe for billing when enabled, and Resend for transactional email when enabled.
• Legal and safety reasons. We may disclose information when reasonably necessary to comply with law or valid legal process; protect rights, safety, and security; investigate fraud or abuse; or enforce agreements.
• Business changes. Information may be transferred as part of a merger, financing, acquisition, reorganization, or sale of all or part of the business, subject to appropriate confidentiality and legal requirements.
• At your direction. We may disclose information when you or an authorized workspace administrator directs us to do so.

Relden does not sell personal information for money and does not use personal information for cross-context behavioral advertising. We also do not sell or transfer Google user data to data brokers or advertising platforms.

6. Retention

We retain account and workspace information for as long as the account or organization is active and afterwards as reasonably needed to provide support, protect the Service, resolve disputes, enforce agreements, and meet legal or accounting obligations. User content generally remains until it is deleted through available product controls or an authorized request is completed.

Application session credentials expire no later than 30 days after creation and may be revoked earlier. OAuth requests and Voice authorization grants are short-lived. Public Voice usage metadata may be retained longer for rate limiting, cost control, security, and abuse investigation. Relden has not adopted a single fixed deletion period for every category of account, workspace, security, billing, and Voice metadata. Backup copies, if maintained, may remain until their normal rotation completes.

7. Access, correction, and deletion requests

You may update certain account and workspace information in the Service. To request access, correction, or deletion of personal information, contact us at the address below. An organization administrator may need to authorize a request involving organization records. We may verify your identity and retain information when required by law or reasonably necessary for security, billing records, fraud prevention, dispute resolution, or the rights of other users. Privacy rights can vary by location.

You may also revoke Relden's Google account access through your Google Account settings. Revocation prevents new Google authorization but does not automatically delete the Relden account or information already retained under this policy; contact us for a Relden deletion request.

8. Security

Relden uses safeguards designed for the Service, including access controls, tenant-scoped authorization, hashed session credentials, server-side provider credentials, signed short-lived file access, private object storage, rate limits, and TLS for public production traffic. No security measure or transmission method can guarantee absolute security. Please use a strong, unique password where password sign-in is available and promptly report suspected unauthorized access.

9. International processing

Relden and its service providers may process information in the United States and other countries where they operate. Those locations may have privacy laws different from those in your location. Contact us if you have questions about where your information is processed.

10. Children's privacy

The Service is intended for businesses and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to Relden, contact us so we can investigate and take appropriate action.

11. Changes to this policy

We may update this policy as the Service or legal requirements change. We will post the revised policy here and update its effective date. If a change materially affects how we use information already collected, we will provide additional notice when required.

12. Contact

Questions or requests about this policy may be sent to admin@relden.co.