Privacy Policy
Nestarc Audit helps businesses record changes in their software and show an audit history to their own users. How we use information depends on whether you visit our site, manage a workspace, or appear in a customer’s audit history.
Who decides how data is used?
The individual who operates Nestarc Audit under the Nestarc name is responsible for account information, support correspondence and information needed to secure and operate the service. In this policy, “we” refers to that operator.
The organization that connects its software determines which people and changes to record and who may see or export them. We process those audit records and viewer permissions on its instructions. Its privacy notice explains why it records your activity.
What we collect and why
- Accounts and workspaces. When you sign up, you provide an email address and password. We store a password hash and use the email address to verify your account and send password-reset links. We keep your account ID, verification status, workspace and project names, membership, and records of key issuance and revocation to manage access.
- Customer audit histories. A customer’s connector sends an event ID, organization identifier, time, action, actor and target identifiers and types, selected values before and after a change, and sometimes a request identifier. For example, a role change can identify the user whose role changed and the person who changed it. The customer selects the fields and should exclude passwords, secrets and unnecessary personal details.
- Viewer access. When you open an audit history from a customer’s app, its server supplies a viewer ID, organization identifier and permissions. We use them to limit searches, event details and CSV exports to the authorized organization. The customer handles your sign-in to its app.
- Service and security records. We process connection information, including IP addresses, to route requests and prevent abuse. Authentication rate limits use hashed identifiers and attempt counts. We measure request counts, status and duration, track connector instance IDs, delivery counts and times, and record retained event counts for usage reports and manual billing review.
- Support and billing. If you contact us, we use your contact details and message to answer and follow up. The pilot generates billing proposals for manual review. The current application has no Paddle checkout or card-entry form.
Who receives information and where
People authorized by the customer can see its audit records, and those with export permission can download a CSV. The customer controls any copy it exports. We may also disclose information when required by law.
The planned hosting configuration uses Cloudflare’s network to serve the site, handle incoming requests and forward API traffic. The application database and encrypted daily backups are configured for Amazon Web Services in Seoul, South Korea. Cloudflare can process traffic and service metadata outside South Korea. The providers describe their infrastructure in the Cloudflare privacy FAQ and AWS region directory.
When you email support, Cloudflare Email Routing forwards your address and message to the operator’s support inbox.
Account verification and password recovery require an email provider to receive the destination address and a message containing a one-time link. The production email provider, its processing locations and the applicable cross-border transfer arrangements are still to be confirmed before live customer onboarding.
To protect records, the production configuration requires HTTPS and encrypted database storage and backups. The application restricts database access by role and by customer organization. It stores passwords using Argon2id hashing and enforces time limits on sessions and email links.
How long records are kept
- Audit event content. An event becomes unavailable to viewers 90 days after the time recorded by the customer’s application. A maintenance job then removes its content in batches. Closing a project or customer organization blocks access and ingestion and schedules the affected content for cleanup.
- Delivery receipts and usage. A receipt containing identifiers, timestamps and a content hash helps detect duplicate deliveries. It expires 97 days after the original event time. We separately retain event and organization identifiers, acceptance and expiry information, and daily counts to reconcile usage. The pilot has no automatic long-term deletion schedule for these accounting records.
- Backups. Daily database backups are configured to expire after seven days. A backup made before online deletion can contain the deleted record until the backup expires.
- Accounts and support. Verification links expire after 24 hours and reset links after 30 minutes. Authentication rate-limit counters expire after their 15-minute window. Account and membership records have no automatic deletion date when a project closes. Retention periods for closed accounts and support correspondence are still under review. You can request deletion as described below.
Cookies and browser storage
The application uses first-party cookies for authentication and access protection. Their maximum lifetimes are 24 hours for sign-in protection (na_auth), 20 minutes for workspace setup (na_onboarding), eight hours for a console session (na_console) and ten minutes for a viewer session (na_viewer). Blocking them can prevent sign-in or access to a history.
The console also writes a timestamp and random value in browser storage so other open tabs can refresh after sign-in or sign-out. It contains no account or session credentials. You can clear it through your browser’s site-data controls. The application does not set advertising cookies.
Privacy requests
If an audit record concerns you, contact the organization whose app displayed the history. It can identify the workspace and instruct us on how to handle your request. For account requests or privacy questions, email the operator at support@nestarc.dev. Describe your request and, if it concerns an account, identify the email address used for that account. We may ask you to verify your identity or authority. Keep passwords, API keys and complete audit records out of the request.
Depending on applicable law, you may request access, correction, deletion, a portable copy, or restriction of processing. You may also object to certain uses or lodge a complaint with your local data protection authority. A customer’s copy of a CSV or its own source records must be addressed with that organization.