not.bot Sign My Work Privacy Notice
Julia Social, Inc. operates not.bot Sign My Work. This notice explains information handling for the hosted Basic and Pro service, including subscriber accounts, signing members, uploaded content, and people who check an item's status or retrieve its original. It is separate from the not.bot Verify privacy statement and the not.bot app's privacy information.
SMW is offered to adults based in the United States. This notice describes actual processing; eligibility restrictions do not mean that technical access is blocked outside the United States. Acknowledging this notice is not blanket consent to unrelated processing or a waiver of privacy rights.
1 Information we handle
Subscriber and account information
We handle the contact and account information supplied during signup and account administration, including email address, account or organization name, login identifiers, and any contact name, telephone number, or domain you provide. We hold plan, subscription, payment-status, and billing records and Stripe identifiers needed to administer the subscription. Stripe processes payment information through its payment services.
We keep evidence of document acceptance, including the customer and document identifiers, time, document version or content identifier, and IP-address and browser user-agent information supplied with the acceptance request. These are retained agreement records, distinct from ordinary application logs.
Members and signing records
We handle alias identifiers, account membership and permissions, member status, display or alias names, login and signing timestamps, and signing history. Signing records may contain disclosed credential claims and values, presentation hashes, and the presentation reference used to generate a downloadable signature. What is disclosed depends on the signing request and the presentation authorized by the signer.
An alias is not the same as a legal name, but we do not treat every alias record as anonymous. Account relationships, public information, disclosed claims, and other context can identify or help identify a person. The subscriber and signer may be the same person.
Content and metadata
For uploaded files, the service receives the file bytes, computes information needed for signing, encrypts the file, and stores the encrypted original. It handles temporary content keys and signing messages during that workflow. We do not routinely decode uploaded media to evaluate what it depicts or says. This is different from claiming that the server never receives plaintext or keys.
We separately retain metadata such as item titles, descriptions, original filenames, media types, sizes, source URLs for links, item identifiers, account relationships, timestamps, and signing or deletion status. These fields are not covered by the same encryption boundary as the stored file. Do not put information in a title or description on the assumption that we cannot access it.
Signing is authorized through the not.bot app. SMW does not take custody of the device-held private key that produces your signature. Passport enrollment and device authentication occur through the app's separate processes. This notice does not describe every party or record involved in app enrollment.
Technical information and correspondence
We use operational metrics and short-lived application logs to operate and troubleshoot the service. Ordinary application logging is focused on route and service metrics, rather than a centralized user-activity history. Malformed-request diagnostics may include request headers, which can contain identifiers. Our current setup retains the current and prior pod logs without a centralized log-management archive; rotation depends on operation of the infrastructure, rather than a guaranteed fixed number of days.
Cloudflare processes network requests for DNS, delivery, security, and standard traffic analytics. This can include IP addresses and other request or network information even though we have not configured an additional request-log export. We do not describe all network processing as anonymous or claim that the lack of our own log archive prevents providers from processing technical information.
We retain messages and related information you send for support, billing, privacy, abuse reports, or legal matters. Correspondence can include identifying information supplied by you or another person. Avoid sending unnecessary sensitive information.
2 Why we use information
We use information to:
- Establish and authenticate accounts, manage members and permissions, and provide signing and verification functions.
- Store and serve encrypted originals and maintain item status and signing history.
- Enforce signature allowances, administer subscriptions, process billing, and retain evidence of accepted terms.
- Deliver account and service messages, respond to requests, and provide maintenance and support.
- Measure operational availability and performance, troubleshoot errors, secure the service, and address misuse.
- Handle legal requests, statutory notices, preservation duties, privacy rights, and disputes concerning the service.
We do not use customer content or account information for advertising, marketing profiling, or AI training. We do not sell personal information or share it for cross-context behavioral advertising. Standard infrastructure analytics and availability monitoring are used for operation and security, not advertising or marketing analysis.
3 Who can receive or access information
Your account and people receiving your signatures
Account administrators can see the account's signing history and manage members and content. An administrator may also be a signer. Information available through the account should not be treated as private from its administrators.
A signed artifact carries or references information needed to verify it. For files, it can give a recipient the means to retrieve and decrypt the original. Recipients may retain or redistribute copies. We cannot erase a recipient's copies by deleting our hosted original. Organizational badges reflect the account owner's authorization, not an independent employment or identity endorsement by Julia Social.
Company personnel
Internal production access is currently limited to the CEO and head of engineering for maintenance and support. Authorized access may also be used for security and legal administration, including handling your requests. This describes company personnel access; it does not exclude processing by the infrastructure providers below or mean that access produces a signature on your behalf.
Service providers
We use the following providers for specific operational functions:
| Provider | Function and relevant information |
|---|---|
| Amazon Web Services | Hosts servers, databases, encrypted content, and database backups. Infrastructure processes the information needed to provide those services. |
| Cloudflare | Provides DNS, content delivery, security, and standard traffic analytics. Processes network and request information and traffic passing through its services. |
| Delivers service email through SMTP, processing recipient addresses, message content, and delivery information. | |
| Stripe | Processes payments and subscription billing, including payment, account, transaction, and billing information. |
| UptimeRobot | Checks the public health endpoint for availability. Those checks do not provide customer content or authenticated account pages to the monitor. |
Operational processing by these providers is different from selling information or providing it for advertising. A provider may also process information for its own obligations under its applicable terms and privacy information. We do not claim that every provider is a processor for every activity it performs.
Legal matters and business changes
We may preserve or disclose information when required by applicable law or valid legal process, to respond to statutory content notices, or where otherwise lawfully necessary to address misuse or protect rights and safety. We assess the basis and scope of requests. We notify affected customers where lawful and appropriate; some requests prohibit notification. A preservation request does not by itself authorize every form of disclosure or deletion.
Complaint handling can involve giving the affected customer the complaint information needed to respond, and copyright counter-notices are forwarded as required by the applicable process. Submitters should not expect such correspondence always to remain confidential from the other party.
Information may pass to a successor in a merger, reorganization, or transfer of the relevant business, subject to applicable law and protections for the information. This is not authorization for unrelated advertising or sale of customer data as a separate business activity.
4 Storage and location
Our application servers, PostgreSQL database, and primary content storage are on AWS in the US East region. Content is currently stored on provisioned AWS block storage. Our use of globally operating providers, including Cloudflare and Google, does not establish that all network traffic, email, or provider processing remains exclusively in that AWS region.
We protect connections using transport encryption and encrypt stored content files. We do not promise that all database metadata, logs, or correspondence are encrypted with keys unavailable to us. The server handles plaintext bytes and temporary content keys during processing, and it handles signature presentations and their references. These facts limit any claim that the architecture makes access to all customer information impossible.
5 Retention and deletion
| Category | Current retention practice |
|---|---|
| Signed original files | Retained after cancellation while Julia Social continues to exist, unless authorized deletion, a content restriction, or a legal requirement changes their handling. |
| Unsigned uploaded files | Expire after 72 hours and are removed by scheduled cleanup. |
| Deleted content files | Made unavailable through the service and eligible for physical purge after 90 days. Scheduled processing may occur after the precise eligibility time. The 90-day delay is our operational policy, not a universal legal retention requirement. |
| Signature presentation reference used for QR download | Available in the live database for up to seven days (seven by default; the account owner may set a shorter period or removal after download for later signatures; with removal after download, a presentation never downloaded is removed at seven days). Scheduled cleanup clears that presentation information; it does not erase the separate signing record. |
| Signing and content metadata | Retained indefinitely under the current policy, including after a content file is purged. This includes identifiers, history, timestamps, and retained descriptive or claim information. Some processing fields, such as the content key and content hash, are cleared by the workflow. |
| Account, subscription, billing, and acceptance records | Not automatically deleted on cancellation or ordinary account closure. Current practice is indefinite retention, subject to applicable rights and legal requirements. |
| PostgreSQL backups | Created daily, retaining the four most recent backups. Records removed from the live database can remain in older backups until they rotate out. This is a backup-count policy, not an unconditional promise of erasure within exactly four days. |
| Uploaded content backups | We do not back up uploaded content files. Database backups do not contain copies of those content files. |
| Application diagnostics | Kept within the current and prior pod-log lifecycle, without a centralized log archive. Provider-held network/security information follows the applicable provider's arrangements. |
| Support, privacy, abuse, and legal correspondence | There is no fixed automatic deletion schedule currently established for these records. We retain them for handling requests and related administration, disputes, and legal obligations, subject to applicable rights and requirements. |
Cancellation or ordinary account closure does not mean account erasure. You may still sign in and request deletion of content. A privacy request to erase personal information is a separate request and may have different legal requirements or exceptions.
We may preserve particular information beyond ordinary schedules when legally required. Conversely, applicable law may require restriction or deletion sooner. We restrict access to retained evidence as appropriate. The ordinary content-purge schedule does not override legal preservation duties, and our indefinite-retention policy does not override applicable privacy rights.
The service does not offer customer deletion recovery at launch. Retaining a file temporarily after deletion is not a promise to restore it. Keep independent copies of originals and downloaded signatures.
6 Cookies and operational measurements
The application uses session and authentication mechanisms to keep you signed in and protect account operations. Billing uses cookies or equivalent session records for authentication and the email-verification and subscription workflow. Cloudflare and other integrated service functions may process technical information needed for delivery and security.
We do not use advertising trackers or build marketing profiles. We do not change the necessary operation of the service in response to a browser Do Not Track signal. Standard operational metrics remain in use. Where an applicable law requires honoring an opt-out preference signal, we will honor that requirement; we currently do not sell personal information or share it for cross-context behavioral advertising.
7 Privacy requests
Contact [email protected] to ask about information we hold, request access or correction, request deletion, or exercise a privacy right that applies to you. Identify the account or alias and describe the request. Do not send your passport, password, private signing key, or unnecessary sensitive information.
We verify authority using information appropriate to the request, such as control of an account email or an alias, and request additional information only where reasonably necessary. An authorized representative may make a request with appropriate evidence of authority. We will explain if we cannot reasonably verify a request without compromising another person's information.
Your rights depend on applicable law and can include access, correction, deletion, a portable copy, and applicable opt-outs. Where provided by law, you may appeal a denied request by replying to the decision and asking for a privacy appeal. We will respond within applicable legal deadlines and explain relevant exceptions or further complaint options. We do not discriminate for exercising protected privacy rights.
If an organization administers your account and directs the relevant processing, we may need its instructions or direct your request to it. We remain responsible for requests concerning processing for which Julia Social is independently responsible. An administrator's control of account history does not eliminate a member's applicable legal rights.
Deletion may be limited by recordkeeping, legal preservation, security, or other applicable exceptions. Where deletion is required, we will explain the treatment of live records and backups rather than treating the published default retention schedule as a reason to refuse automatically.
SMW uses public blockchain identities. We cannot rewrite records on an independently maintained blockchain or delete copies held by other people. The inability to remove those records does not excuse handling a valid request concerning information within our control.
8 Adults and geographic scope
SMW subscribers and signers must be at least 18 and have reached the applicable age of majority. We do not offer SMW accounts to children. This is an eligibility rule, not a statement that we collect a date of birth or verify age or residence in every session. The not.bot app has a separate eligibility policy.
If you believe a person who is not eligible has an SMW account, contact [email protected] so we can address it. Lawful content depicting a minor is different from a minor operating an account; the content restrictions and applicable rights still apply.
9 Updates and contact
We will identify the effective date of this notice and post revised notices when practices change. We will communicate material changes through an appropriate account or service notice and obtain separate consent where required by law. Posting a change does not itself authorize a use prohibited by applicable law.
Julia Social, Inc.
300 Peachtree St NE, Ste CS2-3299, Atlanta, Georgia 30308
Privacy contact: [email protected], handled by the CEO.