Security

​

Core Security Implementation

AnotherWrapper includes several security features out of the box. This guide explains the existing security measures and shows how to implement optional rate limiting:

1. Database Security (RLS)
2. API Route Protection
3. Rate Limiting (not implemented but easy to add)
4. AI Services Abuse Protection
5. Email Security

​

Database Security with Supabase RLS

If you’ve followed the setup guides, Row Level Security (RLS) is already enabled and configured for all your tables, ensuring users can only access their own data.

​

RLS Guiding Principles

1. User Ownership: Use auth.uid() to match the authenticated user with their data
2. Default Deny: Start with all access denied, then explicitly grant permissions
3. Minimal Access: Give users access only to what they absolutely need
4. Separate Policies: Create distinct policies for different operations (SELECT, INSERT, etc.)

Here’s an example of common RLS policies:

-- Enable RLS
ALTER TABLE "documents" ENABLE ROW LEVEL SECURITY;

-- Users can only read their own documents
CREATE POLICY "Users can read own documents"
ON "documents"
FOR SELECT
USING (auth.uid() = user_id);

-- Users can only insert documents they own
CREATE POLICY "Users can insert own documents"
ON "documents"
FOR INSERT
WITH CHECK (auth.uid() = user_id);

-- Users can only update their own documents
CREATE POLICY "Users can update own documents"
ON "documents"
FOR UPDATE
USING (auth.uid() = user_id)
WITH CHECK (auth.uid() = user_id);

-- Users can only delete their own documents
CREATE POLICY "Users can delete own documents"
ON "documents"
FOR DELETE
USING (auth.uid() = user_id);

These policies ensure that users can only access, modify, or delete their own data, while administrators can manage all records through superuser access.

​

API Route Protection

All sensitive API routes in AnotherWrapper are automatically protected by authentication middleware:

import { authMiddleware } from "@/lib/middleware/authMiddleware";

export async function GET(req: Request) {
  // Apply auth middleware
  const authResponse = await authMiddleware(req);
  if (authResponse.status === 401) {
    return authResponse;
  }

  // Your protected route logic here
  return Response.json({ message: "Protected data" });
}

​

Rate Limiting (Recommended)

Rate limiting is not implemented by default, but you can easily add it to protect your API routes from abuse. Here’s how:

1. First, set up Upstash Redis:

npm install @upstash/redis @upstash/ratelimit

2. Add to your .env:

UPSTASH_REDIS_REST_URL=your_url
UPSTASH_REDIS_REST_TOKEN=your_token

3. Update the following files to implement rate limiting:

The middleware handles the rate limiting logic, while the blocked page provides a user-friendly interface when limits are exceeded. Users will be redirected to this page when they hit the rate limit on non-API routes.

​

AI Services Abuse Protection

Protect against AI service abuse by setting hard limits in your AI service dashboards:

All AI providers (OpenAI, Replicate, Anthropic, ElevenLabs, Groq) have built-in tools to regulate usage and set maximum spending limits. Make sure to configure these limits in each provider’s dashboard to prevent abuse and unexpected costs.

​

Email Security

​

Supabase Magic Links

• Default rate limit: 3 emails per hour without custom SMTP
• With custom SMTP setup, you can configure your own rate limits

​

Loops Email Service

• Built-in rate limit: 10 requests per second per team
• View Loops API Documentation